This document provides a high-level overview of the Ancore system architecture.
┌─────────────────────────────────────────────────────────────┐
│ User Applications │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Extension │ │ Mobile │ │ Web │ │
│ │ Wallet │ │ Wallet │ │ Dashboard │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
└────────────────────────┬────────────────────────────────────┘
│
│ Ancore SDK
│
┌────────────────────────▼────────────────────────────────────┐
│ Core SDK Layer │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Account │ │ Session │ │ TX │ │
│ │ Mgmt │ │ Keys │ │ Builder │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
└────────────────────────┬────────────────────────────────────┘
│
│
┌────────────────────────▼────────────────────────────────────┐
│ Stellar/Soroban Layer │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Account │ │ Validation │ │ Invoice │ │
│ │ Contract │ │ Modules │ │ Contract │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
└────────────────────────┬────────────────────────────────────┘
│
│
Stellar Network
Smart accounts are the foundation of Ancore. Unlike traditional accounts that use a single private key for all operations, smart accounts are programmable contracts that can implement custom validation logic.
Key Features:
- Custom signature validation
- Multi-signature support
- Session keys for seamless UX
- Upgradeability
- Recovery mechanisms
Ancore brings ERC-4337-style account abstraction to Stellar/Soroban:
- Validation: Custom logic determines if a transaction is valid
- Execution: Transactions are executed on behalf of the account
- Paymaster: Optional third-party fee payment
- Bundling: Multiple operations in a single transaction
Session keys enable seamless UX by allowing time-limited, permission-scoped signing keys:
- User signs once to create a session
- Session key signs subsequent transactions
- Automatic expiration
- Granular permissions
- Revocable at any time
1. User initiates transaction
↓
2. Wallet creates UserOp
↓
3. Session key signs (if available)
↓
4. Submit to relayer (optional)
↓
5. Relayer submits to network
↓
6. Account contract validates
↓
7. Transaction executes
↓
8. Events emitted
1. Generate key pair
↓
2. Deploy account contract
↓
3. Initialize with owner
↓
4. Set up validation modules
↓
5. (Optional) Configure recovery
- User's Private Key: Ultimate source of authority
- Account Contract: Enforces validation rules
- Validation Modules: Pluggable validation logic
- Session Keys: Limited, scoped permissions
- Relayers: Untrusted transaction submitters
- Contract Level: Validation, access control, nonce management
- SDK Level: Transaction building, signing, encryption
- Application Level: UI security, phishing protection
- Minimal on-chain storage
- Efficient validation algorithms
- Batch operations
- Off-chain computation where possible
Optional relayer network for:
- Meta-transactions
- Gasless transactions
- Transaction batching
- Network fee abstraction
- Core SDK: JavaScript/TypeScript SDK for building applications
- Contract ABIs: Direct contract interaction
- REST API: Optional backend services
- WebSocket: Real-time updates
- Browser Extension: Web3 wallet extension
- Mobile Apps: iOS/Android wallets
- Web Dashboard: Account management interface
- Cross-chain support via bridges
- Privacy features (zk-proofs)
- Advanced recovery mechanisms
- Decentralized relayer network
- AI-powered financial agent
Last Updated: January 2026