Rollup Governance v1 🏛️
The Habitat Rollup is governed and upgraded by the HBT token-holders. This includes technical upgrades, as well as fee structures and incentives. The initial first version (v1) of the Rollup Governance will help the Habitat community to propose, vote and implement changes to the shared infrastructure.
Starting with mainnet launch, governance will focus on controlling the reward structure and managing the operator fees. Within the first months, the Habitat genesis team stays involved in network and rollup governance for emergency situations and downtime assistance.
Members can take part in HBT Governance when they acquire HBT on the Ethereum Mainnet and deposit it on the Habitat Rollup. HBT is converted/wrapped to HBT, which is essentially a staked version with voting power on the rollup governance, given out in a 1:1 ratio.
Deposits enable Governance Participation
After mainnet launch, the HBT Community will have 2 voting modules to decide and vote about changes and receive signaling feedback for adjustments and incentives:
Signaling - used in Feature Farms, deciding about app layer integrations.
- Continous voting, no deadline
- No quorum required Deployed on Mainnet: https://etherscan.io/address/0x63818D74A71DC141b605204cf83FE51EE7267612
On-Chain Votes - used for rollup upgrades and finalizing funding proposals.
- 7 day voting period
- 10% quorum required Deployed on Mainnet: https://etherscan.io/address/0x4de7f3c0aD9EF9E8dDa5A7D19378C11B16d655af
Both initial Voting Modules share the same parameters:
total member count- how many users interacted at least once with the community?
total vote count- how many votes have been submitted?
total voting shares- total shares voted on a proposal
total signal- determines yes/no by range of 1-100
The modules can be implemented by all communities on Habitat to govern their own DAO/Community.
It is not enough to “hold” the voting power, HBT tokens need to be placed and removed actively. Governance participants “stake” their tokens on proposals, therefore they need to be on the rollup and actively voted on an outcome to be counted into the final results.
Users will need to stake their tokens on proposals they vote on and want to support. So each time tokens need to be moved from one proposal to another, being staked and un-staked. This way Habitat ensures no “Double-Vote” fraud.
Proposals have a simple and straight-forward format and can be used for signaling votes and for on-chain governance. Simply Create/Import Github Issues to Habitat, or simply insert a link to your proposal.
A proposal shall include:
- ID & title
- Markdown text
- Github link & tags
When HBT holders delegate votes, they assign their voting power to other delegates. Which allows them to form alliances and influence the outcome to their preference.
Potential upcoming features for delegation:
- Connect delegate address to Twitter & Github for social links
- Verification Tweet for further proof, until a decentralized identity solution is working.
Delegation might be necessary to unite voting power and issue proposals, as a minimal HBT Proposer Balance is required to initiate votes.