bnb-attestation-service-primary-sources-2026-05-11

BNB Attestation Service primary sources

Collected: 2026-05-11 UTC

Primary sources reviewed

• https://docs.bnbchain.org/showcase/identity/attestation/
  • Official BNB Chain BAS overview
  • Used to confirm BAS’s own framing as arbitrary-attestation infrastructure, its schema / attestation / resolver split, onchain versus offchain support, Greenfield storage claims, and example integrations
• https://doc.bascan.io/core_concept/schema
  • Official BAS schema docs
  • Used to confirm schema fields, optional resolver attachment, attestation counts, ABI-encoded schema data, and BAS’s preference for modular composable schema design
• https://doc.bascan.io/core_concept/attestation
  • Official BAS attestation docs
  • Used to confirm attestation records, UID structure, reference links between attestations, and the protocol’s framing of attestations as a bridge from web2 data into web3
• https://doc.bascan.io/core_concept/resolver
  • Official BAS resolver docs
  • Used to confirm that resolver contracts act as schema-level issuance hooks and can enforce arbitrary gating logic such as ownership checks or payment requirements
• https://github.com/bnb-attestation-service/bas-contract
  • Official BAS contract repository linked from the docs
  • Used as repository evidence that BAS is meant as a developer-facing reusable attestation stack rather than only as a hosted explorer feature

Notes

• BAS cleared the bar because it is not just another chain-specific attestation label or an EAS clone. The reviewed materials make the protocol split unusually explicit: schemas define structure, resolvers define policy, and attestations carry claims either onchain or offchain.
• The most durable comparison surface is the storage model. BAS says offchain attestations can live in Greenfield with ownership, privacy, and access-control properties, which makes storage location and custody a first-class part of the design rather than just an implementation detail.
• Resolver logic is the second key control surface. The docs make clear that issuance openness is optional: a schema can stay open, or it can attach a resolver that gates creation using arbitrary custom logic.
• The schema docs also matter because they push modular schema composition rather than one universal monolithic credential design. BAS therefore belongs in the corpus not only as an attestation product but also as schema-and-policy middleware.
• The attestation docs highlight references between attestations, which suggests BAS is useful for thinking about claims graphs and dependency chains, not just stand-alone badges.
• This entry belongs in the active corpus because it gives the identity / attestation cluster a BNB-native comparison point where schema governance, resolver gating, offchain privacy, and decentralized-storage custody are all more visible than they are in flatter “credential” narratives.