Contributor compensation is how a DAO pays the people who build, maintain, and govern it. It is one of the hardest operational problems a DAO faces, because a DAO has no employer of record: there is no company to sign an employment contract, run payroll, withhold taxes, or offer benefits. Instead, every payment comes out of the shared treasury and must ultimately be authorized through governance — which turns "paying a teammate" into a public, on-chain, community-approved act. Because compensation is typically the single largest recurring outflow from a treasury, how a DAO answers this question directly determines its runway and its survival.

Ways DAOs pay contributors

No single model dominates; most mature DAOs run several at once, matched to the type of work. Whichever the DAO picks, the payment still has to leave the treasury with a paper trail behind it — invoicing and accounts-payable tooling such as Request Finance is the layer that turns an approved budget into bills, approvals and books.

• Salaries and streaming. Ongoing roles are paid a recurring wage, increasingly as a real-time stream rather than monthly lump sums — protocols like Superfluid let a DAO pay by the second and cancel the stream the moment a contributor stops, so pay tracks work continuously instead of in arrears.
• Bounties and task-based pay. Discrete, scoped deliverables are posted with a fixed reward and paid on completion — low-commitment, easy to open to newcomers, but weak for retaining long-term contributors.
• Grants. The DAO funds an external team or working group to build something, usually against milestones. Quadratic-funding rounds such as Gitcoin let a community's small donations decide allocations rather than a committee.
• Retroactive funding. Pay after impact is proven rather than promised. Optimism's Retro Funding (RetroPGF) has distributed tens of millions of OP to contributors whose work already shipped, inverting the risk of speculative up-front grants – though Optimism paused the programme in January 2026 for at least twelve months, so the model is currently better evidenced than it is available.
• Peer allocation. Contributors decide each other's pay. Coordinape runs "circles" in which each member distributes a fixed budget of GIVE tokens per epoch to the peers whose contributions they valued, converting distributed judgment into a reward split.

Organizing the work behind the pay

Compensation only makes sense once responsibility is scoped, so DAOs wrap work in structures that a budget can attach to. Working groups and guilds gather contributors by function — design, engineering, governance, treasury — and receive a periodic budget they allocate internally. Larger organizations spin off sub-DAOs: semi-autonomous units with their own mandate and multisig, funded by the parent but free to run their own compensation. This lets a DAO delegate the messy, high-frequency work of paying people down to the smallest group that actually has the context to judge contribution, while the top-level proposal process only ratifies the aggregate budget.

What those structures cost to run, once compensation, legal retainers and tooling are added up, is set out with published figures on DAO governance operating costs.

Paying in the native token

DAOs frequently pay part of compensation in their own governance token, which is attractive on paper: it costs no stablecoins, and it turns contributors into voting stakeholders whose incentives point at the protocol's long-term value. The costs are real, though. Contributors carry the token's price volatility as personal income risk; unvested grants can create heavy sell pressure when they unlock; and paying core work in a governance token quietly concentrates voting power in the hands of insiders. The standard mitigation is vesting — multi-year schedules with a cliff — which aligns contributors with a time horizon longer than the next token pump, at the cost of locking up income they cannot spend. Most healthy programs blend a stablecoin base (to pay rent) with a vesting token grant (to align upside). The same exposure runs through governance payroll: delegate incentive programs that set budgets in dollars but pay in the governance token spend the most tokens exactly when the token is cheapest, which is what forced Arbitrum to cut its per-proposal budgets 28–40% in July 2026. The constraint reads more clearly in the DAO that cannot use the lever: Beefy's supply is fixed at 80,000 tokens with no mint function and nothing left undistributed, so its entire $145,500-a-month contributor budget is paid in stablecoins out of vault revenue. A DAO with no seigniorage has no soft option.

The unsolved problems

Even well-run compensation systems wrestle with the same open tensions:

• Valuation and fairness. Without managers or market salaries, deciding what a contribution is worth is genuinely hard; peer-allocation and retroactive systems are attempts to distribute that judgment, but both can reward visibility over substance. Protocol Guild takes the other route and declines to judge at all, paying ~184 Ethereum core maintainers on a formula of tenure and full- or part-time status alone — objective and hard to game, at the cost of being unable to tell a decisive contributor from a merely present one. Its own ops team has since drafted an "impact weighting" alternative, which would reintroduce exactly the judgment the formula was built to avoid.
• Churn and burnout. Contributors can leave instantly with no notice period, and pseudonymous, part-time work makes retention harder than in a firm.
• Legal and tax status. With no employer, contributors are typically self-employed across many jurisdictions, and the DAO itself may lack a legal wrapper to contract or withhold — an unresolved compliance gray zone.
• Transparency vs. privacy. On-chain pay is fully public by default, which aids accountability but exposes every contributor's income to the world.
• Sustainability. Compensation is usually the biggest drain on the treasury; a DAO that over-commits to salaries in a bull market can run out of runway when its token falls.

How Caper approaches this

Caper does not add a separate payroll layer — it pays contributors through the same governance path as any other treasury spend. A member submits a payout proposal naming a recipient, a currency, and an amount; if the caper votes it through and its market does not veto it in the market window that follows, execution transfers exactly that currency and amount from the caper's treasury straight to the recipient's account. There is no privileged spending key and no off-chain invoice: every payment to a contributor is a proposal the whole caper approved and can see on-chain. Recurring pay is simply repeated payouts rather than a bespoke streaming primitive, which keeps the rule the same for a one-off bounty and an ongoing salary — the treasury only ever moves when a proposal says it should.