Reading a Protocol Governance Proposal

Protocol governance proposals decide parameter changes, treasury spending and upgrades. They are published in full and read by a small fraction of those who could vote.

The structure

Summary. What is proposed, in a paragraph.

Motivation. Why. This is where the actual argument is and where weak proposals reveal themselves.

Specification. The technical change. Parameter values, contract addresses, code.

Rationale and alternatives. What else was considered.

Risks. Sometimes present, frequently thin.

Voting parameters. Quorum required, duration, and what happens if quorum is not met.

The four things to check

Who benefits. Treasury allocations, fee changes and parameter adjustments all move value between groups. Identifying which group benefits is the first analytical step and it is frequently unstated.

What the specification actually does. The summary and the specification occasionally diverge. The specification governs.

Who is voting. Token distribution determines outcomes. Where a small number of addresses hold enough to decide, the vote is a formality and the discussion is theatre.

Whether it is reversible. A parameter change can be adjusted later. A treasury disbursement cannot. An upgrade that changes contract logic may be irreversible in effect even if technically upgradeable again.

The participation problem

Turnout in most protocol governance is low, and voting power is concentrated. Delegation improves turnout and concentrates power further in the delegates.

This is not unique to crypto and it is more visible here, because the distribution is public and the votes are on-chain.

What a token holder can do

Read the proposals for protocols where you hold governance tokens. Vote or delegate deliberately rather than by default.

For most holders the realistic action is delegation to someone whose published positions you have read, which at least makes the concentration an informed choice.

Why it matters to non-participants

Governance decisions change fee structures, collateral requirements and supported assets. Users of a protocol are affected whether or not they hold the token.

Proposals are announced in advance with a voting period, which means changes to something you use are visible before they take effect if you are watching.

The timelock question

Well-designed protocols impose a delay between a passed vote and execution, so that users who disagree can exit.

The length of that delay is the most user-relevant governance parameter and it is rarely discussed. A protocol where governance can execute immediately is one where a passed proposal is a fait accompli.

Where funds sit at a venue rather than in a protocol, none of this applies, which is a real difference between the two. Balances at exchanges licensed in the jurisdiction are governed by a company under supervision rather than by a token vote, with a different set of trade-offs.