-
Notifications
You must be signed in to change notification settings - Fork 0
VOTING_SYSTEM.md
Transparent, fair, and community-driven governance.
The CeloHT Voting System provides a structured process for making important community decisions. While CeloHT strives to reach consensus through open discussion, formal voting ensures that significant proposals can be decided in a transparent and accountable manner.
Every vote should uphold the following principles:
- Transparency
- Fairness
- Inclusiveness
- Accountability
- Community Participation
- Open Governance
- Long-term Sustainability
A formal vote may be conducted for matters including:
- Governance updates
- Major strategic initiatives
- Significant technical changes
- Election or removal of maintainers
- Treasury-related decisions
- Adoption of major partnerships
- Changes to community policies
- Other proposals determined by the community
Minor operational decisions generally do not require a community vote.
Before a vote begins, a proposal should include:
- Title
- Summary
- Background
- Motivation
- Expected impact
- Benefits
- Risks
- Alternatives considered
- Implementation plan
- Discussion period
Incomplete proposals may be returned for revision.
The standard voting process consists of:
- Proposal Submission
- Public Discussion
- Proposal Revision (if needed)
- Voting Period
- Vote Verification
- Result Publication
- Implementation (if approved)
All major decisions should remain publicly documented.
Voting eligibility may include:
- Active contributors
- Maintainers
- Working group members
- Approved community representatives
Eligibility requirements may evolve as the governance model matures.
Depending on the decision, CeloHT may use:
- Simple Majority
- Qualified Majority
- Consensus Approval
- Ranked Choice Voting (when appropriate)
The voting method must be announced before voting begins.
For important governance decisions, a minimum level of community participation (quorum) may be required before results become valid.
Quorum requirements will be defined according to the type of proposal.
After every vote, the following information should be published:
- Proposal title
- Voting period
- Participation statistics
- Final outcome
- Implementation status
- Links to relevant discussions
Whenever possible, voting records should remain publicly accessible.
Critical security incidents, legal obligations, or infrastructure emergencies may require immediate action by maintainers without a prior community vote.
These actions must be documented and reviewed by the community after the situation has been resolved.
If community members believe that a voting process was unfair or improperly conducted, they may submit an appeal for review through the governance process.
Appeals should include:
- Description of the concern
- Supporting evidence
- Proposed resolution
- GOVERNANCE.md
- DECISION_PROCESS.md
- DISCUSSIONS.md
- TREASURY.md
- TRANSPARENCY.md
- COMMUNITY.md
The CeloHT Community
Founder: Johnny Dubic
© 2026 CeloHT - Open Source. Global Impact. Licensed under MIT.
Welcome to the official CeloHT documentation. This knowledge base provides comprehensive documentation for users, developers, contributors, partners, researchers, and ecosystem participants. Explore architecture, APIs, smart contracts, developer guides, governance, security, educational resources, roadmap, transparency reports, and community initiatives. Built with openness, collaboration, and long-term sustainability in mind, the CeloHT documentation follows international open-source documentation standards to make learning, building, and contributing accessible to everyone.