Protocol
Architecture
AIDOS is a four-layer stack. Applications sit on top, the SDK exposes protocol calls, a privacy layer enforces the guarantees, and Solana provides settlement.
The four layers
- Application — the Aidos App (web + iOS), plus anything built on the SDK: Telegram bots, white-label neobanks.
- Protocol (SDK) — a single surface of calls:
createAccount(),deposit(),spend(),swap(),deployAgent(),issueCard(). - Privacy — three engines that enforce the guarantees: the ZK Shield (balances and transfers), the TEE Runtime (agents and attestation), and the Darkpool (batch auctions and ZK settlement).
- Settlement — Solana L1: ZK proofs verified on-chain, card settlement over USDC/Mastercard, and IBAN via a licensed partner.
┌───────────────────────────────────────────────┐
│ APPLICATION Aidos App · Telegram · White-label │
├───────────────────────────────────────────────┤
│ PROTOCOL Aidos SDK │
│ createAccount · deposit · spend · swap │
│ deployAgent · issueCard │
├───────────────────────────────────────────────┤
│ PRIVACY │
│ ZK Shield TEE Runtime Darkpool │
│ (balances) (agents) (ZK settle) │
├───────────────────────────────────────────────┤
│ SETTLEMENT Solana L1 │
│ ZK proofs · card settlement · IBAN partner │
└───────────────────────────────────────────────┘Stack specification
| Layer | Technology |
|---|---|
| ZK proving | Light Protocol / Helius ZK; Groth16, sub-second client-side. |
| TEE runtime | Phala Network (Intel TDX); GPU TEE for AI inference. |
| Darkpool | Custom batch auction + ZK settlement, Solana-native. |
| Card issuance | Mastercard partner (Bleap / Gnosis Pay model). |
| IBAN rails | Licensed EMI partner; SEPA + SWIFT. |
| Chain | Solana; 400 ms finality, $0.00025 fees. |
| Client | React Native (iOS/Android) + Web PWA; self-custody via the Solana Mobile SDK. |
Why Solana
400 ms finality and $0.00025 fees make consumer-grade, high-frequency private banking economical, and the chain has a maturing privacy stack (Helius/Light ZK, Arcium MPC, PrivacyCash) to build on.
The guarantees these layers enforce are spelled out in the Privacy Doctrine, and how to check them is covered in Verification.