Concepts
Global Accounts
Global Accounts unify state between Solana-native programs and external execution environments. They allow builders to keep a single canonical ledger while running custom logic (EVM, SVM extensions, or domain-specific runtimes) without juggling multiple wallets and derivation paths.
Structure
Each Global Account is a composite object that references Solana accounts, extension metadata, and role-based policies. The account carries its own capability graph so you can grant execution permissions to RFQ partners, custodians, or off-chain automation services without sharing private keys.
State Payload
- Owner + delegate public keys
- Linked Solana accounts (ATA, PDAs, system accounts)
- Extension manifests (EVM slot, WASM runtime, etc.)
- Compliance tags + audit references
Policy Matrix
- Action-based permissions (reserveSlot, submitRFQ, cancel)
- Rate limits and per-lane budgets
- Geographic or compliance restrictions
- Expiration + revocation hooks
Why It Matters
- Eliminates state fragmentation across RFQs, MEV relays, and liquidity partners.
- Supports multi-team operations where trading desks, risk, and compliance need separate keys.
- Enables audit-ready history because every Reservation or execution references the same account ID.
- Improves security by scoping permissions instead of sharing hot wallets.