• Open now · 50 briefs
    Get paid in DFR to help build this forum
    DAOForum runs like a real DAO — so anyone can contribute, not just watch. Pick one of 50 open topics from the Curated Launch Library, write it, and an accepted thread pays 2,000–4,000 DFR straight from the on-chain treasury. The DFR is yours — hold it or sell it. No fee to claim, no wallet to connect — you only share an address at the end so the treasury can pay you. Do the real thing, and if you're good, become part of the team.

Delegates and Delegation: How DAO Voting Power Actually Flows in 2026

Lawlet

Member

Introduction: Holding Tokens Is Not the Same as Governing​


Decentralized autonomous organizations (DAOs) promise a different approach to decision-making. Instead of leaving every important decision to a central company or a small management team, they allow communities to participate in governing protocols, allocating treasury funds, approving upgrades, and setting long-term priorities.

But decentralization introduces a practical challenge: not every token holder has the time, technical knowledge, or interest required to evaluate every proposal.

A governance proposal might involve a smart contract upgrade, a multimillion-dollar treasury allocation, an incentive program, or a change to a protocol's economic model. Understanding its consequences may require hours of research. Multiply that across several DAOs, and direct participation becomes difficult.

Delegation offers a solution. Token holders can assign their voting power to representatives who actively follow governance and make decisions on their behalf.

However, delegation also introduces new risks. Voting power can become concentrated, delegates can become inactive, and financial incentives can influence how representatives vote.

The important question is therefore not simply how to delegate tokens. It is how to ensure that delegated voting power remains transparent, accountable, and aligned with the people who entrusted it.

This guide explains how delegation works, how to choose a representative, which platforms support governance participation, how delegate incentives operate, and how DAOs can mitigate vote-buying and delegation-capture risks.

1. What Is Delegation, and Why Do Governance Tokens Require It?​


Delegation is the process of assigning the voting power associated with governance tokens to a wallet address. That address may belong to the token holder or to another person, organization, or governance participant.

Consider a simple example.

Alice holds 1,000 governance tokens. She wants to influence decisions in her DAO but cannot follow every proposal. She delegates her voting power to Bob, a community member who regularly researches proposals and publishes explanations of his voting decisions.

If the DAO uses one vote per eligible token and all 1,000 tokens qualify, Bob can exercise the voting power Alice delegated to him, subject to the DAO's rules.

Alice ordinarily retains ownership of her tokens. Bob receives voting authority, not ownership of the underlying assets.

Why do some governance tokens need delegation?​


Some token-based governance systems distinguish between owning tokens and having activated voting power.

OpenZeppelin's ERC20Votes documentation explains that its voting extension tracks historical voting power through checkpoints. By default, an account's token balance does not automatically count as voting power. Holders generally need to delegate to activate that voting power, including delegating to themselves if they want to vote directly.

This design makes participation explicit and allows the system to record voting power at defined historical points.

The rule is not universal across every DAO. Some use different token contracts, off-chain voting strategies, or alternative governance mechanisms. Always check the specific system's documentation before assuming that holding a token automatically grants active voting power.

For example, the ENS DAO delegation guide explains that $ENS tokens must be delegated to an Ethereum address before they can be used to vote. Delegation can be directed to the holder's own address or another representative.

Delegation, ownership, and voting power are different​


These three concepts should not be confused.

  • Holding means you own the tokens.
  • Delegating means you assign the associated voting power according to the governance system's rules.
  • Transferring means you move ownership of the tokens to another address.

Delegation ordinarily does not transfer token ownership or give the delegate permission to sell the holder's tokens. It changes who can exercise the associated voting power.

The precise rules depend on the token contract. In some systems, each address can delegate to only one representative at a time. Others support more flexible arrangements, including multi-delegate mechanisms.

Why delegation matters​


Delegation can make governance more accessible, allow participants to specialize in particular policy areas, and encourage better-informed voting.

It can also help communities identify people who consistently contribute research, challenge weak proposals, and explain the consequences of governance decisions.

But delegation is not automatically decentralizing. If most voting power accumulates in a handful of representatives, a DAO may become dependent on a small group even though its tokens are distributed among thousands of holders.

The objective is to make participation easier without removing accountability.

2. Self-Delegation vs. Delegating to Others​


Token holders generally have two broad choices: assign voting power to their own address or delegate it to someone else.

Self-delegation: keeping direct control​


Self-delegation assigns voting power to the holder's own address. It is useful for people who want to research proposals, vote independently, and take direct responsibility for governance decisions.

For example, Alice may want to vote on a proposal that changes a protocol's fee structure. If the governance system requires prior delegation, she can self-delegate and then participate directly.

The main advantage is independence. Alice does not need to trust another person to represent her preferences.

The trade-off is time. She must follow proposals, understand the arguments, meet voting deadlines, and make decisions herself.

Delegating to another representative​


Delegating to another address is useful when a holder wants to participate indirectly through someone who follows governance more closely.

A capable delegate may provide technical knowledge, consistent participation, independent research, and clear voting explanations.

However, a delegate can become inactive, support proposals the holder opposes, or develop financial relationships that affect their judgment.

Delegation should therefore be treated as an ongoing relationship rather than a permanent endorsement.

A practical comparison​


  • Self-delegation: greater direct control, but usually more research and participation.
  • Delegating to another person: less day-to-day work, but greater dependence on the representative's judgment.
  • Changing delegation: an option when a representative becomes inactive or no longer reflects your priorities, subject to the DAO's rules.

The Arbitrum DAO delegation guide explains that token holders can delegate voting power, change their representative, or reclaim voting power according to the DAO's procedures.

The best choice depends on your available time, expertise, and willingness to follow governance. Neither option is automatically superior.

3. How to Research and Choose a Delegate​


Choosing a delegate is one of the most important decisions a token holder makes. The person or organization receiving your voting power may influence treasury spending, protocol development, security decisions, and the direction of the ecosystem.

A large following or impressive profile is not enough. The strongest evidence comes from a delegate's actual behavior.

A. Examine voting history​


Start with previous votes. Look for consistency, thoughtful participation, and explanations that demonstrate an understanding of the proposal.

Ask yourself:

  • Does the delegate participate regularly?
  • Do they explain why they support or oppose proposals?
  • Do they identify trade-offs and potential risks?
  • Do they evaluate proposals independently rather than simply following popular opinion?
  • Do they explain their decisions when community members disagree?

Voting participation is useful, but it should not be treated as the only measure of quality. A delegate who votes on every proposal without researching it may contribute less than someone who carefully evaluates difficult decisions and communicates their reasoning.

B. Read delegate statements​


A delegate statement should explain the representative's priorities, relevant experience, approach to governance, and commitment to participation.

For example, a delegate may prioritize protocol security, treasury sustainability, public goods, or ecosystem growth. These priorities help token holders determine whether the representative's judgment is likely to align with their own.

A useful starting point is the Optimism Collective delegate forum, where delegates publish statements and governance updates. One example is Ezekiel Ekondu's delegate statement, which describes commitments to active participation, thoughtful proposal review, transparent voting rationales, and continued learning.

A statement is a commitment, not proof of performance. Compare what the delegate promises with their actual activity.

C. Check participation beyond voting​


Good governance happens before and after a vote.

Strong delegates may identify weaknesses in proposals, ask questions, participate in community discussions, suggest amendments, and explain implementation risks.

Review three recent proposals and ask:

  • Did the delegate contribute to discussions before voting?
  • Did they identify meaningful risks or alternatives?
  • Did they explain their final position?
  • Did they communicate the outcome or follow-up work?

This process helps distinguish representatives who contribute to governance from those who simply cast votes.

D. Investigate conflicts of interest​


Delegates may have financial relationships with protocol teams, grant recipients, service providers, or organizations seeking treasury funding.

These relationships do not automatically make someone a bad delegate. Relevant professional experience can improve decision-making. The problem arises when financial interests are hidden or improperly influence a vote.

Look for clear disclosures, explanations of relevant relationships, and appropriate procedures for handling conflicts.

E. Use real delegate profiles​


The following official resources provide starting points for research across four major ecosystems.

  • Optimism: delegate statements and updates. Review published commitments and compare them with voting activity.
  • Arbitrum: delegation documentation and the DAO FAQ. These explain how representatives participate and how holders can change their delegation.
  • ENS: ENS delegate profiles on Agora. Profiles can include delegate statements and participation information. For example, the directory includes named participants such as Superphiz.eth and organizational representatives such as coinbase.eth. Review their current records rather than assuming that an old participation figure remains accurate.
  • Uniswap: Uniswap governance documentation. Use the official governance process to understand UNI delegation and evaluate participating representatives.

These are research starting points, not endorsements of particular delegates. Participation figures and profile information change over time.

A practical delegate-selection checklist​


Before delegating, check whether the representative has a credible record, communicates clearly, discloses conflicts, and understands the proposals they vote on.

The most important question is not simply, "How much voting power does this delegate have?"

It is, "Can I understand and trust the way this delegate uses voting power?"

4. Delegation Platforms: Tally, Boardroom, and Agora​


Governance platforms make it easier to discover delegates, examine proposals, and participate in voting. However, a platform interface is not the same as the governance system itself. Token contracts and DAO rules determine how voting power is calculated and which actions are valid.

Tally​


Tally provides governance interfaces for supported protocols, including tools for examining proposals, exploring delegates, and participating in governance.

Its role and availability vary by DAO and product. Users should begin with their DAO's official documentation and confirm which interface is currently supported.

Boardroom​


Boardroom has provided governance discovery and analytics tools, including delegate discovery, voting information, and proposal tracking.

An example of its use in the Optimism ecosystem is documented in the Optimism governance proposal for Boardroom's Delegate Discovery initiative. The proposal described tools that helped token holders research delegates and compare governance activity.

The wider lesson is that delegate discovery should make it easier to find representatives based on their priorities and contributions, rather than simply ranking them by voting power.

Agora​


Agora provides governance infrastructure and interfaces used by DAOs. The ENS Agora interface, for example, lets users explore ENS governance, view delegates, and examine proposals.

The ENS delegation guide identifies Agora, Tally, and the ENS delegation interface as options for delegating $ENS voting power.

How to use governance platforms safely​


  • Start from official DAO documentation rather than an unfamiliar link shared in a message.
  • Confirm that the platform supports the correct DAO and governance token.
  • Review the delegate's profile and voting history.
  • Verify the recipient address before confirming a delegation transaction.
  • Read the transaction details in your wallet before signing.
  • Confirm that the delegation was recorded successfully.
  • Never enter your seed phrase into a website to delegate tokens.

A familiar interface does not guarantee that a delegate is trustworthy. Platform security and representative quality are separate questions.

5. Delegate Incentive Programs: Paying for Useful Governance​


Delegates spend time researching proposals, participating in discussions, explaining decisions, and monitoring governance outcomes. These responsibilities can become substantial as a DAO grows.

Incentive programs attempt to compensate contributors for that work and encourage consistent participation. But poorly designed incentives can reward activity without improving decision quality.

Why incentives can help​


A well-designed program can make governance work more sustainable, encourage representatives to publish voting rationales, and lower the financial barrier to participation for people who lack substantial personal resources.

However, rewards should not be distributed simply because a delegate controls a large amount of voting power.

What should rewards measure?​


  • Participation in eligible governance votes.
  • Clear, substantive explanations of voting decisions.
  • Meaningful involvement in proposal discussions.
  • Disclosure of relevant conflicts of interest.
  • Compliance with the program's published rules.
  • Evidence of sustained contribution over time.

A program that rewards only voting frequency may encourage delegates to vote without conducting adequate research. A program that rewards only delegated token volume may reinforce concentration by directing the largest payments to already powerful representatives.

Transparent eligibility requirements, reasonable caps, public reporting, and periodic evaluation can help reduce these risks.

Real example: Arbitrum's delegate incentives​


Arbitrum provides a concrete example of how incentive programs can evolve. The Arbitrum Foundation's 2025 transparency report describes the Rewarding Active Delegates (RAD) program, an iteration of its earlier Delegate Incentive Program.

The report explains that RAD rewards active delegates based on their voting records and publicly shared voting rationales. It also describes oversight involving the DAO's operating company and a third-party program manager.

This model illustrates an important principle: incentives can reward both participation and the communication that helps token holders evaluate governance decisions.

It does not establish that every incentive program should use the same structure. Each DAO should evaluate its own needs, budget, participation patterns, and risk of gaming.

Real example: ENS delegation incentives​


ENS governance has also considered and approved delegation incentive funding. Its official proposal history includes the Delegation Incentives Program funding proposal and related governance decisions.

This provides a useful example of incentives being handled through formal DAO governance rather than an informal promise from a project team.

Before citing a particular program's current reward amount or eligibility conditions, check the latest proposal and implementation status. Funding decisions can change, and approval of a proposal does not automatically mean that every component remains active indefinitely.

The broader lesson is that incentives should strengthen informed participation without turning voting power into a market for political support.

6. Vote-Buying and Delegation-Capture Risks​


Delegation creates an opportunity for expertise to influence governance, but it also creates incentives for interested parties to accumulate voting power.

Vote-buying and delegation capture are related but distinct problems.

Vote-buying generally involves offering a benefit in exchange for a particular vote or voting commitment. Delegation capture occurs when an individual or coordinated group gains disproportionate influence over governance representatives or voting power.

Both can undermine the independence of a DAO.

Risk 1: Direct vote-buying​


An interested party may offer money, tokens, or another benefit in exchange for a delegate's support of a proposal.

Compensation for legitimate governance work is not automatically vote-buying. The concern is a payment or arrangement intended to purchase a particular voting outcome, especially when it is concealed from token holders.

When voting decisions are influenced by undisclosed payments, public rationales become less reliable and governance legitimacy suffers.

Risk 2: Concentrated voting power​

Imagine a DAO with 100 million eligible votes, of which three delegates collectively control 60 million.
That concentration does not prove wrongdoing. Holders may have delegated voluntarily because they trust those representatives. Nevertheless, it creates systemic risk if the delegates coordinate improperly, become compromised, or stop representing their constituents' interests.
A healthy governance system should make concentration visible and allow token holders to reconsider their delegation choices.

Risk 3: Coordinated delegation capture​

A team, investor group, or organized interest may encourage holders to delegate to selected addresses. If enough voting power accumulates, the group may influence treasury decisions, protocol upgrades, or changes to governance rules.
Warning signs include undisclosed relationships, misleading claims about delegate independence, opaque coordination, and rewards conditioned on specific voting outcomes.
Delegation campaigns are not inherently improper. The important distinction is whether participants can understand who is coordinating the campaign, what incentives exist, and how representatives intend to vote.

Risk 4: Last-minute changes to voting power​

If a governance system permits voting power to change before a relevant snapshot, a sudden movement of tokens or delegation may alter the apparent balance of support.
The precise risk depends on the implementation. Historical voting checkpoints and clearly defined snapshots can limit some forms of manipulation, but they do not eliminate bribery, collusion, or long-term concentration.

How DAOs can mitigate these risks​

  • Public delegate statements: Make voting histories, commitments, and relevant relationships easier to inspect.
  • Transparent incentives: Publish funding sources, eligibility rules, reward calculations, and conflict-of-interest policies.
  • Historical checkpoints: Use appropriate mechanisms to record voting power at defined points in time.
  • Clear deadlines: Communicate snapshot times and delegation rules before voting begins.
  • Concentration monitoring: Publish information about the distribution of voting power across representatives.
  • Independent analysis: Encourage public discussion and scrutiny of important proposals.
  • Appropriate governance safeguards: Consider quorum requirements, timelocks, proposal thresholds, or additional review procedures where they fit the protocol.
No single safeguard solves every problem. For example, a snapshot can help prevent certain last-minute changes but cannot prevent a delegate from accepting a bribe. Likewise, a high quorum may reduce the risk of a small group passing a proposal, but excessively high thresholds can make governance ineffective.
Safeguards should be matched to the actual threat rather than added without considering their costs.

7. Re-Delegation and Vote-Weight Snapshots​

Delegation is not necessarily permanent. In many systems, token holders can change representatives, but the timing and effect depend on the DAO's rules and implementation.

How re-delegation works​

Suppose Alice delegates her voting power to Bob. After several months, Bob stops participating in governance.
Alice can review other delegates, select a more suitable representative, and change her delegation if the governance system supports that operation.
In systems that support self-delegation, she may also reclaim voting power for direct participation. Re-delegation generally changes the assignment of voting rights rather than transferring ownership of the tokens.
The Arbitrum delegation documentation explains how token holders can change or revoke their delegation. The ENS delegation guide similarly states that delegation can be changed.
A holder should verify the actual transaction requirements and the effect of a change on any ongoing proposal.

What is a vote-weight snapshot?​

A snapshot records voting power at a defined point in time. Depending on the governance system, that point may be represented by a blockchain block number, timestamp, or another specified reference.
Consider this simplified example:
  • Alice holds 1,000 GOV.
  • Before a proposal's snapshot, she delegates her voting power to Bob.
  • At the relevant snapshot, the governance system records Bob's eligible voting power.
  • Alice later changes her delegation.
In a system that uses historical voting checkpoints, the later change does not necessarily alter the voting power recorded for the existing proposal. The proposal may continue to use the historical record associated with its designated timepoint.
This separation helps ensure that voting weight is calculated according to a defined rule rather than changing unpredictably during a vote.

Snapshot time is not the voting deadline​

These are different concepts.
The snapshot determines which voting power is counted under the proposal's rules. The voting period determines when participants can cast their votes.
A holder who delegates after the relevant snapshot may not contribute voting power to that proposal. Similarly, a later re-delegation may not change the historical voting weight already recorded.
OpenZeppelin's Governor documentation explains how governance systems can use historical voting power from vote-enabled token contracts.
Before participating, check:
  • When voting power is measured.
  • Whether the system uses historical checkpoints or another voting strategy.
  • When a delegation change becomes effective for the relevant proposal.
  • Whether the holder can vote directly after changing delegation.
  • Whether the proposal is on-chain, off-chain, or governed by a combination of mechanisms.
Understanding these details can prevent token holders from assuming that a delegation transaction automatically gives them voting power in every ongoing proposal.

8. What Better Delegation Should Look Like in 2026​

Delegation should not be judged solely by how many tokens have been assigned to representatives. A DAO can have substantial delegation participation and still suffer from weak accountability.
A stronger approach evaluates the entire governance relationship.

For token holders​

Treat delegation as an active choice. Research representatives, read their explanations, review their participation, and change your delegation if their conduct no longer meets your expectations.
You do not need to become a full-time governance researcher. Even periodically reviewing important proposals can help you decide whether your delegate remains aligned with your priorities.

For delegates​

Treat delegated voting power as a responsibility rather than a personal achievement.
Publish your reasoning, acknowledge uncertainty, disclose relevant conflicts, and explain when you change your position. If you cannot adequately review a proposal, communicate that limitation rather than presenting an uninformed vote as a researched decision.
Technical expertise is most useful when it can be translated into clear explanations that ordinary token holders can understand.

For DAO governance teams​

Make delegation easier to understand and safer to use.
Provide accessible documentation, clear voting timelines, searchable delegate records, and transparent information about incentive programs. Monitor voting-power concentration and evaluate whether the governance process allows token holders to hold representatives accountable.
Where possible, publish participation data without reducing every contribution to a simplistic performance score.
A healthy governance system should help participants answer three questions:
  • Who currently exercises voting power?
  • Why are they voting the way they are?
  • What can token holders do if they disagree with their representatives?
If those answers are difficult to find, the DAO has an accountability problem even if its voting contracts function as designed.

Conclusion: Delegation Is a Relationship, Not a Transaction​

Delegation solves a real coordination problem. It allows token holders to participate in complex governance without researching every proposal themselves, while enabling experienced contributors to specialize in protocol decisions.
But delegation also changes how power is distributed. Voting power can become concentrated, incentives can distort behavior, and holders can lose visibility into decisions that affect their assets and communities.
The answer is not to reject delegation. It is to practice and design it responsibly.
Token holders should select representatives based on evidence rather than popularity alone. Delegates should communicate their reasoning and disclose conflicts. Governance teams should design incentive programs carefully, monitor concentration, and establish clear rules for snapshots and re-delegation.
Most importantly, token holders should remember that delegation does not eliminate their responsibility to the DAO. It changes how they exercise that responsibility.
A healthy DAO does not merely distribute voting power. It makes that power understandable, contestable, and accountable.
That is the real test of decentralized governance in 2026: not whether people can delegate their votes, but whether the resulting system continues to serve the community that entrusted those votes in the first place.

Sources and Further Reading​

Editorial note​

Governance rules, platform availability, delegate participation, and incentive programs can change. Readers should confirm current DAO-specific documentation and proposal status before making decisions. Examples in this article illustrate governance practices; they are not endorsements of individual delegates or financial advice.
 
Last edited:

Introduction: Holding Tokens Is Not the Same as Governing​


Decentralized autonomous organizations (DAOs) promise a different approach to decision-making. Instead of leaving every important decision to a central company or a small management team, they allow communities to participate in governing protocols, allocating treasury funds, approving upgrades, and setting long-term priorities.

But decentralization introduces a practical challenge: not every token holder has the time, technical knowledge, or interest required to evaluate every proposal.

A governance proposal might involve a smart contract upgrade, a multimillion-dollar treasury allocation, an incentive program, or a change to a protocol's economic model. Understanding its consequences may require hours of research. Multiply that across several DAOs, and direct participation becomes difficult.

Delegation offers a solution. Token holders can assign their voting power to representatives who actively follow governance and make decisions on their behalf.

However, delegation also introduces new risks. Voting power can become concentrated, delegates can become inactive, and financial incentives can influence how representatives vote.

The important question is therefore not simply how to delegate tokens. It is how to ensure that delegated voting power remains transparent, accountable, and aligned with the people who entrusted it.

This guide explains how delegation works, how to choose a representative, which platforms support governance participation, how delegate incentives operate, and how DAOs can mitigate vote-buying and delegation-capture risks.

1. What Is Delegation, and Why Do Governance Tokens Require It?​


Delegation is the process of assigning the voting power associated with governance tokens to a wallet address. That address may belong to the token holder or to another person, organization, or governance participant.

Consider a simple example.

Alice holds 1,000 governance tokens. She wants to influence decisions in her DAO but cannot follow every proposal. She delegates her voting power to Bob, a community member who regularly researches proposals and publishes explanations of his voting decisions.

If the DAO uses one vote per eligible token and all 1,000 tokens qualify, Bob can exercise the voting power Alice delegated to him, subject to the DAO's rules.

Alice ordinarily retains ownership of her tokens. Bob receives voting authority, not ownership of the underlying assets.

Why do some governance tokens need delegation?​


Some token-based governance systems distinguish between owning tokens and having activated voting power.

OpenZeppelin's ERC20Votes documentation explains that its voting extension tracks historical voting power through checkpoints. By default, an account's token balance does not automatically count as voting power. Holders generally need to delegate to activate that voting power, including delegating to themselves if they want to vote directly.

This design makes participation explicit and allows the system to record voting power at defined historical points.

The rule is not universal across every DAO. Some use different token contracts, off-chain voting strategies, or alternative governance mechanisms. Always check the specific system's documentation before assuming that holding a token automatically grants active voting power.

For example, the ENS DAO delegation guide explains that $ENS tokens must be delegated to an Ethereum address before they can be used to vote. Delegation can be directed to the holder's own address or another representative.

Delegation, ownership, and voting power are different​


These three concepts should not be confused.


  • []Holding means you own the tokens.
    []Delegating means you assign the associated voting power according to the governance system's rules.
  • Transferring means you move ownership of the tokens to another address.

Delegation ordinarily does not transfer token ownership or give the delegate permission to sell the holder's tokens. It changes who can exercise the associated voting power.

The precise rules depend on the token contract. In some systems, each address can delegate to only one representative at a time. Others support more flexible arrangements, including multi-delegate mechanisms.

Why delegation matters​


Delegation can make governance more accessible, allow participants to specialize in particular policy areas, and encourage better-informed voting.

It can also help communities identify people who consistently contribute research, challenge weak proposals, and explain the consequences of governance decisions.

But delegation is not automatically decentralizing. If most voting power accumulates in a handful of representatives, a DAO may become dependent on a small group even though its tokens are distributed among thousands of holders.

The objective is to make participation easier without removing accountability.

2. Self-Delegation vs. Delegating to Others​


Token holders generally have two broad choices: assign voting power to their own address or delegate it to someone else.

Self-delegation: keeping direct control​


Self-delegation assigns voting power to the holder's own address. It is useful for people who want to research proposals, vote independently, and take direct responsibility for governance decisions.

For example, Alice may want to vote on a proposal that changes a protocol's fee structure. If the governance system requires prior delegation, she can self-delegate and then participate directly.

The main advantage is independence. Alice does not need to trust another person to represent her preferences.

The trade-off is time. She must follow proposals, understand the arguments, meet voting deadlines, and make decisions herself.

Delegating to another representative​


Delegating to another address is useful when a holder wants to participate indirectly through someone who follows governance more closely.

A capable delegate may provide technical knowledge, consistent participation, independent research, and clear voting explanations.

However, a delegate can become inactive, support proposals the holder opposes, or develop financial relationships that affect their judgment.

Delegation should therefore be treated as an ongoing relationship rather than a permanent endorsement.

A practical comparison​



  • []Self-delegation: greater direct control, but usually more research and participation.
    []Delegating to another person: less day-to-day work, but greater dependence on the representative's judgment.
  • Changing delegation: an option when a representative becomes inactive or no longer reflects your priorities, subject to the DAO's rules.

The Arbitrum DAO delegation guide explains that token holders can delegate voting power, change their representative, or reclaim voting power according to the DAO's procedures.

The best choice depends on your available time, expertise, and willingness to follow governance. Neither option is automatically superior.

3. How to Research and Choose a Delegate​


Choosing a delegate is one of the most important decisions a token holder makes. The person or organization receiving your voting power may influence treasury spending, protocol development, security decisions, and the direction of the ecosystem.

A large following or impressive profile is not enough. The strongest evidence comes from a delegate's actual behavior.

A. Examine voting history​


Start with previous votes. Look for consistency, thoughtful participation, and explanations that demonstrate an understanding of the proposal.

Ask yourself:


  • [] Does the delegate participate regularly?
    [] Do they explain why they support or oppose proposals?
    [] Do they identify trade-offs and potential risks?
    [] Do they evaluate proposals independently rather than simply following popular opinion?
  • Do they explain their decisions when community members disagree?

Voting participation is useful, but it should not be treated as the only measure of quality. A delegate who votes on every proposal without researching it may contribute less than someone who carefully evaluates difficult decisions and communicates their reasoning.

B. Read delegate statements​


A delegate statement should explain the representative's priorities, relevant experience, approach to governance, and commitment to participation.

For example, a delegate may prioritize protocol security, treasury sustainability, public goods, or ecosystem growth. These priorities help token holders determine whether the representative's judgment is likely to align with their own.

A useful starting point is the Optimism Collective delegate forum, where delegates publish statements and governance updates. One example is Ezekiel Ekondu's delegate statement, which describes commitments to active participation, thoughtful proposal review, transparent voting rationales, and continued learning.

A statement is a commitment, not proof of performance. Compare what the delegate promises with their actual activity.

C. Check participation beyond voting​


Good governance happens before and after a vote.

Strong delegates may identify weaknesses in proposals, ask questions, participate in community discussions, suggest amendments, and explain implementation risks.

Review three recent proposals and ask:


  • [] Did the delegate contribute to discussions before voting?
    [] Did they identify meaningful risks or alternatives?
    [] Did they explain their final position?
    [] Did they communicate the outcome or follow-up work?

This process helps distinguish representatives who contribute to governance from those who simply cast votes.

D. Investigate conflicts of interest​


Delegates may have financial relationships with protocol teams, grant recipients, service providers, or organizations seeking treasury funding.

These relationships do not automatically make someone a bad delegate. Relevant professional experience can improve decision-making. The problem arises when financial interests are hidden or improperly influence a vote.

Look for clear disclosures, explanations of relevant relationships, and appropriate procedures for handling conflicts.

E. Use real delegate profiles​


The following official resources provide starting points for research across four major ecosystems.


  • [] Optimism: delegate statements and updates. Review published commitments and compare them with voting activity.
    [] Arbitrum: delegation documentation and the DAO FAQ. These explain how representatives participate and how holders can change their delegation.
    [] ENS: ENS delegate profiles on Agora. Profiles can include delegate statements and participation information. For example, the directory includes named participants such as Superphiz.eth and organizational representatives such as coinbase.eth. Review their current records rather than assuming that an old participation figure remains accurate.
    [] Uniswap: Uniswap governance documentation. Use the official governance process to understand UNI delegation and evaluate participating representatives.

These are research starting points, not endorsements of particular delegates. Participation figures and profile information change over time.

A practical delegate-selection checklist​


Before delegating, check whether the representative has a credible record, communicates clearly, discloses conflicts, and understands the proposals they vote on.

The most important question is not simply, "How much voting power does this delegate have?"

It is, "Can I understand and trust the way this delegate uses voting power?"

4. Delegation Platforms: Tally, Boardroom, and Agora​


Governance platforms make it easier to discover delegates, examine proposals, and participate in voting. However, a platform interface is not the same as the governance system itself. Token contracts and DAO rules determine how voting power is calculated and which actions are valid.

Tally​


Tally provides governance interfaces for supported protocols, including tools for examining proposals, exploring delegates, and participating in governance.

Its role and availability vary by DAO and product. Users should begin with their DAO's official documentation and confirm which interface is currently supported.

Boardroom​


Boardroom has provided governance discovery and analytics tools, including delegate discovery, voting information, and proposal tracking.

An example of its use in the Optimism ecosystem is documented in the Optimism governance proposal for Boardroom's Delegate Discovery initiative. The proposal described tools that helped token holders research delegates and compare governance activity.

The wider lesson is that delegate discovery should make it easier to find representatives based on their priorities and contributions, rather than simply ranking them by voting power.

Agora​


Agora provides governance infrastructure and interfaces used by DAOs. The ENS Agora interface, for example, lets users explore ENS governance, view delegates, and examine proposals.

The ENS delegation guide identifies Agora, Tally, and the ENS delegation interface as options for delegating $ENS voting power.

How to use governance platforms safely​



  • [] Start from official DAO documentation rather than an unfamiliar link shared in a message.
    [] Confirm that the platform supports the correct DAO and governance token.
    [] Review the delegate's profile and voting history.
    [] Verify the recipient address before confirming a delegation transaction.
    [] Read the transaction details in your wallet before signing.
    [] Confirm that the delegation was recorded successfully.
  • Never enter your seed phrase into a website to delegate tokens.

A familiar interface does not guarantee that a delegate is trustworthy. Platform security and representative quality are separate questions.

5. Delegate Incentive Programs: Paying for Useful Governance​


Delegates spend time researching proposals, participating in discussions, explaining decisions, and monitoring governance outcomes. These responsibilities can become substantial as a DAO grows.

Incentive programs attempt to compensate contributors for that work and encourage consistent participation. But poorly designed incentives can reward activity without improving decision quality.

Why incentives can help​


A well-designed program can make governance work more sustainable, encourage representatives to publish voting rationales, and lower the financial barrier to participation for people who lack substantial personal resources.

However, rewards should not be distributed simply because a delegate controls a large amount of voting power.

What should rewards measure?​



  • [] Participation in eligible governance votes.
    [] Clear, substantive explanations of voting decisions.
    [] Meaningful involvement in proposal discussions.
    [] Disclosure of relevant conflicts of interest.
    [] Compliance with the program's published rules.
    [] Evidence of sustained contribution over time.

A program that rewards only voting frequency may encourage delegates to vote without conducting adequate research. A program that rewards only delegated token volume may reinforce concentration by directing the largest payments to already powerful representatives.

Transparent eligibility requirements, reasonable caps, public reporting, and periodic evaluation can help reduce these risks.

Real example: Arbitrum's delegate incentives​


Arbitrum provides a concrete example of how incentive programs can evolve. The Arbitrum Foundation's 2025 transparency report describes the Rewarding Active Delegates (RAD) program, an iteration of its earlier Delegate Incentive Program.

The report explains that RAD rewards active delegates based on their voting records and publicly shared voting rationales. It also describes oversight involving the DAO's operating company and a third-party program manager.

This model illustrates an important principle: incentives can reward both participation and the communication that helps token holders evaluate governance decisions.

It does not establish that every incentive program should use the same structure. Each DAO should evaluate its own needs, budget, participation patterns, and risk of gaming.

Real example: ENS delegation incentives​


ENS governance has also considered and approved delegation incentive funding. Its official proposal history includes the Delegation Incentives Program funding proposal and related governance decisions.

This provides a useful example of incentives being handled through formal DAO governance rather than an informal promise from a project team.

Before citing a particular program's current reward amount or eligibility conditions, check the latest proposal and implementation status. Funding decisions can change, and approval of a proposal does not automatically mean that every component remains active indefinitely.

The broader lesson is that incentives should strengthen informed participation without turning voting power into a market for political support.

6. Vote-Buying and Delegation-Capture Risks​


Delegation creates an opportunity for expertise to influence governance, but it also creates incentives for interested parties to accumulate voting power.

Vote-buying and delegation capture are related but distinct problems.

Vote-buying generally involves offering a benefit in exchange for a particular vote or voting commitment. Delegation capture occurs when an individual or coordinated group gains disproportionate influence over governance representatives or voting power.

Both can undermine the independence of a DAO.

Risk 1: Direct vote-buying​


An interested party may offer money, tokens, or another benefit in exchange for a delegate's support of a proposal.

Compensation for legitimate governance work is not automatically vote-buying. The concern is a payment or arrangement intended to purchase a particular voting outcome, especially when it is concealed from token holders.

When voting decisions are influenced by undisclosed payments, public rationales become less reliable and governanc
Your Thread has a good structure and covers the subject well. However, a few corrections are needed before acceptance.

1. Fix the malformed bullet lists throughout the article. Several sections currently display literal [] markers instead of properly formatted lists.

2. Please check the end of the article. The version I'm reviewing appears to stop halfway through a sentence in the vote buying section. Ensure the full section and conclusion are included.

3. Expand the explanation of delegation capture with a practical example showing how a coordinated group could gain disproportionate governance influence.

4. Add a practical walkthrough showing how a token holder can research a delegate, examine their voting history and make an informed delegation decision.

5. Verify the current descriptions and features of Tally, Boardroom and Agora, and ensure the sources support the claims made.

Please address these points and check the formatting throughout before resubmitting.
 

Introduction: Holding Tokens Is Not the Same as Governing​


Decentralized autonomous organizations (DAOs) promise a different approach to decision-making. Instead of leaving every important decision to a central company or a small management team, they allow communities to participate in governing protocols, allocating treasury funds, approving upgrades, and setting long-term priorities.

But decentralization introduces a practical challenge: not every token holder has the time, technical knowledge, or interest required to evaluate every proposal.

A governance proposal might involve a smart contract upgrade, a multimillion-dollar treasury allocation, an incentive program, or a change to a protocol's economic model. Understanding its consequences may require hours of research. Multiply that across several DAOs, and direct participation becomes difficult.

Delegation offers a solution. Token holders can assign their voting power to representatives who actively follow governance and make decisions on their behalf.

However, delegation also introduces new risks. Voting power can become concentrated, delegates can become inactive, and financial incentives can influence how representatives vote.

The important question is therefore not simply how to delegate tokens. It is how to ensure that delegated voting power remains transparent, accountable, and aligned with the people who entrusted it.

This guide explains how delegation works, how to choose a representative, which platforms support governance participation, how delegate incentives operate, and how DAOs can mitigate vote-buying and delegation-capture risks.

1. What Is Delegation, and Why Do Governance Tokens Require It?​


Delegation is the process of assigning the voting power associated with governance tokens to a wallet address. That address may belong to the token holder or to another person, organization, or governance participant.

Consider a simple example.

Alice holds 1,000 governance tokens. She wants to influence decisions in her DAO but cannot follow every proposal. She delegates her voting power to Bob, a community member who regularly researches proposals and publishes explanations of his voting decisions.

If the DAO uses one vote per eligible token and all 1,000 tokens qualify, Bob can exercise the voting power Alice delegated to him, subject to the DAO's rules.

Alice ordinarily retains ownership of her tokens. Bob receives voting authority, not ownership of the underlying assets.

Why do some governance tokens need delegation?​


Some token-based governance systems distinguish between owning tokens and having activated voting power.

OpenZeppelin's ERC20Votes documentation explains that its voting extension tracks historical voting power through checkpoints. By default, an account's token balance does not automatically count as voting power. Holders generally need to delegate to activate that voting power, including delegating to themselves if they want to vote directly.

This design makes participation explicit and allows the system to record voting power at defined historical points.

The rule is not universal across every DAO. Some use different token contracts, off-chain voting strategies, or alternative governance mechanisms. Always check the specific system's documentation before assuming that holding a token automatically grants active voting power.

For example, the ENS DAO delegation guide explains that $ENS tokens must be delegated to an Ethereum address before they can be used to vote. Delegation can be directed to the holder's own address or another representative.

Delegation, ownership, and voting power are different​


These three concepts should not be confused.

  • Holding means you own the tokens.
  • Delegating means you assign the associated voting power according to the governance system's rules.
  • Transferring means you move ownership of the tokens to another address.

Delegation ordinarily does not transfer token ownership or give the delegate permission to sell the holder's tokens. It changes who can exercise the associated voting power.

The precise rules depend on the token contract. In some systems, each address can delegate to only one representative at a time. Others support more flexible arrangements, including multi-delegate mechanisms.

Why delegation matters​


Delegation can make governance more accessible, allow participants to specialize in particular policy areas, and encourage better-informed voting.

It can also help communities identify people who consistently contribute research, challenge weak proposals, and explain the consequences of governance decisions.

But delegation is not automatically decentralizing. If most voting power accumulates in a handful of representatives, a DAO may become dependent on a small group even though its tokens are distributed among thousands of holders.

The objective is to make participation easier without removing accountability.

2. Self-Delegation vs. Delegating to Others​


Token holders generally have two broad choices: assign voting power to their own address or delegate it to someone else.

Self-delegation: keeping direct control​


Self-delegation assigns voting power to the holder's own address. It is useful for people who want to research proposals, vote independently, and take direct responsibility for governance decisions.

For example, Alice may want to vote on a proposal that changes a protocol's fee structure. If the governance system requires prior delegation, she can self-delegate and then participate directly.

The main advantage is independence. Alice does not need to trust another person to represent her preferences.

The trade-off is time. She must follow proposals, understand the arguments, meet voting deadlines, and make decisions herself.

Delegating to another representative​


Delegating to another address is useful when a holder wants to participate indirectly through someone who follows governance more closely.

A capable delegate may provide technical knowledge, consistent participation, independent research, and clear voting explanations.

However, a delegate can become inactive, support proposals the holder opposes, or develop financial relationships that affect their judgment.

Delegation should therefore be treated as an ongoing relationship rather than a permanent endorsement.

A practical comparison​


  • Self-delegation: greater direct control, but usually more research and participation.
  • Delegating to another person: less day-to-day work, but greater dependence on the representative's judgment.
  • Changing delegation: an option when a representative becomes inactive or no longer reflects your priorities, subject to the DAO's rules.

The Arbitrum DAO delegation guide explains that token holders can delegate voting power, change their representative, or reclaim voting power according to the DAO's procedures.

The best choice depends on your available time, expertise, and willingness to follow governance. Neither option is automatically superior.

3. How to Research and Choose a Delegate​


Choosing a delegate is one of the most important decisions a token holder makes. The person or organization receiving your voting power may influence treasury spending, protocol development, security decisions, and the direction of the ecosystem.

A large following or impressive profile is not enough. The strongest evidence comes from a delegate's actual behavior.

A. Examine voting history​


Start with previous votes. Look for consistency, thoughtful participation, and explanations that demonstrate an understanding of the proposal.

Ask yourself:

  • Does the delegate participate regularly?
  • Do they explain why they support or oppose proposals?
  • Do they identify trade-offs and potential risks?
  • Do they evaluate proposals independently rather than simply following popular opinion?
  • Do they explain their decisions when community members disagree?

Voting participation is useful, but it should not be treated as the only measure of quality. A delegate who votes on every proposal without researching it may contribute less than someone who carefully evaluates difficult decisions and communicates their reasoning.

B. Read delegate statements​


A delegate statement should explain the representative's priorities, relevant experience, approach to governance, and commitment to participation.

For example, a delegate may prioritize protocol security, treasury sustainability, public goods, or ecosystem growth. These priorities help token holders determine whether the representative's judgment is likely to align with their own.

A useful starting point is the Optimism Collective delegate forum, where delegates publish statements and governance updates. One example is Ezekiel Ekondu's delegate statement, which describes commitments to active participation, thoughtful proposal review, transparent voting rationales, and continued learning.

A statement is a commitment, not proof of performance. Compare what the delegate promises with their actual activity.

C. Check participation beyond voting​


Good governance happens before and after a vote.

Strong delegates may identify weaknesses in proposals, ask questions, participate in community discussions, suggest amendments, and explain implementation risks.

Review three recent proposals and ask:

  • Did the delegate contribute to discussions before voting?
  • Did they identify meaningful risks or alternatives?
  • Did they explain their final position?
  • Did they communicate the outcome or follow-up work?

This process helps distinguish representatives who contribute to governance from those who simply cast votes.

D. Investigate conflicts of interest​


Delegates may have financial relationships with protocol teams, grant recipients, service providers, or organizations seeking treasury funding.

These relationships do not automatically make someone a bad delegate. Relevant professional experience can improve decision-making. The problem arises when financial interests are hidden or improperly influence a vote.

Look for clear disclosures, explanations of relevant relationships, and appropriate procedures for handling conflicts.

E. Use real delegate profiles​


The following official resources provide starting points for research across four major ecosystems.

  • Optimism: delegate statements and updates. Review published commitments and compare them with voting activity.
  • Arbitrum: delegation documentation and the DAO FAQ. These explain how representatives participate and how holders can change their delegation.
  • ENS: ENS delegate profiles on Agora. Profiles can include delegate statements and participation information. For example, the directory includes named participants such as Superphiz.eth and organizational representatives such as coinbase.eth. Review their current records rather than assuming that an old participation figure remains accurate.
  • Uniswap: Uniswap governance documentation. Use the official governance process to understand UNI delegation and evaluate participating representatives.

These are research starting points, not endorsements of particular delegates. Participation figures and profile information change over time.

A practical delegate-selection checklist​


Before delegating, check whether the representative has a credible record, communicates clearly, discloses conflicts, and understands the proposals they vote on.

The most important question is not simply, "How much voting power does this delegate have?"

It is, "Can I understand and trust the way this delegate uses voting power?"

4. Delegation Platforms: Tally, Boardroom, and Agora​


Governance platforms make it easier to discover delegates, examine proposals, and participate in voting. However, a platform interface is not the same as the governance system itself. Token contracts and DAO rules determine how voting power is calculated and which actions are valid.

Tally​


Tally provides governance interfaces for supported protocols, including tools for examining proposals, exploring delegates, and participating in governance.

Its role and availability vary by DAO and product. Users should begin with their DAO's official documentation and confirm which interface is currently supported.

Boardroom​


Boardroom has provided governance discovery and analytics tools, including delegate discovery, voting information, and proposal tracking.

An example of its use in the Optimism ecosystem is documented in the Optimism governance proposal for Boardroom's Delegate Discovery initiative. The proposal described tools that helped token holders research delegates and compare governance activity.

The wider lesson is that delegate discovery should make it easier to find representatives based on their priorities and contributions, rather than simply ranking them by voting power.

Agora​


Agora provides governance infrastructure and interfaces used by DAOs. The ENS Agora interface, for example, lets users explore ENS governance, view delegates, and examine proposals.

The ENS delegation guide identifies Agora, Tally, and the ENS delegation interface as options for delegating $ENS voting power.

How to use governance platforms safely​


  • Start from official DAO documentation rather than an unfamiliar link shared in a message.
  • Confirm that the platform supports the correct DAO and governance token.
  • Review the delegate's profile and voting history.
  • Verify the recipient address before confirming a delegation transaction.
  • Read the transaction details in your wallet before signing.
  • Confirm that the delegation was recorded successfully.
  • Never enter your seed phrase into a website to delegate tokens.

A familiar interface does not guarantee that a delegate is trustworthy. Platform security and representative quality are separate questions.

5. Delegate Incentive Programs: Paying for Useful Governance​


Delegates spend time researching proposals, participating in discussions, explaining decisions, and monitoring governance outcomes. These responsibilities can become substantial as a DAO grows.

Incentive programs attempt to compensate contributors for that work and encourage consistent participation. But poorly designed incentives can reward activity without improving decision quality.

Why incentives can help​


A well-designed program can make governance work more sustainable, encourage representatives to publish voting rationales, and lower the financial barrier to participation for people who lack substantial personal resources.

However, rewards should not be distributed simply because a delegate controls a large amount of voting power.

What should rewards measure?​


  • Participation in eligible governance votes.
  • Clear, substantive explanations of voting decisions.
  • Meaningful involvement in proposal discussions.
  • Disclosure of relevant conflicts of interest.
  • Compliance with the program's published rules.
  • Evidence of sustained contribution over time.

A program that rewards only voting frequency may encourage delegates to vote without conducting adequate research. A program that rewards only delegated token volume may reinforce concentration by directing the largest payments to already powerful representatives.

Transparent eligibility requirements, reasonable caps, public reporting, and periodic evaluation can help reduce these risks.

Real example: Arbitrum's delegate incentives​


Arbitrum provides a concrete example of how incentive programs can evolve. The Arbitrum Foundation's 2025 transparency report describes the Rewarding Active Delegates (RAD) program, an iteration of its earlier Delegate Incentive Program.

The report explains that RAD rewards active delegates based on their voting records and publicly shared voting rationales. It also describes oversight involving the DAO's operating company and a third-party program manager.

This model illustrates an important principle: incentives can reward both participation and the communication that helps token holders evaluate governance decisions.

It does not establish that every incentive program should use the same structure. Each DAO should evaluate its own needs, budget, participation patterns, and risk of gaming.

Real example: ENS delegation incentives​


ENS governance has also considered and approved delegation incentive funding. Its official proposal history includes the Delegation Incentives Program funding proposal and related governance decisions.

This provides a useful example of incentives being handled through formal DAO governance rather than an informal promise from a project team.

Before citing a particular program's current reward amount or eligibility conditions, check the latest proposal and implementation status. Funding decisions can change, and approval of a proposal does not automatically mean that every component remains active indefinitely.

The broader lesson is that incentives should strengthen informed participation without turning voting power into a market for political support.

6. Vote-Buying and Delegation-Capture Risks​


Delegation creates an opportunity for expertise to influence governance, but it also creates incentives for interested parties to accumulate voting power.

Vote-buying and delegation capture are related but distinct problems.

Vote-buying generally involves offering a benefit in exchange for a particular vote or voting commitment. Delegation capture occurs when an individual or coordinated group gains disproportionate influence over governance representatives or voting power.

Both can undermine the independence of a DAO.

Risk 1: Direct vote-buying​


An interested party may offer money, tokens, or another benefit in exchange for a delegate's support of a proposal.

Compensation for legitimate governance work is not automatically vote-buying. The concern is a payment or arrangement intended to purchase a particular voting outcome, especially when it is concealed from token holders.

When voting decisions are influenced by undisclosed payments, public rationales become less reliable and governance legitimacy suffers.

Risk 2: Concentrated voting power​

Imagine a DAO with 100 million eligible votes, of which three delegates collectively control 60 million.
That concentration does not prove wrongdoing. Holders may have delegated voluntarily because they trust those representatives. Nevertheless, it creates systemic risk if the delegates coordinate improperly, become compromised, or stop representing their constituents' interests.
A healthy governance system should make concentration visible and allow token holders to reconsider their delegation choices.

Risk 3: Coordinated delegation capture​

A team, investor group, or organized interest may encourage holders to delegate to selected addresses. If enough voting power accumulates, the group may influence treasury decisions, protocol upgrades, or changes to governance rules.
Warning signs include undisclosed relationships, misleading claims about delegate independence, opaque coordination, and rewards conditioned on specific voting outcomes.
Delegation campaigns are not inherently improper. The important distinction is whether participants can understand who is coordinating the campaign, what incentives exist, and how representatives intend to vote.

Risk 4: Last-minute changes to voting power​

If a governance system permits voting power to change before a relevant snapshot, a sudden movement of tokens or delegation may alter the apparent balance of support.
The precise risk depends on the implementation. Historical voting checkpoints and clearly defined snapshots can limit some forms of manipulation, but they do not eliminate bribery, collusion, or long-term concentration.

How DAOs can mitigate these risks​

  • Public delegate statements: Make voting histories, commitments, and relevant relationships easier to inspect.
  • Transparent incentives: Publish funding sources, eligibility rules, reward calculations, and conflict-of-interest policies.
  • Historical checkpoints: Use appropriate mechanisms to record voting power at defined points in time.
  • Clear deadlines: Communicate snapshot times and delegation rules before voting begins.
  • Concentration monitoring: Publish information about the distribution of voting power across representatives.
  • Independent analysis: Encourage public discussion and scrutiny of important proposals.
  • Appropriate governance safeguards: Consider quorum requirements, timelocks, proposal thresholds, or additional review procedures where they fit the protocol.
No single safeguard solves every problem. For example, a snapshot can help prevent certain last-minute changes but cannot prevent a delegate from accepting a bribe. Likewise, a high quorum may reduce the risk of a small group passing a proposal, but excessively high thresholds can make governance ineffective.
Safeguards should be matched to the actual threat rather than added without considering their costs.

7. Re-Delegation and Vote-Weight Snapshots​

Delegation is not necessarily permanent. In many systems, token holders can change representatives, but the timing and effect depend on the DAO's rules and implementation.

How re-delegation works​

Suppose Alice delegates her voting power to Bob. After several months, Bob stops participating in governance.
Alice can review other delegates, select a more suitable representative, and change her delegation if the governance system supports that operation.
In systems that support self-delegation, she may also reclaim voting power for direct participation. Re-delegation generally changes the assignment of voting rights rather than transferring ownership of the tokens.
The Arbitrum delegation documentation explains how token holders can change or revoke their delegation. The ENS delegation guide similarly states that delegation can be changed.
A holder should verify the actual transaction requirements and the effect of a change on any ongoing proposal.

What is a vote-weight snapshot?​

A snapshot records voting power at a defined point in time. Depending on the governance system, that point may be represented by a blockchain block number, timestamp, or another specified reference.
Consider this simplified example:
  • Alice holds 1,000 GOV.
  • Before a proposal's snapshot, she delegates her voting power to Bob.
  • At the relevant snapshot, the governance system records Bob's eligible voting power.
  • Alice later changes her delegation.
In a system that uses historical voting checkpoints, the later change does not necessarily alter the voting power recorded for the existing proposal. The proposal may continue to use the historical record associated with its designated timepoint.
This separation helps ensure that voting weight is calculated according to a defined rule rather than changing unpredictably during a vote.

Snapshot time is not the voting deadline​

These are different concepts.
The snapshot determines which voting power is counted under the proposal's rules. The voting period determines when participants can cast their votes.
A holder who delegates after the relevant snapshot may not contribute voting power to that proposal. Similarly, a later re-delegation may not change the historical voting weight already recorded.
OpenZeppelin's Governor documentation explains how governance systems can use historical voting power from vote-enabled token contracts.
Before participating, check:
  • When voting power is measured.
  • Whether the system uses historical checkpoints or another voting strategy.
  • When a delegation change becomes effective for the relevant proposal.
  • Whether the holder can vote directly after changing delegation.
  • Whether the proposal is on-chain, off-chain, or governed by a combination of mechanisms.
Understanding these details can prevent token holders from assuming that a delegation transaction automatically gives them voting power in every ongoing proposal.

8. What Better Delegation Should Look Like in 2026​

Delegation should not be judged solely by how many tokens have been assigned to representatives. A DAO can have substantial delegation participation and still suffer from weak accountability.
A stronger approach evaluates the entire governance relationship.

For token holders​

Treat delegation as an active choice. Research representatives, read their explanations, review their participation, and change your delegation if their conduct no longer meets your expectations.
You do not need to become a full-time governance researcher. Even periodically reviewing important proposals can help you decide whether your delegate remains aligned with your priorities.

For delegates​

Treat delegated voting power as a responsibility rather than a personal achievement.
Publish your reasoning, acknowledge uncertainty, disclose relevant conflicts, and explain when you change your position. If you cannot adequately review a proposal, communicate that limitation rather than presenting an uninformed vote as a researched decision.
Technical expertise is most useful when it can be translated into clear explanations that ordinary token holders can understand.

For DAO governance teams​

Make delegation easier to understand and safer to use.
Provide accessible documentation, clear voting timelines, searchable delegate records, and transparent information about incentive programs. Monitor voting-power concentration and evaluate whether the governance process allows token holders to hold representatives accountable.
Where possible, publish participation data without reducing every contribution to a simplistic performance score.
A healthy governance system should help participants answer three questions:
  • Who currently exercises voting power?
  • Why are they voting the way they are?
  • What can token holders do if they disagree with their representatives?
If those answers are difficult to find, the DAO has an accountability problem even if its voting contracts function as designed.

Conclusion: Delegation Is a Relationship, Not a Transaction​

Delegation solves a real coordination problem. It allows token holders to participate in complex governance without researching every proposal themselves, while enabling experienced contributors to specialize in protocol decisions.
But delegation also changes how power is distributed. Voting power can become concentrated, incentives can distort behavior, and holders can lose visibility into decisions that affect their assets and communities.
The answer is not to reject delegation. It is to practice and design it responsibly.
Token holders should select representatives based on evidence rather than popularity alone. Delegates should communicate their reasoning and disclose conflicts. Governance teams should design incentive programs carefully, monitor concentration, and establish clear rules for snapshots and re-delegation.
Most importantly, token holders should remember that delegation does not eliminate their responsibility to the DAO. It changes how they exercise that responsibility.
A healthy DAO does not merely distribute voting power. It makes that power understandable, contestable, and accountable.
That is the real test of decentralized governance in 2026: not whether people can delegate their votes, but whether the resulting system continues to serve the community that entrusted those votes in the first place.

Sources and Further Reading​

Editorial note​

Governance rules, platform availability, delegate participation, and incentive programs can change. Readers should confirm current DAO-specific documentation and proposal status before making decisions. Examples in this article illustrate governance practices; they are not endorsements of individual delegates or financial advice.
@Diornov I've edited it
 
Back
Top