Wind-down, CoDAO and what surv…Daddy domain-for-sale listing.By 24 September 2026 it had mo…epts/analysis/how-daos-fail) .

How Caper approaches this Coo…ff-chain step to later ratify.Carrying the ballot is not the… company, or a domain renewal.

Where it came from The questi…itcoin, Bankless, Olympus and Index Coop (/wiki/daos/lending/index-coop) were running circles. By the p…al (https://coordinape.com/) )

Wind-down, CoDAO and what surv…n is no longer held by the DAO:. On 15 August 2026 it iwas delegated to Afternic’s nameservers and its landing page redirectsed to a GoDaddy domain-for-sale listing (checked 15 August 2026). By 24 September 2026 it had moved again: the registry record (https://rdap.centralnic.com/xyz/domain/codao.xyz) dates the current registration to 28 August 2025 at the Japanese registrar Onamae.com, points it at dns1.onamae-expired.com, the nameservers that registrar parks unpaid registrations on, and the domain answered no web request at all. The only CoDAO page still re…epts/analysis/how-daos-fail) .

How Caper approaches this Coo… it: a passing payout earns a 48-hour market window, and the money m… or above the baseline locked when it openedat the trigger. A spend the holders will not… company, or a domain renewal.

How Caper approaches this Coo…ed (/wiki/governance/voting) andon-chain and, if it carries, executed (/wiki/governance/execution) on-chain directly against the caper’s v…ff-chain step to later ratify. Carrying the ballot is not the end of it: a passing payout earns a 48-hour market window, and the money moves at the close of that window only if the caper’s time-weighted price held at or above the baseline locked when it opened. A spend the holders will not stand behind is stopped by the market, not by a reviewer. The trade-off mirrors the one… company, or a domain renewal.

Category Contributor compensation · peer allocation Operated 2021–2025 (app sunset 2025; CoDAO (https://about.coordinape.com/codao) stewards the IP) Core mechanic Per-epoch GIVE allocation inside “circles” — contributors reward each other; your reward share = GIVE received ÷ total GIVE Token $CO — governance handed from the founding team to CoDAO holders Status App closed; contracts open-source; GIVE attestations moved on-chain (EAS on Base, 2025) Site coordinape.com (https://coordinape.com/) · docs (https://docs.coordinape.com/) Related DAO tooling stack (/wiki/daos/tooling/dao-tooling-overview) , What is a DAO? (/wiki/daos/concepts/fundamentals/what-is-a-dao) , Safe (/wiki/daos/tooling/treasury/safe)

Coordinape was the canonical tool for peer-allocated compensation in DAOs (/wiki/daos/concepts/fundamentals/what-is-a-dao) — 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 (https://coordinape.com/) . ( Coordinape docs (https://docs.coordinape.com/) )

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 (https://docs.coordinape.com/) )

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 (/wiki/daos/tooling/dao-tooling-overview) .

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 (https://about.coordinape.com/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 (https://github.com/coordinape/coordinape-protocol) are open-source, and the GIVE allocations were migrated to on-chain attestations (via EAS (https://attest.org/) on Base) so the history of who-rewarded-whom cannot be erased. CoDAO continues as steward of the intellectual property. ( CoDAO (https://about.coordinape.com/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 (/wiki/governance/proposals) is voted (/wiki/governance/voting) and executed (/wiki/governance/execution) 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 (https://coordinape.com/) and documentation (https://docs.coordinape.com/) . - Coordinape, CoDAO (https://about.coordinape.com/codao) (governance and IP steward). - Coordinape, coordinape-protocol (https://github.com/coordinape/coordinape-protocol) (open-source contracts).

Category Contributor compensation – peer allocation Operated 2021–2025. Conceived inside Yearn Finance (/wiki/daos/lending/yearn-finance) in 2020; app sunset 2025 Core mechanic Per-epoch GIVE allocation inside “circles” – contributors reward each other; your reward share = GIVE received ÷ total GIVE Scale 50M+ GIVE sent through circles – 500+ DAOs and organizations at peak – 64,000+ on-chain attestations Token $CO, launched on Base in 2024 alongside the Social Oracle; governance handed to CoDAO the same year Status App closed; contracts open-source (https://github.com/coordinape/coordinape-protocol) ; GIVE attestations live on EAS (https://attest.org/) (Base). CoDAO’s own domain has lapsed – see below Site coordinape.com (https://coordinape.com/) (now a memorial) – docs (https://docs.coordinape.com/) Related DAO tooling stack (/wiki/dao-governance/tooling/dao-tooling-overview) , What is a DAO? (/wiki/dao-governance/concepts/fundamentals/what-is-a-dao) , Safe (/wiki/dao-governance/tooling/treasury/safe)

Coordinape was the canonical tool for peer-allocated compensation in DAOs (/wiki/dao-governance/concepts/fundamentals/what-is-a-dao) – 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 and shaped how a generation of DAOs handled contributor pay before its app sunset in 2025. The site that remains is a memorial (https://coordinape.com/) rather than a product page, and it is now the project’s primary record. ( Coordinape docs (https://docs.coordinape.com/) )

Where it came from The question that produced Coordinape was asked inside Yearn Finance (/wiki/daos/lending/yearn-finance) in 2020: “How do we pay the people who just showed up?” Yearn had a large treasury, an enormous community, and no fair way to establish who had contributed or how much – so compensation fell to a handful of insiders who could not possibly see everything. Contributors sketched an alternative in which the team itself decided, and Coordinape launched publicly in early 2021. Within weeks Gitcoin, Bankless, Olympus and Index Coop were running circles. By the project’s own accounting it carried more than 50 million GIVE across circles and reached 500+ DAOs and organizations at peak adoption. ( Coordinape memorial (https://coordinape.com/) )

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 (https://docs.coordinape.com/) ) The team was candid about the limits: the model “could be gamed and had blind spots,” and worked best where a circle had already built real trust. That is the honest boundary on every peer-allocation scheme – it measures reputation inside a group, and inherits whatever the group’s reputation dynamics already are.

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 (/wiki/dao-governance/tooling/dao-tooling-overview) .

Wind-down, CoDAO and what survived The sequence is dated on the project’s own chronicle. In 2024 the $CO token launched on Base with the Social Oracle, an on-chain attestation system that recorded 64,000+ attestations via EAS (https://attest.org/) – taking GIVE-based reputation out of the app’s database and onto a public ledger. That same year the founding team transferred governance to CoDAO, the community of $CO holders, in what it calls “one of the more honest governance transitions in web3”: control handed over and the builders stepping back “not gradually – fully.” In 2025 the app closed and the contracts were wound down. ( Coordinape memorial (https://coordinape.com/) ) The protocol contracts (https://github.com/coordinape/coordinape-protocol) remain open-source and the attestations remain on Base, which is the part of the design that was meant to outlive the company – and did. CoDAO holds the intellectual property, and the memorial is explicit that “active development has wound down.” The steward’s own domain has lapsed Anyone following that record today hits a gap worth naming, because it is a recurring failure mode rather than a quirk. The memorial’s “Visit CoDAO” link points at codao.xyz, and that domain is no longer held by the DAO: it is delegated to Afternic’s nameservers and its landing page redirects to a GoDaddy domain-for-sale listing (checked 15 August 2026). The only CoDAO page still reachable is about.coordinape.com/codao (https://about.coordinape.com/codao) , on the parent project’s domain – and it is a pre-sunset artefact, still inviting readers to “Launch Coordinape,” still promising GIVE “very soon on Farcaster,” and still describing a handover in the future tense (“CoDAO will ultimately control the CO token”) that completed two years ago. The lesson generalises past Coordinape: a collective’s domain is rented and its on-chain record is not. Coordinape planned for this better than most – the attestations and contracts are exactly the things that cannot lapse – but the organisation nominated as steward is now discoverable only through a stale page on someone else’s hostname. When reading any wound-down DAO, treat DNS as the least durable citation you have. See how DAOs fail (/wiki/dao-governance/concepts/analysis/how-daos-fail) .

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 (/wiki/governance/proposals) is voted (/wiki/governance/voting) and executed (/wiki/governance/execution) 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 replicate Coordinape’s fine-grained peer signal for dividing a reward among many contributors – a caper decides payouts by vote, not by circle. There is a second parallel worth stating plainly, since Coordinape’s wind-down demonstrates it. What survived the company was what was written to a chain nobody had to keep paying for. A caper’s proposals, ballots and treasury are on-chain state in its own contract for the same reason – the record does not depend on a hosted app, a company, or a domain renewal.

References - Coordinape, coordinape.com (https://coordinape.com/) – the post-sunset memorial: origin at Yearn, the 2020–2025 chronicle, and the 50M GIVE / 500+ organizations / 64,000 attestations figures. - Coordinape, documentation (https://docs.coordinape.com/) – circles, epochs and the GIVE allocation mechanic. - Coordinape, CoDAO (https://about.coordinape.com/codao) – the surviving CoDAO page, which predates the sunset and should be read as an artefact. - Coordinape, coordinape-protocol (https://github.com/coordinape/coordinape-protocol) – open-source contracts. - Ethereum Attestation Service, attest.org (https://attest.org/) – the attestation layer the Social Oracle records to on Base.

Category Contributor compensat… DAO tooling stack (/wiki/daos/tooling/dao-tooling-overview) , What is a DAO? (/wiki/daos/concepts/fundamentals/what-is-a-dao) , Safe (/wiki/daos/tooling/treasury/safe)

Coordinape was the canonical t…mpensation in DAOs (/wiki/daos/concepts/fundamentals/what-is-a-dao) — a way to dec…ttps://docs.coordinape.com/) )

Why it mattered Compensation … DAO tooling stack (/wiki/daos/tooling/dao-tooling-overview) .

Category Contributor compensation · peer allocation Operated 2021–2025 (app sunset 2025; CoDAO (https://about.coordinape.com/codao) stewards the IP) Core mechanic Per-epoch GIVE allocation inside “circles” — contributors reward each other; your reward share = GIVE received ÷ total GIVE Token $CO — governance handed from the founding team to CoDAO holders Status App closed; contracts open-source; GIVE attestations moved on-chain (EAS on Base, 2025) Site coordinape.com (https://coordinape.com/) · docs (https://docs.coordinape.com/) Related DAO tooling stack (/wiki/dao/tooling/dao-tooling-overview) , What is a DAO? (/wiki/dao/concepts/what-is-a-dao) , Safe (/wiki/dao/tooling/safe)

Coordinape was the canonical tool for peer-allocated compensation in DAOs (/wiki/dao/concepts/what-is-a-dao) — 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 (https://coordinape.com/) . ( Coordinape docs (https://docs.coordinape.com/) )

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 (https://docs.coordinape.com/) )

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 (/wiki/dao/tooling/dao-tooling-overview) .

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 (https://about.coordinape.com/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 (https://github.com/coordinape/coordinape-protocol) are open-source, and the GIVE allocations were migrated to on-chain attestations (via EAS (https://attest.org/) on Base) so the history of who-rewarded-whom cannot be erased. CoDAO continues as steward of the intellectual property. ( CoDAO (https://about.coordinape.com/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 (/wiki/governance/proposals) is voted (/wiki/governance/voting) and executed (/wiki/governance/execution) 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 (https://coordinape.com/) and documentation (https://docs.coordinape.com/) . - Coordinape, CoDAO (https://about.coordinape.com/codao) (governance and IP steward). - Coordinape, coordinape-protocol (https://github.com/coordinape/coordinape-protocol) (open-source contracts).