Architecture
BlockVault is structured as a mobile-first platform with a clear separation between client-side and server-side responsibilities.
Client Side (Mobile App)
The app is built with Ionic + Capacitor and runs on both Android and iOS. All sensitive operations happen on-device:
Mobile App (Ionic + Capacitor)
├── Wallet Core
│ ├── Key derivation (BIP-39/32/44)
│ ├── Transaction signing
│ ├── AES-256-GCM encryption
│ └── Hardware-backed storage (Keystore / Keychain)
├── AI Assistant
│ ├── Gemma 3 1B (on-device inference)
│ ├── ReAct agent (LangGraph)
│ └── 10 wallet tools
├── Web3 Browser
│ ├── EVM provider (MetaMask-compatible)
│ ├── Solana provider (Phantom-compatible)
│ └── Cosmos provider (Keplr-compatible)
├── Trading (dYdX v4)
│ ├── Order construction & local signing
│ ├── Agent wallet (limited-permission trading key)
│ └── Real-time market data
└── Device Integrity
├── Google Play Integrity (Android)
└── App Attest (iOS)Server Side (Backend)
A Django REST Framework API handles user registration, referral processing, and reward distribution:
Backend (Django + DRF)
├── Wallet Registration
│ ├── Telegram OAuth verification
│ ├── SIWE (Sign-In with Ethereum) verification
│ └── Device integrity token validation
├── Referral System
│ ├── Code generation & application
│ ├── Automatic BLVC reward transfer
│ └── Daily/max limits enforcement
├── Rewards Vesting
│ ├── RewardsVesting smart contract integration
│ └── Beneficiary registration (single/weekly)
└── Infrastructure
├── AWS Lightsail (containers)
├── S3 (media + ML models)
└── PostgreSQLBlockchain Interactions
The app interacts directly with blockchain networks — the backend is not involved in transaction signing or broadcasting:
| Component | Networks | Interaction |
|---|---|---|
| Wallet | 12 blockchains | Direct RPC calls from device |
| Trading | dYdX v4 (Cosmos) | Orders signed locally, broadcast to validators |
| Rewards | Ethereum Mainnet | Backend transfers BLVC via smart contracts |
| Web3 Browser | EVM, Solana, Cosmos | Provider injection, local signing |
Security Layers
Layer 1: App Integrity (Play Integrity / App Attest)
Layer 2: Telegram OAuth (identity verification)
Layer 3: SIWE (wallet ownership proof)
Layer 4: AES-256-GCM + PBKDF2 (mnemonic encryption)
Layer 5: Hardware TEE / Secure Enclave (storage encryption)