Cowrie Research

attest-protocol

3 min read

Attest Protocol

  • Name: Attest Protocol
  • URL: https://docs.attest.so/introduction
  • Tags: stellar-ecosystem
  • Category: attestation middleware / schema-and-resolver framework / verified-issuer registry / cross-chain trust infrastructure
  • Summary: Attest Protocol is a modular attestation rail with a useful split: schema ownership, issuance policy, and verified-authority discovery are not the same thing. That separation is the note. Resolvers decide admission, authority registration handles reputation, and BLS delegation pushes submission into a relay layer. Good comparison material, not an anchor.
  • What it does:
    • Lets anyone create schemas and issue attestations by default, unless a schema creator attaches a resolver that restricts issuance or revocation
    • Stores attestations onchain and exposes schema registration, attestation creation, and revocation through a core protocol contract
    • Separately offers a verified-authority registration layer with metadata, trust badges, and issuer discovery for organizations that want stronger reputational signaling
    • Supports resolver contracts that can enforce allowlists, collect fees, distribute rewards, or implement custom validation logic before attestations are accepted
    • Uses BLS delegation so attestations can be signed offchain and submitted onchain by a relayer, shifting gas payment and batch-submission possibilities away from the original issuer key
    • Positions itself as multi-chain trust infrastructure, with Stellar active in current docs and Solana / Starknet / other chains presented as expansion paths in the repo materials
  • Key claims:
    • The introduction docs make the core framing very plain: Attest wants to be reusable proof infrastructure for identity, contribution, ownership, permissions, and other trust signals without requiring every app to deploy bespoke contracts.
    • The strongest mechanism insight is the authority / resolver split. The docs emphasize that the wallet creating a schema becomes its authority, but this alone does not restrict who can attest; actual access control sits in an attached resolver. That separation is useful because many attestation systems blur ownership, issuance rights, and validation policy together.
    • The authorities docs also add a second layer of meaning to “authority”: beyond schema ownership, the platform offers optional verified-authority registration with metadata and badges. That means trust can centralize not only in schema design and resolver logic, but also in issuer-verification and discovery surfaces.
    • The resolver docs are especially valuable because they make the protocol’s policy surface explicit. Resolvers can gate attestation issuance, charge fees, distribute rewards, and run arbitrary custom logic, so the real control plane often sits in per-schema resolver design rather than in the base protocol contract.
    • BLS delegation matters because it turns attestation submission into a separable relay layer. That is operationally useful, but it also means issuer authority, signer delegation, and gas/payment responsibility can be split across different actors.
    • The repo’s multi-chain framing is analytically relevant even if current production emphasis appears to be on Stellar. The project is pitching interoperable trust infrastructure, not just a single-chain attestation app, which makes it a good comparison point for broader schema-and-proof middleware.
    • Attest Protocol belongs in the active corpus because it sharpens a recurring question in identity and attestation systems: who really controls issuance legitimacy — schema creators, resolver authors, verified-authority registries, relayers, or downstream apps deciding which attestations count?
  • Whitepaper: No canonical standalone whitepaper or litepaper surfaced in this pass. The strongest primary materials were the official docs pages for introduction, architecture, authorities, and resolvers, plus the official repository README; see ../whitepapers/attest-protocol-primary-sources-2026-05-10.md.
  • Sources:

Internal linkages

Graph View