Governance
Every consequential decision, on the ledger.
ZooBC governance is split into two surfaces, both on-chain. The Foundation participates in one and administers the other. Neither is controlled by any single party — including the Foundation.
Protocol governance
Node owners decide.
Everything concerning the ZooBC blockchain's function — consensus parameters, fee schedules, protocol upgrades, addition or removal of registry entries — is decided by on-chain vote of the registered node owners. Proposals are submitted as transactions, quorum is enforced by consensus, and outcomes are executed automatically when they pass.
Registry size
13
Quorum
9
Open proposals
0
Live from /api/v1/governance/proposals. Two-thirds quorum is the default rule.
Foundation governance
Members and users decide.
Foundation-scope decisions — grant category weights, programme changes, reporting cadences, appointments, articles amendments post-incorporation — are also on-chain, using the same primitive that runs protocol votes. The electorate differs: Foundation members carry the primary vote, with participation weighting from users of the network.
Why on-chain?
The Foundation is asking the community to trust it with funds and stewardship. Using the same voting rail the network itself uses is the strongest available claim that no admin backend, no signature, no closed meeting can override an on-chain decision.
Proposal archive
Query the raw feed →No proposals yet.
There are zero governance proposals on the network today. When one is made it will appear here, mirrored from the on-chain feed. This is an honest early-stage state — proposals are for real decisions, not for looking busy.
How a protocol proposal gets made
- Draft a change in the community forum. Rough consensus on the intent.
- Submit as an on-chain proposal transaction. Consensus locks the exact text.
- Node owners vote within the voting window. Quorum enforced by consensus.
- Passing proposals execute automatically at the scheduled activation height.
- Outcome is mirrored to this page under "Protocol proposals".
How a Foundation decision gets made
- Draft published for member and public review with an explicit comment window.
- Revised text posted as an on-chain Foundation proposal transaction.
- Members vote; participating users add their weight per the published policy.
- Result is executed by the Foundation and logged here under "Foundation decisions".
- Rationale and dissents (if any) are attached to the record.