Skip to main content
Schema A is the entity attestation — Droplinked’s on-chain receipt that a brand slug has been operator-reviewed and is who it says it is. It anchors the first axis of the 4-axis trust fabric: everything downstream (lender underwriting, peer cross-attestations) presumes the brand identity has been verified.

Network & UIDs

EAS registry version: v1.4.0 (EIP-712 typed-data attestations; revocation via revoke(bytes32 uid) direct call).

Field reference

The on-chain payload is ABI-encoded against the schema string:
EAS envelope fields (set by the contract, not by the schema):

Read via Droplinked API

Read via viem (TypeScript)

Read via ethers (TypeScript)

Read via Cast (Foundry)

Indexer access (EAS GraphQL)

EAS publishes a public GraphQL indexer per chain. Use it to enumerate without RPC round-trips.

Common queries

All Schema A attestations for a brand slug — enumerate by attester (Droplinked operator) + schema, then resolve data client-side to filter by brandName. There is no on-chain index on brandName; for scale, use the Droplinked verifier API.
Single attestation by UID:

Trust assumptions

A Schema A attestation is authoritative if and only if:
  1. The on-chain attester is the Droplinked operator wallet: 0xD5F6FB7b6E71DD7F609b8442951444E5a5C76cce (Base mainnet).
  2. The on-chain schema matches the mainnet UID for Schema A (see top of page).
  3. revocationTime == 0 AND expirationTime == 0 (Schema A is issued without expiry by default).
  4. If issued via a future operator-wallet rotation, the wallet was the registered operator at issuance time — check the time field against the operator-rotation log.
KMS-backed signer rotation is queued (tracking: backend issue #1718). Until it ships, the mainnet issuer is the personal operator wallet listed above. After rotation, this page will be updated and the legacy wallet will remain valid for the historical window.