Coordinape was the canonical tool for peer-allocated compensation in DAOs — a way to decide who gets paid without a manager, a committee, or a token vote. Instead of one authority setting salaries, the contributors themselves signalled who created value, and rewards flowed accordingly. It ran for four years (2021–2025) and shaped how a generation of DAOs handled contributor pay before its app wound down in 2025. (Coordinape docs)

How circles and GIVE worked

A team formed a circle — the set of contributors to be rewarded for a period. Each epoch (say, a month), every member received a budget of GIVE tokens and allocated them to the peers whose work they valued, optionally with a note. GIVE could not be kept for yourself, so the mechanic surfaced a collective, bottom-up judgement of contribution. When the epoch closed, each member’s share of a real reward pool (USDC, a governance token, whatever the DAO funded) was simply their GIVE received divided by total GIVE allocated. It replaced the fraught task of a core team guessing everyone’s worth with a distributed signal from the people actually doing the work. (Coordinape docs)

Why it mattered

Compensation is one of the hardest problems in a DAO: contributions are fluid, contributors are pseudonymous, and there is no HR department. Coordinape’s insight was that the people inside a circle have far better information about who contributed than any central allocator, and that a low-stakes per-epoch signal captures it cheaply. It made contributor pay legible and participatory, and the pattern — peer signal in, proportional reward out — influenced how many DAOs still think about rewarding work. It is the contributor-comp layer in the DAO tooling stack.

Wind-down and CoDAO

In 2024 the founding team executed what it called “one of the more honest governance transitions in web3”: it transferred control to CoDAO — the community of $CO token holders — and stepped back fully rather than gradually. The hosted app then closed in 2025. Its work persists as on-chain record: the protocol contracts are open-source, and the GIVE allocations were migrated to on-chain attestations (via EAS on Base) so the history of who-rewarded-whom cannot be erased. CoDAO continues as steward of the intellectual property. (CoDAO)

How Caper approaches this

Coordinape sat beside a DAO’s governance — a separate app that decided who to pay, whose output a treasury still had to honour. Caper routes contributor payouts through the same binding path as any other treasury action: a payout proposal is voted and executed on-chain directly against the caper’s vault, with no separate allocation tool and no off-chain step to later ratify. The trade-off mirrors the one Coordinape made deliberately: Caper gains a single auditable path from decision to payment, but does not (today) replicate Coordinape’s fine-grained peer-signal for dividing a reward among many contributors — a caper decides payouts by vote, not by circle.

References

• Coordinape, coordinape.com and documentation.
• Coordinape, CoDAO (governance and IP steward).
• Coordinape, coordinape-protocol (open-source contracts).