# The State of DAO Delegate Compensation Today

*Exploring the Evolving Landscape of DAO Delegate Compensation*

By [Sharing is Caring](https://paragraph.com/@sharingiscaring) · 2026-07-02

dao, governance, delegates

---

Introduction
------------

Three years ago, delegate compensation felt like part of DAO governance’s natural progression. Protocols were launching DAOs, tokenholders needed representation, and delegates were emerging as the people willing to do the work.

Since then, the picture has changed. Many DAOs reduced governance scope, cut delegate programs, or centralized decision-making back to core teams. The first wave of DAO governance exposed real problems: low participation, unclear accountability, performative forum activity, and difficulty proving ROI.

But delegate compensation has not disappeared.

Compound, Arbitrum, Rootstock, and Shutter show that some DAOs still see value in paying delegates — not as a symbolic nod to decentralization, but because shared infrastructure still requires informed decision-making around treasury allocation, protocol upgrades, ecosystem priorities, and credible neutrality.

Delegates are imperfect, but they solve a real coordination problem: most tokenholders are not going to track every proposal, evaluate every tradeoff, or show up for every governance decision that may affect them.

I have seen this firsthand.

Most tokenholders are not checking governance forums every week. They are not reading every proposal. They are sometimes not even aware of key votes, even when those decisions may affect their business. **Delegates help fill that gap by turning passive token ownership into informed representation — at least when the delegate role is taken seriously.**

When I wrote about [delegate compensation](https://paragraph.com/@tally-2/a-new-approach-to-reward-dao-delegates) three years ago at Tally, now Cactus, the conversation was still early. Today, the better question is not whether DAOs should pay delegates. **It is what DAOs are actually paying for.**

Decentralization still matters, but the bar is higher
-----------------------------------------------------

In the past, launching a DAO was sometimes treated as a decentralization signal. A protocol could launch a token, a governance system, create a forum website, and claim the project was now community-led.

That framing is aging poorly.

Emerging U.S. market structure legislation, including the CLARITY Act, suggests that decentralization may still matter — but not as a branding exercise. The [introduced bill](https://www.congress.gov/bill/119th-congress/house-bill/3633/text/rs) defines **a decentralized governance system as a "transparent, rules-based system for reaching consensus around the development, publication, management, or administration of a blockchain system, where participation is not limited to or effectively controlled by one person or group under common control."**

This does not mean that having a DAO is a regulatory shortcut. It points in the opposite direction: if decentralization is relevant, the quality of governance becomes more important. A protocol needs to show that control is meaningfully distributed, that governance is legible, and that participation is not just nominally open but practically concentrated in the hands of insiders.

_This is not legal advice, and the final legislative framework may change. But the broader governance point is clear:_ **_if decentralization continues to matter, then serious governance participation matters too._**

Compound DAO
------------

![](https://storage.googleapis.com/papyrus_images/9e3491d028e20cec401d93feed39d0880da294b224e50b6fefc17f97edcaf99a.png)

Compound is one of the clearest examples of a DAO formalizing expectations around delegate participation.

Its current approach has two related pieces: [treasury delegation](https://www.comp.xyz/t/compound-delegate-race-cycle-2/7302) and [delegate compensation](https://www.comp.xyz/t/delegate-compensation-program-initial-6-month-term/7712).

For treasury delegation, eligible delegates are evaluated based on voting history to determine who can receive delegated voting power from the treasury. Delegates who receive a treasury delegation are expected to maintain at least 80% onchain vote participation over a six-month period, calculated by the Compound Growth Working Group. If a delegate falls below that threshold, their voting power can be revoked through an onchain vote and reassigned to another active delegate.

Compound has also proposed an initial six-month Delegate Compensation Program. The proposal frames compensation as a response to declining participation and engagement, especially in a DAO with high proposal volume and technical complexity. Eligible delegates must maintain sufficient delegated voting power, keep a public delegate statement, follow the Governance Code of Conduct, and provide public voting rationales. The program compensates top eligible delegates based on voting participation and substantive public forum communication, with oversight and a review before renewal.

Compound’s model is measurable and administratively clear. It rewards the baseline work of governance: voting, communicating, and staying accountable to tokenholders.

It also shows the limits of the current model. **The metrics are objective, but they mostly measure governance participation. That is a necessary starting point, but it is not the full expression of delegate impact.**

Arbitrum DAO
------------

![](https://storage.googleapis.com/papyrus_images/e9f3e00603c6f126d719fdfaded502fbcde0730d3cfbadc5b67d298c4e35b5f5.png)

Arbitrum shows a different version of the same trend.

Arbitrum governance has gone through pauses, tensions, redesigns, and now renewed activity. Today, the DAO is not moving away from governance as much as it is trying to make governance more operationally coherent.

The [“Vision for the Future of Arbitrum”](https://forum.arbitrum.foundation/t/a-vision-for-the-future-of-arbitrum/28962) post describes an ecosystem of Arbitrum Aligned Entities and teams. The core idea is that the ArbitrumDAO should remain the source of power: delegates and tokenholders should continue to control technical upgrades and treasury disbursements. But execution should increasingly move through aligned entities with clearer mandates, accountability, and responsibility for delivery.

That is an important shift.

It recognizes that large DAOs cannot ask tokenholders and delegates to manage every operational decision directly. Delegates should not be expected to negotiate every vendor scope, manage every workstream, or serve as the collective counterparty for every service provider. Their role becomes more focused: a**pprove or reject budgets, evaluate aligned entities, maintain oversight, and make sure execution remains connected to the DAO’s mission and goals.**

Arbitrum also has a clearer delegate incentive path through the [Rewarding Active Delegates program](https://forum.arbitrum.foundation/c/dao-grant-programs/rewarding-active-delegates-program-rad/72). At the same time, broader contributor pathways remain unresolved. I proposed contributor pathways through my research on an [Arbitrum DAO Contributor Program](https://forum.arbitrum.foundation/t/arbitrum-dao-contributor-program-validation-research-report/30788), however executing on this research is not currently a priority for the DAO.

Professionalization can clarify some roles while leaving other forms of contribution undefined. Arbitrum has more structure around delegates and execution entities, but **operationalizing support from valuable external contributors remains a to-do item.**

For delegate compensation, the lesson is that programs cannot be designed in isolation. They sit inside a broader operating system of stakeholders: foundations, aligned entities, service providers, contributors, and tokenholders. **The more professional DAO structures become, the more important it is to define what delegates are uniquely responsible for.**

Rootstock Collective
--------------------

![](https://storage.googleapis.com/papyrus_images/6c5f564d82c7fc31c4bed6d98f7e80db6c9f54ff602f397aa019f1ea2ffaa8a4.png)

Rootstock’s [recognized delegate compensation program](https://gov.rootstockcollective.xyz/t/new-delegate-compensation-scheme/849) is another active example.

The current program is designed to incentivize active participation and thoughtful governance. Delegates qualify by writing rationales for at least 90% of their votes cast, having more than 50,000 stRIF delegating, and at least 3 hours of read time on the forum.

The total amount is distributed among all qualifying delegates in such a way that the bottom ranked delegate receives 30% less than the top ranked delegate.

This is a strong participation-based model. It is simple, transparent, and designed to prevent coasting. Delegates know what is expected of them, and the community can see whether those expectations are being met.

But Rootstock also shows where the conversation is heading next.

In [delegate discussions and research](https://gov.rootstockcollective.xyz/t/additional-contributions-from-delegates-a-discussion-thread/770?u=axia) that I conducted, there was interest in expanding beyond grant review and baseline participation toward contribution lanes tied to ecosystem priorities. These lanes have not been adopted yet, but I did recently re-surface [the discussion.](https://gov.rootstockcollective.xyz/t/new-delegate-compensation-scheme/849/20?u=axia)

Possible contribution areas for delegates include liquidity introductions, strategic introductions, marketing, events with KPIs, RIF adoption, and content. The stronger version would start with 2–3 North Star priorities, design 1–2 concrete pilots, measure whether they move the needle, and compensate what works.

Rootstock’s current program rewards active governance. The next question is whether recognized delegates can also help advance protocol growth in measurable ways.

Shutter DAO 0x36
----------------

![](https://storage.googleapis.com/papyrus_images/b5c4d02b1f7a023c3edc455e2c38d12f7b4a1028bfde72b9d60802f0fe115a5f.png)

Shutter is the most forward-looking example, but it has not yet an adopted program.

I submitted the [Shutter Delegate Impact Pilot + AI Agent Bounty](https://shutternetwork.discourse.group/t/shutter-delegate-impact-pilot-ai-agent-bounty/889) as a funding slate. Tokenholders still need to vote and decide which of the submitted slates to fund.

The proposal is a 12-week pilot to reward delegates for measurable ecosystem impact across three areas: governance participation, idea origination, and business development. The framing is specific to Shutter’s needs. Shutter is open-source cryptographic infrastructure for fairer blockchain systems. Its threshold encryption protocol helps protect users from malicious MEV, vote manipulation, and information asymmetry by keeping sensitive information encrypted until it is ready to be revealed. **As Shutter advances encrypted mempool work through EIP-8184 / LUCID, the ecosystem needs more than technical development. It needs active delegates who can help governance function, generate useful ideas, and create paths for adoption.**

The slate also includes AI agent bounties to support delegate impact. Proposed ideas for agents include an EIP-8184/LUCID monitor, a public goods narrative agent, and a scout agent to identify dApps where Shutter’s encryption features could be useful.

Shutter is useful because it shows where delegate compensation could go next. **Instead of only asking whether delegates voted, the pilot asks whether delegates can help the protocol create useful outputs: better governance, better ideas, more integrations, and stronger ecosystem awareness.**

The point is not to assume impact-based compensation is easy, but rather to test it directly.

What today’s delegate compensation programs reveal
--------------------------------------------------

The current state of delegate compensation is uneven, but there is a clear pattern.

Adopted programs still tend to reward governance activity: voting participation, written rationales, public communication, engagement, and visible accountability. These metrics are useful because they are objective and easy to evaluate. They establish a baseline. If a delegate is being paid by a DAO, they should vote, explain their reasoning, and be available to the community.

But those metrics are not enough.

**A delegate can vote on every proposal and still add little strategic value. A delegate can write rationales that sound good but are not especially useful**. **A delegate can show up often without helping the protocol grow, attract builders, improve adoption, or make better decisions.**

The next generation of delegate compensation should preserve participation requirements, but add protocol-specific contribution metrics. Different DAOs need different things. A lending protocol may need risk review and parameter expertise. An L2 may need ecosystem strategy and oversight of aligned entities. A privacy protocol may need integrations, developer education, and use case discovery. A grants-heavy DAO may need evaluation, accountability, and follow-through.

**The best programs will not ask only, “Did this delegate show up?” They will ask, “What did this delegate help the protocol do?”**

Professionalization without capture
-----------------------------------

As expectations rise, DAOs may need to professionalize how they work with delegates.

That does not mean delegates should become employees of the protocol, foundation, or core team. Their independence is part of their value. Delegates need to be able to disagree publicly, vote against insiders, and represent tokenholders rather than management.

But the opposite extreme is also weak. The idea that delegates are just casual community members breaks down once DAOs expect recurring, skilled, accountable work. If delegates are sourcing integrations, reviewing proposals, advising on ecosystem growth, representing stakeholder groups, or helping with business development, some of that work begins to look more like a contractor relationship.

DAOs already have models they can borrow from the traditional world: scopes of work, deliverables, confidentiality agreements, conflict disclosures, payment terms, renewal reviews, and termination rights. Some DAOs already ask delegates or contributors to sign NDAs for sensitive work. That is not inherently a problem. Clients ask contractors to sign NDAs all the time.

**The risk is using professionalization to move governance into private rooms.** NDAs may be appropriate for partnership discussions, security-sensitive information, or integration pipelines. They should not become a way to hide governance reasoning from tokenholders.

**The goal should be more context and accountability, not delegate capture**. **DAOs can treat delegates more professionally while still preserving public reasoning, independent judgment, and conflict transparency.**

Token price is a signal, not the scoreboard
-------------------------------------------

It is understandable that protocols want delegate work to connect to tokenholder outcomes. If governance is allocating capital, shaping strategy, and supporting adoption, tokenholders should care whether that work contributes to protocol value.

But token price is too noisy to be a clean delegate compensation metric. It reflects market cycles, liquidity, macro conditions, narrative, speculation, and many factors outside a delegate’s control. It can also incentivize short-term decision-making at the expense of durable protocol health.

**A better approach is to reward inputs delegates can credibly influence: integrations sourced, builders introduced, proposals improved, ecosystem relationships created, grants evaluated, adoption milestones supported, governance participation increased, or risks identified before they become expensive.**

Token price may be one signal that the market believes a protocol is becoming more valuable, but should not be the scoreboard for delegate compensation.

Conclusion
----------

Delegate compensation is not dead. It is becoming more demanding.

Compound and Rootstock show that participation-based programs are still active and useful. Arbitrum shows how delegate incentives sit inside a broader shift toward professional DAO operating structures. Shutter shows the design frontier: compensation tied to measurable ecosystem impact (pending a tokenholder vote).

Together, these examples suggest that the first version of delegate compensation was too narrow. Paying delegates to vote and write rationales may improve baseline governance, but it does not fully answer what protocols need from their most active representatives.

**The next generation of delegate compensation should reward delegates not for occupying governance seats, but for helping protocols make better decisions, attract more builders, grow adoption, and maintain credible decentralization.**

That is the opportunity for DAOs designing or revisiting delegate programs today. Do not copy-paste the last program. Start with the protocol’s actual needs. Define the work. Measure what can be measured. Preserve delegate independence. Then compensate what helps the protocol move forward.

---

*Originally published on [Sharing is Caring](https://paragraph.com/@sharingiscaring/the-state-of-dao-delegate-compensation-today)*