On-Chain Governance

On-chain governance is a method of running a blockchain or decentralised application in which the rules for changing the system are written into the system itself. Proposals are submitted as transactions, holders of a designated token vote by signing further transactions, and the result is counted by code. In many designs, an approved change is then applied automatically, without anyone having to persuade node operators to install new software.

The model is used at the base layer by networks such as Tezos and Polkadot, and at the application layer by many lending protocols and exchanges that are controlled by a DAO. It is the main alternative to off-chain governance, where changes depend on informal agreement and voluntary upgrades.

Think of a members' club whose rulebook includes a section on how the rulebook itself can be amended. Any member with enough shares can table a motion, everyone votes with a ballot box that counts automatically, and if the motion passes, the new rule is printed into the book the moment voting closes. There is no committee that can quietly ignore the result.

The voting weight usually follows the number of tokens a member holds, much like shares in a company. That makes the process clear and fast, but it also means that whoever holds the most tokens has the loudest voice.

Designs differ, but most follow a similar cycle:

1. Submission. A proposer locks a deposit or must hold a minimum amount of the governance token, which discourages spam. The proposal contains either a description or the exact code to be executed.
2. Voting period. Token holders vote for, against or to abstain within a fixed window. Some systems let holders delegate their votes to representatives.
3. Thresholds. A proposal passes only if it meets a quorum, a minimum share of total supply taking part, and the required majority.
4. Timelock and execution. Passed changes often wait in a timelock, giving users time to exit if they disagree, before a smart contract applies them.

• Tezos. Tezos describes itself as self-amending: protocol upgrades pass through a series of proposal and voting periods in which bakers vote, and an approved upgrade is activated by the network without a hard fork.
• Polkadot. Polkadot's governance lets DOT holders vote on referenda that can change the runtime, with conviction voting, under which locking tokens for longer gives a vote more weight.
• Decred. Politeia handles proposals and treasury spending, while consensus rule changes are approved by stakeholders voting with tickets on the chain itself, a hybrid of both approaches.
• DeFi protocols. Projects such as Compound and Uniswap use governor contracts that let token holders change parameters and spend treasury funds.

Protocols have experimented with ways to make token voting fairer or harder to game:

• Delegation. Holders who do not follow every proposal can assign their votes to a delegate, who builds a public voting record. This raises turnout but concentrates influence in well-known delegates.
• Time-weighted or locked voting. Some systems give more weight to holders who lock tokens for longer, on the theory that they are more committed to the protocol's future. Curve's vote-escrow model is a widely copied example.
• Quadratic and reputation-based voting. Experimental designs reduce the advantage of large holders by making each extra vote cost more, or by weighting votes by verified identity, which requires some form of proof of personhood.
• Veto or guardian roles. Some DAOs keep a small group that can cancel clearly malicious proposals, accepting a degree of central control as a safety valve.

Each refinement trades simplicity for protection, and none fully removes the influence of concentrated holdings.

Supporters say on-chain governance makes decision-making transparent and auditable, because every proposal and vote is public. It can resolve disputes without a chain split, since the losing side has a clear, accepted outcome rather than a reason to fork. It also lets a protocol upgrade more quickly and fund development from a shared treasury.

The most common criticism is plutocracy: one token, one vote favours large holders, including funds and exchanges that may vote with customers' tokens. Turnout is often low, so a small, organised group can decide outcomes. Governance can also be attacked. In April 2022, an attacker used a flash loan to borrow enough voting power to pass a malicious proposal on the Beanstalk protocol and drain its funds in a single transaction. Designs now commonly add voting delays, snapshots of balances taken before a proposal and timelocks to blunt such attacks. Finally, binding votes cannot capture technical nuance well, and a poorly reviewed proposal that passes may be executed before anyone spots its flaws. Supporters of Bitcoin's approach argue that this speed is exactly the danger.