Cowrie Research

daoip-3

3 min read

DAOIP-3

  • Name: DAOIP-3 (Attestations for DAOs)
  • URL: https://github.com/metagov/daostar/blob/main/DAOIPs/daoip-3.md
  • Category: DAO attestation standard / contribution-and-membership indexing layer / multi-issuer reputation interoperability spec
  • Summary: DAOIP-3 is best understood not as a single attestation product, but as an indexing and discovery architecture for DAO membership and contribution data. Its core move is to place W3C-verifiable-credential-shaped attestations behind issuer endpoints, then connect those issuers back to a DAO through daoURI and attestationIssuersURI, so wallets, profiles, grants tools, and aggregators can discover which issuers speak for a DAO and how to query subject-level attestations or aggregate presentations. That makes DAOIP-3 a useful comparison class for Ethereum Attestation Service, Sign Protocol, Verax, Govrn, and contribution-profile systems: the distinctive control surface here is not just who can issue an attestation, but who gets listed as an issuer, who aggregates other issuers’ data, which subject identifiers are treated as canonical, and which endpoints downstream clients decide to trust.
  • What it does:
    • Defines a VC-shaped attestation format for DAO-related claims, with issuer, attestationURI, credentialSubject, and recommended expirationDate fields
    • Specifies standard attestation families for membership, contributions, and daoURI publication on behalf of a DAO
    • Requires DAOs to publish attestationIssuersURI metadata so clients can discover which issuers are recognized by that DAO
    • Requires issuers to publish issuer metadata plus a subjectAttestationsURI endpoint for querying attestations about a subject
    • Allows issuers to publish aggregate subject presentations that merge multiple membership or contribution claims into one response shape
    • Intentionally composes with daoURI and with existing identity systems instead of prescribing one canonical identity or PII framework
  • Key claims:
    • The most reusable mechanism is the split between DAO-controlled discovery and issuer-controlled evidence. A DAO lists recognized issuers, but the issuers host the actual attestation endpoints and query surfaces.
    • DAOIP-3 treats contributions and membership as interoperable data objects rather than as properties trapped inside one product database, which is why it is analytically closer to an indexing protocol than to a badge or profile app.
    • The spec’s use of W3C VC-shaped documents matters less as an identity ideology statement than as a serialization choice that lets DAOIP-3 focus on cross-issuer indexing, endpoint discovery, and aggregate presentations.
    • The attestationURI field is a real control point because it makes relayed data auditable back to an origin source while also letting one issuer re-expose another issuer’s contribution data.
    • The Avenue / Govrn example in the spec and discussion is especially important because it shows the intended topology: a client may integrate with one issuer and still receive relayed data from others, meaning practical influence can accumulate at aggregator endpoints even in an ostensibly permissionless graph.
    • DAOIP-3 is also a useful precursor to DAOIP-5. Once grants and project metadata can point to attestation issuers, the real authority shifts toward issuer admission, schema choice, subject matching, and indexer policy before any capital-allocation workflow begins.
    • The draft status matters. The design ambition is clear, but the GitHub discussion also shows unresolved implementation questions around pagination, prefetching, common contribution schemas, and performance.
  • Whitepaper: No standalone DAOIP-3 whitepaper surfaced in this pass. The strongest primary materials were the draft DAOIP text and the accompanying DAOstar discussion thread; see ../whitepapers/daoip-3-primary-sources-2026-05-10.md.
  • Sources:

Internal linkages

Graph View