DAOIP-3’s main reusable mechanism is not merely “use attestations”; it is the pairing of VC-shaped attestations with discoverable issuer endpoints and DAO-published issuer registries.
The spec treats daoURI as the DAO-controlled discovery layer and subjectAttestationsURI as the issuer-controlled evidence layer. That split is where most practical governance and trust decisions sit.
Membership and contribution attestations share a common base shape but differ in their subject payloads: membership binds a subject to a DAO, while contribution attestations bind a subject to a contribution object that can also name multiple contributors and external data.
The required attestationURI is important because it gives clients a canonical pointer back to the source assertion even when data is relayed through another issuer or aggregator.
The issuer metadata schema matters because it turns issuer discovery into a first-class API surface. Trust does not live only in signatures; it also lives in whether a DAO lists an issuer and whether clients honor that list.
Aggregate presentations are a notable design choice. DAOIP-3 explicitly allows an issuer to merge multiple attestations into one subject presentation, which is convenient for clients but also creates a natural concentration point for indexing and ranking power.
Specific source signals worth retaining
The raw DAOIP-3 text is the best source for the actual attestation shapes, attestationIssuersURI, issuer endpoint requirements, and the relationship to verifiable credentials.
The spec’s Avenue / Govrn / Disco example is especially useful because it makes the intended topology concrete: one issuer can relay or aggregate another issuer’s data while pointing back to origin attestationURIs.
The GitHub discussion is valuable because it exposes real implementation pressures that the clean draft spec hides, especially pagination, prefetching, contribution-schema normalization, and performance costs when contribution details live behind multiple additional lookups.
The discussion also reinforces that DAOIP-3 was being used as an interoperability layer between Govrn and Avenue rather than as a purely theoretical DAOstar paper.
Why this entry belongs in the corpus
It strengthens the identity / attestation / contribution-legibility clusters by adding an issuer-discovery-and-aggregation layer that differs from single-registry systems like EAS, Sign Protocol, or Verax.
It gives a better way to compare where labor and membership become legible: in attestations themselves, in issuer admission lists, in subject-identifier matching, in relay endpoints, or in aggregate presentations.
It also helps explain later standards like DAOIP-5, where metadata interoperability starts to depend on the same underlying question: who is allowed to publish claims about a project, contributor, or DAO, and how do clients discover and prioritize them?