Governance
Clear accountability today, a path to decentralization
CeloHT is meant to be governed by its community, not run top-down. This model keeps decisions transparent, accountable, and aligned with our three founding pillars.
Structure
Three roles
Foundation Director
Owns overall strategic vision, represents CeloHT externally, and has the final say when governance reaches a genuine deadlock.
Maintainer Council
Responsible for technical review, Pull Request approval, and day-to-day repository management across all CeloHT repositories.
Community Contributors
Anyone submitting Issues, Pull Requests, or joining Discussions — the entry point to the Maintainer Council.
Decision-making
Not every decision needs the same process
Minor changes — typo fixes, documentation improvements — are approved by any maintainer after a standard review.
Major changes — new structure, policy shifts, brand changes — require Maintainer Council consensus, discussed publicly first.
Governance changes — edits to the governance policy itself — require a minimum 14-day public comment period and majority Council approval.
No governance token
Role-based, not token-weighted
CeloHT has no token, so community governance votes (in the dApp’s GovernanceVoting contract) use one-address-one-vote, restricted to addresses the Maintainer Council has approved — trading permissionless participation for resistance to Sybil and plutocratic attacks. See our developer documentation for the technical detail.
Read the full policy
The complete, binding governance document lives in our GitHub repository.