# Governance delegation: voting power without transferring the tokens

Governance delegation assigns voting power to a representative under a token’s governance rules. In OpenZeppelin’s ERC20Votes and Governor example, delegates cast votes, and holders can delegate to themselves. This voting assignment is distinct from transferring the tokens or approving token spending; the exact snapshot and delegation behavior depend on the implementation.

Evidence: [How to set up on-chain governance](https://docs.openzeppelin.com/contracts/5.x/governance); [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20)

Canonical: https://degreesofsatoshi.com/encyclopedia/governance-delegation/
Published: 2026-10-02
Substantively modified: 2026-10-02
Independently verified by an automated reviewer: 2026-10-02T18:19:48.887Z
Data current through: 2026-10-02

AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied.

## Key facts

- **Voter:** Delegates carry voting power in the cited Governor example. ([How to set up on-chain governance](https://docs.openzeppelin.com/contracts/5.x/governance))
- **Self-delegation:** A holder can become their own delegate. ([How to set up on-chain governance](https://docs.openzeppelin.com/contracts/5.x/governance))
- **History:** ERC20Votes tracks historical balances for voting-power snapshots. ([How to set up on-chain governance](https://docs.openzeppelin.com/contracts/5.x/governance))

## Separate ownership from who casts the vote

Suppose Alice holds 100 voting tokens and delegates their voting power to Bob. In the illustrated governance design, Bob can use the delegated votes without becoming the token owner merely because of that delegation.

An ERC-20 allowance is a separate authorization to spend tokens. A wallet prompt that grants spending approval should not be interpreted as harmless voting delegation just because it appears on a governance website.

Evidence: [How to set up on-chain governance](https://docs.openzeppelin.com/contracts/5.x/governance); [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20)

## The proposal’s timepoint matters

The Governor example retrieves voting power historically, rather than assuming that the latest wallet balance is the power for every proposal. The token and governor must agree on their clock, which can use block numbers or timestamps.

A delegation made after the relevant snapshot need not change voting power for that proposal. Inspect its timepoint and implementation before expecting a new delegation to affect an already active vote.

Evidence: [How to set up on-chain governance](https://docs.openzeppelin.com/contracts/5.x/governance)

## Delegation is one part of the decision process

Voting weight, quorum, vote counting and execution rules are separate choices in the modular Governor design. A delegate with many votes still operates within those rules.

Evaluate the representative’s voting record and the authority the governance system actually controls. A successful vote cannot exercise powers that the governed contracts have not granted to its execution path.

Evidence: [How to set up on-chain governance](https://docs.openzeppelin.com/contracts/5.x/governance)

## Questions

### Does simply holding a voting token always activate my votes?

No. In the cited OpenZeppelin example, voting power is carried by delegates, so a holder who wants to vote can self-delegate. Other implementations may use different rules.

Evidence: [How to set up on-chain governance](https://docs.openzeppelin.com/contracts/5.x/governance)

## Claims and scope

### governance-delegation-quick-answer

Governance delegation assigns voting power to a representative under a token’s governance rules. In OpenZeppelin’s ERC20Votes and Governor example, delegates cast votes, and holders can delegate to themselves. This voting assignment is distinct from transferring the tokens or approving token spending; the exact snapshot and delegation behavior depend on the implementation.

Scope: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null}

### governance-delegation-fact-voter

Voter: Delegates carry voting power in the cited Governor example.

Scope: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null}

### governance-delegation-fact-self-delegation

Self-delegation: A holder can become their own delegate.

Scope: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null}

### governance-delegation-fact-history

History: ERC20Votes tracks historical balances for voting-power snapshots.

Scope: {"collection":"defi","dataAsOf":"2026-10-02","blockHeight":null}

## Sources

- [How to set up on-chain governance](https://docs.openzeppelin.com/contracts/5.x/governance) — OpenZeppelin. Delegation, historical checkpoints, quorum and execution delays. Locator: Voting token; Governor; Timelock. Retrieved: 2026-10-02T17:03:45.975Z.
- [ERC-20 Token Standard](https://eips.ethereum.org/EIPS/eip-20) — Ethereum Improvement Proposals. Token supply, displayed units and balance accounting. Locator: totalSupply; balanceOf; transfer; decimals; approve; allowance; transferFrom; Transfer. Retrieved: 2026-10-02T17:03:45.826Z.

## Revision history

- 2026-10-02: First publication after primary-source research and independent automated verification.

## Cite this entry

Degrees of Satoshi editorial project. “Governance delegation: voting power without transferring the tokens.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/governance-delegation/