Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.attest.so/llms.txt

Use this file to discover all available pages before exploring further.

​
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:
ActionDefault BehaviorWith Resolver
Create SchemaAnyone can createAnyone can create
Issue AttestationAnyone can attest to any schemaResolver controls access
Revoke AttestationOriginal attester can revokeResolver controls access
┌─────────────────────────────────────────────────────────────┐
│                   PERMISSIONLESS BY DEFAULT                 │
├─────────────────────────────────────────────────────────────┤
│                                                             │
│   Schema Creation                                           │
│   └── Any wallet can deploy a schema                        │
│       └── Creator becomes the "authority" (owner)           │
│                                                             │
│   Attestation Issuance                                      │
│   └── Any wallet can attest to any schema                   │
│       └── Unless a resolver restricts access                │
│                                                             │
│   Access Control (Optional)                                 │
│   └── Attach a resolver to control who can attest           │
│       ├── Fee requirements                                  │
│       ├── Allowlists                                        │
│       └── Custom validation logic                           │
│                                                             │
└─────────────────────────────────────────────────────────────┘

​
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

import { StellarAttestationClient } from '@attestprotocol/stellar-sdk';

const client = new StellarAttestationClient({
  network: 'testnet',
  contractId: 'CBFE5YSUHCRYEYEOLNN2RJAWMQ2PW525KTJ6TPWPNS5XLIREZQ3NA4KP'
});

// Deploy a schema - you become its authority
const schemaUid = await client.createSchema({
  definition: 'string name, bool verified, uint64 timestamp',
  resolver: null,  // No resolver = permissionless attestations
  revocable: true
});

// Anyone can now attest to this schema

​
Restricting Access with Resolvers

If you want to control who can attest to your schema, attach a resolver: 
// Deploy a schema with access control
const schemaUid = await client.createSchema({
  definition: 'string credential, uint64 issuedAt',
  resolver: 'CRESOLVER...', // Resolver controls who can attest
  revocable: true
});

// Now only addresses approved by the resolver can attest
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

import { AttestProtocolAuthority } from '@attestprotocol/stellar-sdk';

// Initialize authority client
const authority = new AttestProtocolAuthority(config, authorityClient);

// Register for verified authority status (optional)
const result = await authority.registerAuthority(
  'GAUTHORITY...', // Your address
  JSON.stringify({
    name: 'Acme Verification Inc.',
    website: 'https://acme.com',
    description: 'KYC and identity verification provider'
  })
);

​
Using the CLI

# Register for verified authority status
pnpm cli authority --chain stellar --action register --key-file ./keypair.json

​
Authority Metadata

When registering as a verified authority, include relevant information: 
{
  "name": "Your Organization Name",
  "website": "https://your-domain.com",
  "description": "Brief description of what you attest to",
  "logo": "https://your-domain.com/logo.png",
  "contact": "attestations@your-domain.com",
  "categories": ["identity", "kyc", "credentials"]
}

​
Checking Authority Status

​
Check Verified Authority Status

// Check if an address is a verified authority
const isVerified = await authority.isAuthority('GADDRESS...');

// Fetch full authority details
const authorityData = await authority.fetchAuthority('GADDRESS...');
console.log('Authority:', authorityData.data);

​
Check Attestation Issuer

Every attestation includes the attester address: 
// Get attestation details
const attestation = await client.getAttestation(attestationUid);
console.log('Issued by:', attestation.data.attester);

​
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

ConceptPurposeControls
AuthoritySchema ownership recordWho created the schema
ResolverAccess control & validationWho can attest, fees, rules
  • 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