What a service provider is

A DAO service provider is an outside firm paid by a DAO to run a defined part of its operation — indexing, treasury management, protocol engineering, growth, governance analytics. It is a distinct category from the two things it is usually confused with. A grantee is funded to build something of its own that the DAO would like to exist; a service provider is funded to deliver a service to the DAO, and the DAO is the customer. A contributor is a person the DAO compensates directly; a service provider is a firm with its own payroll, its own other clients (or a contractual promise not to have any), and its own commercial interest in being renewed.

That last property is what makes this a governance topic rather than a procurement footnote. A DAO that buys operating capability from a firm has created a counterparty with a durable incentive to keep the engagement alive, more information about the DAO's operations than most delegates have, and — in the mature cases — a hand in designing the process by which its own renewal is decided. The published cost of these engagements is covered on DAO governance operating costs. This page is about the relationship: how the firm is chosen, on what terms it is held, and what actually happens when the DAO wants out.

Model one: the open programme with a selection committee

ENS DAO's Service Provider Program is the most fully specified version of this model, and its third season is instructive because the DAO wrote down the rules before running the process. The SPP3 authorization does four things in one vote: it authorizes a single cycle (renewal requires a new DAO vote, and the proposal states plainly that nothing in it commits the DAO to future seasons), it fixes the eligibility test (the primary deliverable must be a service to ENS; projects whose value accrues mostly elsewhere are ineligible), it names the committee that will execute the selection, and it caps the budget at 20% of trailing protocol revenue rather than at a fixed number.

Splitting authorization from selection is the design choice worth copying. SPP3 requires two votes from delegates: one to approve the programme, budget and committee, and a second to ratify the cohort the committee returns with. The stated reason is that the earlier season made delegates rate and rank every applicant themselves, which the proposal describes as a structural problem rather than a one-off inconvenience. Delegates are asked to judge a process and a panel, which they can do, instead of twenty-six commercial proposals, which they cannot.

The cohort recommendation shows the funnel that produced: 26 applications requesting a combined $12.2M against roughly $3.25M available; one disqualified at the eligibility gate; the remaining 25 scored against the published rubric with a structured interview for each qualifying team. The committee recommended four providers — Namespace ($500,000), Goldsky ($450,000), Unruggable ($400,000) and Fluidkey ($340,000), totalling $1,690,000 — and published its assessment of each, plus an aggregate explanation of why the rest were not funded. One committee member recused from evaluating and voting on a provider under the programme's conflict-of-interest rules, which is the minimum viable form of the disclosure this model needs.

Model two: the exclusive mandate

Arbitrum DAO's arrangement with Entropy Advisors runs the opposite way: one firm, no cohort, and exclusivity written into the title of the renewal proposal. The firm was bootstrapped by an Arbitrum Foundation grant and works only for this DAO, which buys deep context at the price of having no comparator — there is no second bidder to price against and no obvious way to run a counterfactual.

What the DAO bought instead is an alignment and termination structure. The renewal's 15M ARB alignment allocation was revised mid-discussion into two parts: 5M ARB to the firm on a one-year cliff and three-year vest, and 10M ARB reserved for the oversight committee to negotiate against milestones, KPIs, equity or time-based bonuses rather than paid out on signature. The termination language was clarified in the same revision: if the DAO ends the relationship, all unearned ARB from that 10M returns to the treasury. Structurally this is the answer to exclusivity — if you cannot create competitive pressure at selection, create it at the vesting cliff.

Note also what the revision says about who the firm answers to. Once the DAO's operating company is sufficiently operationalized, it becomes the firm's counterparty and client, acting as a proxy for the DAO. The DAO stops being the direct commercial counterparty to its own strategy firm — which is model three.

Model three: the operating company as counterparty

The OpCo proposal makes the DAO's procurement problem explicit before solving it: a DAO is structurally slow at evaluating and engaging specialised contributors, initiatives often have no clear owner, and when a service provider disengages there is frequently nobody accountable for continuity. OpCo is a DAO-adjacent legal entity that hires staff and negotiates with service providers on the DAO's behalf — an operational layer that exists so the DAO does not have to be a counterparty to every engagement it depends on.

The interesting part is the drawdown ladder, because it is a governance mechanism disguised as a finance control. The proposal earmarked 30M ARB (explicitly subject to change between the Snapshot and Tally votes) to cover the first 30 months, of which 4M ARB forms a vesting, performance-linked bonus pool for internal employees and the oversight committee, and most of the remainder is liquidated until $12M in cash equivalents is reached, with the leftover ARB returned to the treasury. Against that balance: $2.5M released upfront, then up to $500K per month drawn freely, $500K–$1.5M requiring the oversight committee's approval, and anything above $1.5M requiring a Snapshot vote of the DAO. The entity is fast by default and slow exactly where the amounts get large enough to matter — the same graduated-threshold logic that appears in treasury management and in subDAO mandates.

The test is what happens when the process is inconvenient

Every procurement model looks sound in its authorizing proposal. The signal comes from the first time following it costs the DAO something. SPP3 supplies a clean instance. The committee's cohort originally had five selectees; the provider chosen for the marketplace and revenue vertical declined its award, leaving that vertical unfilled and $1,560,284 of authorized budget uncommitted.

The committee had an easy route available and said so publicly: go back to the applicants it had already scored and renegotiate scope privately. It declined to, on the grounds that SPP3 ran under one published rubric and one deadline that every applicant had agreed to, and that operating outside those bounds would not be in the programme's interest. Instead it proposed an open, tightly scoped RFP for the unfilled vertical, funded from money the DAO had already authorized: a single award of up to $500,000, milestone-gated, with roughly half streamed through go-live and half released against traction gates verifiable on-chain, and the balance returned to the treasury.

Three properties are worth naming, because they are what a DAO should look for in any procurement it approves. The remedy asked for no new money. It did not delay the four ratified providers. And it converted an awkward vacancy into another run of the same public process rather than a private conversation among people who already had the DAO's confidence.

Where it goes wrong

• Renewal by default. The strongest single guard in the ENS model is that authorization expires: the programme is one cycle and a new season needs a new vote. Where an engagement rolls over unless someone objects, the burden of proof has quietly moved from the provider to the delegates — and the participation levels of most DAOs make that burden decisive.
• Incumbency. A returning provider has delivery history, relationships with the committee, and a scope written in the language the DAO now uses. Some of that is genuine earned advantage. It is very hard to tell how much from outside, which is why published rubrics and scores matter more than the identity of the winners.
• Information asymmetry. The firm running a DAO's data infrastructure knows the DAO's numbers better than the delegates voting on its renewal. Mandatory transparency reporting, and a foundation or committee entitled to request them, is the standard mitigation.
• Exclusivity with no comparator. Buying a firm's undivided attention removes the market test at selection. The mitigation is at the other end: long cliffs, milestone-gated tranches, and unearned tokens returning to the treasury on termination.
• Capture of the process itself. The failure worth guarding against is not overpayment; it is a provider whose advice shapes the mandate under which its own performance is later judged. Conflict-of-interest recusal, published rubrics, and separating the body that writes the programme from the body that wins it are the available defences. See How DAOs fail for the wider pattern.

How Caper approaches this

Caper has no service-provider layer, and that is a real answer rather than a gap being talked around. There is no delegate, steward, council or committee class anywhere in the contracts, and no streaming, vesting or recurring-payment primitive: a payment is a proposal option of the PAYOUT kind carrying a currency, an amount and a recipient account, and settlement of a passing proposal is the transfer.

The consequence for this topic is narrow and specific. A multi-season engagement cannot be expressed as one on-chain object, so it decomposes into a sequence of discrete proposals, each of which has to win its own vote. There is nothing to roll over and nothing to claw back — the money simply stops unless the members affirmatively send the next tranche. Renewal-by-default, the first failure mode above, is not a policy a caper has to adopt; it is unavailable. And a provider that accumulated a large position could not simply outvote the members on its own renewal, because vote weight multiplies holdings by an earned, non-transferable participation record, so a bag on its own carries no decisive weight. A member who disagrees with an engagement also has a second move beyond voting against it: a standing exit that returns their share of the treasury.

What Caper does not offer is a better selection process. There is no rubric, no committee, no RFP and no scoring — the DAOs above built those because choosing well among 26 applicants is a hard problem, and nothing in a shorter leash solves it. The honest summary is that Caper makes engagements easy to stop and offers nothing at all for making them easy to choose.

References

• [6.42] [Social] SPP3: Program Authorization and Committee Model — discuss.ens.domains, 25 April 2026. One-cycle authorization, the eligibility test, the named committee, and the 20%-of-trailing-revenue budget cap.
• [EP 6.49] SPP3: Cohort Recommendation — discuss.ens.domains, 3 July 2026. The 26-application funnel, the rubric and interviews, the four-provider $1,690,000 cohort, and the conflict-of-interest recusal.
• [7.1] [Social] SPP3: Marketplace RFP — discuss.ens.domains, 9 July 2026. The declined award, the $1,560,284 uncommitted, and the decision to re-tender publicly rather than renegotiate privately.
• Entropy Advisors: Exclusively Working with the Arbitrum DAO, Y2-Y3 — forum.arbitrum.foundation, 17 June 2025, revised 7 July 2025. The 5M/10M ARB alignment split, the termination clause, and OpCo as counterparty.
• OpCo – A DAO-adjacent Entity for Strategy Execution — forum.arbitrum.foundation, 30 October 2024. The procurement rationale, the 30M ARB earmark and bonus pool, and the drawdown thresholds.