Definitions

Definitions
DAOs use various services offered by service providers. For example, Dework provides Web3-native task management, Avenue hosts DAO communications and collaboration, while Govrn publishes contribution data. All three have access to unique layers of contribution and membership.
An attestation is a digital record composed of a predicate declared by an attester and some identifying information about the attester.
A membership attestation is an attestation declaring information about a given organization and one or more of its members. Typically, this takes the form of some (attester, organization, member) tuple. For example, a simple DAO membership attestation is a record containing a (DAO, DAO, member) tuple, meaning that the DAO itself attests that a given person or entity is a member of that DAO. There are at least four types of attestations about membership:
  • DAO attestations, which canonically is via membersURI, as described in EIP-4824
  • Self attestations, i.e. as in a traditional CV or platforms like LinkedIn
  • Peer attestations, i.e. from other members of a DAO
  • Third-party attestations, i.e. from a third-party service provider such as Snapshot, Tally, or Dework, but also potentially from other DAOs and organizations
A contribution attestation is an attestation declaring information about a given organization, one or more of its members, and for each member one or more of their contributions. For example, a simple DAO contribution attestation is a record containing a (DAO, DAO, member, contribution) tuple.
Often, an attestation is issued and managed on the attester’s behalf by an attestation issuer, or just issuer. Many self attestations will take this form, but so will many DAO attestations. Such an issuer may generate NFTs which represent membership (e.g. POAP), it may issue a verifiable credential following the W3C standard (e.g. Disco), or it may publish and store the record on a traditional server (e.g. Dework, Backdrop). These issuers may also issue attestations of their own—i.e. as a third-party service provider—on top of any attestations that they issue on behalf of a DAO or an end-user.

Definitions

Definitions
DAOs use various services offered by service providers. For example, Dework provides Web3-native task management, Avenue hosts DAO communications and collaboration, while Govrn publishes contribution data. All three have access to unique layers of contribution and membership.
An attestation is a digital record composed of a predicate declared by an attester and some identifying information about the attester.
A membership attestation is an attestation declaring information about a given organization and one or more of its members. Typically, this takes the form of some (attester, organization, member) tuple. For example, a simple DAO membership attestation is a record containing a (DAO, DAO, member) tuple, meaning that the DAO itself attests that a given person or entity is a member of that DAO. There are at least four types of attestations about membership:
  • DAO attestations, which canonically is via membersURI, as described in EIP-4824
  • Self attestations, i.e. as in a traditional CV or platforms like LinkedIn
  • Peer attestations, i.e. from other members of a DAO
  • Third-party attestations, i.e. from a third-party service provider such as Snapshot, Tally, or Dework, but also potentially from other DAOs and organizations
A contribution attestation is an attestation declaring information about a given organization, one or more of its members, and for each member one or more of their contributions. For example, a simple DAO contribution attestation is a record containing a (DAO, DAO, member, contribution) tuple.
Often, an attestation is issued and managed on the attester’s behalf by an attestation issuer, or just issuer. Many self attestations will take this form, but so will many DAO attestations. Such an issuer may generate NFTs which represent membership (e.g. POAP), it may issue a verifiable credential following the W3C standard (e.g. Disco), or it may publish and store the record on a traditional server (e.g. Dework, Backdrop). These issuers may also issue attestations of their own—i.e. as a third-party service provider—on top of any attestations that they issue on behalf of a DAO or an end-user.