Skip to the article
Blockheight

Crypto markets, protocols, policy

DAO votes: delegate first, then make your tokens count

DAO voting weights your token balance at a snapshot; learn when to delegate, how quorum and majority decide a proposal, and how the approved change is carried out.

The Blockheight Editors··3 min read

DAO votes: delegate first, then make your tokens count

DAO voting turns token holdings into votes, and this article shows you when to delegate so your voting power counts and what happens after you cast a vote.

In token-weighted governance, each eligible token adds voting power; the system does not give every person one equal vote. BONE is shiba swap’s governance token. A holder can use it to vote on proposals where that token is eligible, as the DAO’s rules specify.

OpenZeppelin’s Governor documentation describes delegation-based voting power, while ShibaSwap illustrates the connection between a token and a DAO: shiba swap uses BONE for governance. The voting platform and the rules set for a DAO determine how balances are measured and counted.

Delegate before the snapshot

For OpenZeppelin Governor and Compound-style governance, holding tokens alone may not give your wallet voting power. The OpenZeppelin and Compound documentation say holders must delegate their votes, either to themselves or to a representative. Self-delegation makes your own wallet eligible to cast the votes tied to your balance.

Delegation is an on-chain transaction and usually costs gas. Set it before the proposal’s snapshot block: the snapshot fixes the voting power used for that proposal, so delegating afterward will not add your balance to that vote.

Say you hold 1,000 BONE and delegate to yourself before the snapshot. If the applicable voting strategy counts that balance, your vote for the proposal carries 1,000 votes at the snapshot. Without delegation in a Governor-style system, that balance can count as zero votes.

Vote, meet the threshold, then carry out the result

After a proposal opens, eligible holders vote during its voting period. The vote closes with a tally; quorum checks whether enough voting power participated, and the majority rule checks whether enough votes support the proposal. Each DAO sets its own thresholds and counting rules.

Snapshot records votes off-chain: its documentation says voters sign messages without paying gas, and voting power is calculated using the space’s strategy and snapshot. A Snapshot result does not itself change contracts or move treasury funds. A multisig or other authorized executor must carry out the approved decision.

An on-chain Governor vote requires a transaction and gas. In an OpenZeppelin Governor setup with a timelock, a successful proposal is queued, waits through the configured delay, then becomes executable through the Governor and timelock contracts. The delay gives holders time to respond before the change takes effect.

Before voting, check the proposal’s voting method, snapshot, delegation status, quorum and execution path. That tells you whether your tokens count and who must act after the tally.

Related stories