attest-protocol-primary-sources-2026-05-10

Attest Protocol primary sources

Reviewed: 2026-05-10 UTC

What I reviewed

• Official docs:
  • https://docs.attest.so/introduction
  • https://docs.attest.so/concepts/how-it-works
  • https://docs.attest.so/concepts/authorities
  • https://docs.attest.so/concepts/resolvers
• Official repository:
  • https://github.com/daccred/attest.so
  • https://raw.githubusercontent.com/daccred/attest.so/main/README.md

Key takeaways from primary sources

• Attest Protocol’s most useful primitive is not merely “onchain attestations.” It is the explicit separation between schema ownership, optional verified-authority registration, and resolver-controlled admission policy.
• The docs say schemas and attestations are permissionless by default. Anyone can create schemas, and anyone can attest to a schema unless a resolver restricts access. That is an important baseline because it prevents “authority” from being misread as automatic exclusivity.
• The authorities page makes the split especially clear: schema creators become authorities in the sense of ownership records, but verified-authority status is a separate optional platform-layer reputation signal.
• The resolver docs show where policy actually lives. Resolvers can gate issuance, enforce fees, distribute rewards, and add arbitrary validation / post-processing logic, so they function as the per-schema control plane.
• The architecture overview adds two more important surfaces: BLS delegation, which separates attestation signing from onchain submission/gas payment, and staking/economic-security language around authority registration.
• The repository README expands the picture from the current Stellar deployment to a broader multi-chain ambition across Stellar, Solana, Starknet, and other environments, which matters because the project is presenting itself as generalized trust middleware rather than one chain’s attestation app.

Specific source signals worth retaining

• Introduction docs: reusable framing around identity, action, ownership, and permission proofs without bespoke contract deployment.
• How-it-works page: four-actor model of issuer / protocol / holder / verifier and the emphasis on BLS delegation plus optional economic security.
• Authorities docs: strongest source for the distinction between schema authority, permissionless default issuance, resolver-based restrictions, and optional verified-authority badges.
• Resolver docs: strongest source for the protocol’s hidden governance surface because they spell out onattest, onrevoke, onresolve, resolver metadata, and example fee / reward / authority-gating resolvers.
• Repository README: useful for live contract addresses, SDK / CLI packaging, monorepo structure, and the multi-chain roadmap/positioning.

Why this entry belongs in the corpus

• Attest Protocol is a strong addition because it helps disentangle several layers that often get flattened into one generic “attestation protocol” label: schema definition, issuer discovery, permission policy, relay/delegation, and downstream verification.
• It is especially useful for comparison against EAS, Sign Protocol, Verax, and identity middleware projects where the real question is not whether attestations exist, but who can issue them, who can gate them, and which discovery or trust overlays make some issuers count more than others.
• The reusable insight is that attestation infrastructure often recentralizes in schema registries, resolver logic, issuer-badge layers, and relay paths even when the base protocol advertises permissionless claim creation.