Coordinape primary sources — 2026-05-09

What I reviewed

• Official site / archive:
  • https://coordinape.com/
• Official docs:
  • https://docs.coordinape.com/
  • https://raw.githubusercontent.com/coordinape/docs/master/README.md
  • https://raw.githubusercontent.com/coordinape/docs/master/info/documentation/README.md
  • https://raw.githubusercontent.com/coordinape/docs/master/info/co-token-utility.md
• Official protocol materials:
  • https://github.com/coordinape/coordinape-protocol
  • https://raw.githubusercontent.com/coordinape/coordinape-protocol/master/README.md
• Official Social Oracle / CoDAO material:
  • https://about.coordinape.com/codao/social-oracle

Key takeaways from primary sources

• Coordinape’s original core mechanism is peer-directed budget allocation inside recurring “gift circles.” Members receive fixed GIVE balances each epoch and can only allocate them to others, not keep them for themselves.
• The strongest conceptual distinction is that Coordinape is not measuring output directly. It asks peers to express relative value through gifting, then converts that signal into a payout split at epoch end.
• Circle configuration is a real governance surface. The docs say circles can define participation rules, visibility, and parts of the game mechanics through admin controls or internal governance, so the neutrality of the peer-allocation process depends heavily on how the circle is curated.
• The protocol spec is especially useful because it reveals the implementation boundary: badge access, vouching, and some parameter control can be onchain, but GIVE movement during an epoch is intentionally offchain and final state is later synchronized or published. That means operational trust and data-publication choices remain central even in the more decentralized design.
• The protocol spec also makes membership and access control first-order. NFT badges, vouch thresholds, revocation logic, and role toggles determine who can participate, who can receive GIVE, and how much influence each participant has.
• The later Social Oracle materials show a second life for the system: GIVE is no longer only an internal payroll primitive, but also the raw input for an EAS-based attestation graph on Base that others can build on.
• The CO-token utility page adds an important power surface: addresses that hold more CO can emit GIVE at higher rates and keep larger GIVE caps, so token holdings can shape how much reputation data a participant can generate.
• The sunset page matters historically because it frames the app as closed in 2025 while arguing that the underlying mechanism and resulting onchain attestations persist through CoDAO and the Social Oracle.

Specific source signals worth retaining

• Docs homepage and README: Coordinape is framed as a system for communities to manage grants, salaries, and projects by letting contributors reward the value they see created.
• Documentation / How It Works page: circles, epochs, 100 GIVE per member by default, opt-out for receivers, and pro-rata payout from the circle budget.
• Protocol spec README: badge-gated access, vouching, offchain GIVE, GET redemption, admin-created circles, and open design questions around synchronization vs merkle distribution.
• Social Oracle page: GIVE data flows into an EAS schema on Base and is explicitly presented as a public-good reputation layer.
• CO token utility page: higher CO balances increase GIVE emission rates and GIVE caps, linking token ownership to reputation-production capacity.
• Sunset homepage: historical adoption claims, the app’s closure, and the positioning of Social Oracle / CoDAO as what remains.

Why this entry belongs in the corpus

• Coordinape strengthens the contributor-legibility cluster because it sits between pure peer-recognition systems and actual payroll / budget distribution.
• It is a strong comparison class for SourceCred and Praise because it puts the key governance question in a slightly different place: not only in how praise is scored or graph weights are set, but in who gets circle access, how often epochs run, and whether peer gifting is later turned into portable onchain reputation.
• The reusable insight is that peer allocation systems often look democratic at the moment of gifting, while practical authority accumulates upstream in circle formation and downstream in how gift data is exported, token-weighted, or reused.