System Architecture
AttestProtocol operates as a schema-based attestation system where standardized templates define the structure and validation rules for verifiable claims. The architecture ensures consistency across applications while maintaining flexibility for diverse use cases.Core Components
Schemas
Schemas serve as the foundational templates that define:- Data Structure: Field names, types, and relationships
- Validation Rules: Required fields, format constraints, and value ranges
- Metadata: Schema version, description, and usage guidelines
- Revocability: Whether attestations can be revoked after creation
Authorities
Authorities are entities authorized to issue attestations under specific schemas. They provide the trust anchor for the attestation system: Authority Types:- Individual Authorities: Personal accounts for individual attestations
- Organizational Authorities: Companies and institutions providing verification services
- DAO Authorities: Decentralized organizations issuing collective attestations
- Automated Authorities: Systems and protocols issuing programmatic attestations
- Register wallet as authority on-chain
- Optionally complete verification process for enhanced trust
- Begin issuing attestations under chosen schemas
- Build reputation through accurate and reliable attestations
Attestations
Attestations are cryptographically signed claims that link:- Authority: Who issued the attestation
- Subject: Who or what the attestation is about
- Schema: The template governing data structure
- Data: The actual claim information
- Metadata: Timestamps, references, and additional context
Attestation Lifecycle
1. Schema Creation or Selection
Creating New Schema:2. Authority Registration
Initial Registration:- Submit required documentation
- Complete identity verification process
- Receive verified authority status
3. Attestation Issuance
Creating Attestation:4. Attestation Verification
Fetching Attestation:5. Revocation (Optional)
Revoking Attestation:Data Flow Architecture
Attestation Creation Flow
Verification Flow
Chain-Specific Implementation
Stellar/Soroban
Key Features:- Contract-based attestation storage
- Transaction hash UIDs for schemas
- Simple string-based data format
- Built-in revocation mechanisms
Solana/Anchor
Key Features:- Program Derived Address (PDA) management
- Rich metadata and timestamp support
- Token-based levy system for schemas
- Cross-program invocation capabilities
SDK Integration Patterns
Factory Pattern Implementation
Unified Interface Usage
Event System Integration
Real-Time Monitoring
The Horizon indexer provides real-time event monitoring:Webhook Integration
Security Model
Cryptographic Security
- Digital Signatures: Each attestation is cryptographically signed by the issuing authority
- Chain Validation: Blockchain networks validate and store attestation transactions
- Integrity Checking: Data tampering is detectable through signature verification
Trust Model
- Authority Reputation: Track accuracy and reliability of attestation issuers
- Schema Governance: Community-driven schema standards and validation
- Revocation Rights: Original authorities can revoke their own attestations
Privacy Preservation
- Selective Disclosure: Users control which attestations to share
- Off-Chain Storage: Sensitive data can remain off-chain with on-chain proofs
- Zero-Knowledge Options: Future support for ZK-based attestations
Performance Characteristics
Transaction Costs
| Operation | Stellar | Solana | Description |
|---|---|---|---|
| Authority Registration | ~0.00001 XLM | ~0.000005 SOL | One-time setup cost |
| Schema Creation | ~0.00001 XLM | ~0.000005 SOL | Per schema deployment |
| Attestation Creation | ~0.00001 XLM | ~0.000005 SOL | Per attestation issued |
| Revocation | ~0.00001 XLM | ~0.000005 SOL | Per revocation action |
Scalability Features
- Off-Chain Indexing: Horizon indexer reduces query load on blockchain nodes
- Batch Operations: Multiple attestations can be processed efficiently
- Caching Layer: Frequently accessed attestations are cached for performance
- Pagination Support: Large result sets are handled through cursor-based pagination
Integration Best Practices
Development Workflow
- Environment Setup: Configure SDK with appropriate network endpoints
- Schema Design: Define or select schemas that match your use case requirements
- Authority Management: Register and verify authority status before issuing attestations
- Error Handling: Implement robust error handling for network and validation failures
- Testing: Use testnet environments for development and testing workflows
Production Considerations
- Key Management: Implement secure storage for authority private keys
- Rate Limiting: Monitor API usage and implement appropriate rate limiting
- Monitoring: Set up alerts for failed attestations and system health issues
- Backup Strategies: Maintain redundant systems for critical attestation workflows