Skip to main content

What is an Authority?

In AttestProtocol, an authority is simply the wallet address that created a schema. When you deploy a schema, you become its authority — the permanent owner of that schema definition.
Schemas and attestations are permissionless by default. Anyone can create schemas, and anyone can issue attestations to any schema — unless a resolver restricts access.

The Permissionless Model

AttestProtocol is designed to be open:

Schema Authority

When you deploy a schema, your wallet address is recorded as its authority. This gives you:
  • Ownership record — Your address is permanently linked to the schema
  • Schema definition control — You defined the structure and resolver at creation
Being a schema authority does not mean only you can attest. By default, anyone can issue attestations to your schema. Use a resolver if you need access control.

Creating a Schema

Restricting Access with Resolvers

If you want to control who can attest to your schema, attach a resolver:
See Resolvers for details on implementing access control.

Verified Authority (Optional)

Separately from schema authority, you can register as a Verified Authority on the AttestProtocol platform. This is completely optional and provides:
  • Platform badge — Visual indicator that you’re a verified issuer
  • Trust signals — Users can see your verification status
  • Discovery — Easier for verifiers to find trusted attestation sources

Verification Methods

stellar.toml

For Stellar-native organizations, verify using your domain’s stellar.toml file

DID & Verifiable Credentials

Use decentralized identifiers and external credentials for verification

Registering as a Verified Authority

Using the CLI

Authority Metadata

When registering as a verified authority, include relevant information:

Checking Authority Status

Check Verified Authority Status

Check Attestation Issuer

Every attestation includes the attester address:

Delegates

Authorities can delegate attestation signing to other addresses using BLS delegation. This enables:
  • Gasless attestations — Users sign off-chain, a relayer submits on-chain
  • Batch operations — Issue many attestations in one transaction
  • Separation of concerns — Keep hot wallets separate from main keys
See Delegates for detailed documentation.

Authority vs Resolver

  • Authority = “Who owns this schema definition”
  • Resolver = “What rules apply when attesting”
Without a resolver, attestations are permissionless. With a resolver, you can enforce any access control logic you need. See Resolvers for implementation details.

Security Considerations

Keep your private keys secure. While attestations are permissionless, your verified authority status and any resolver admin rights are tied to your address.

Best Practices

  1. Use resolvers for access control — Don’t assume only you will attest to your schema
  2. Secure your keys — Use hardware wallets or multi-sig for production
  3. Verify your domain — Set up stellar.toml for additional trust
  4. Monitor attestations — Track what’s being issued to your schemas

Next Steps

Resolvers

Add access control to your schemas

Schemas

Define attestation structures

Delegates

Enable off-chain signing with BLS delegation

Examples

See real-world implementations