Blog · 2026-09-26
Building AEGIS: Architecture, Wallets and Roadmap
An engineering view of AEGIS: gateway-first microservices, custodial wallet derivation, audit logging, and a roadmap separated into live, in-development, and planned.
AEGIS is built the way infrastructure should be: boring components, clear contracts between them, and a roadmap that distinguishes what exists from what is being built. This is the engineering view.
Architecture
AEGIS is a gateway-first microservices system. One gateway handles authentication, rate limiting, and routing. Behind it, each functional domain runs as an isolated engine: wallet vault, swap, treasury, transfer, identity, notifications, rates, market, risk, compliance, and the AI orchestrator that routes user intent to specialized reasoning engines. Clients — web and Android — hold no business logic; they call the gateway. Production identity is Firebase Authentication; production data is Supabase. These were deliberate choices, documented in the architecture, not accidents to be reversed.
Wallets
Phase One wallets are custodial. Wallet addresses are derived deterministically — the same account always maps to the same address, and addresses are treated as immutable: they are never re-derived into different addresses or overwritten. Keys are managed server-side; users operate their wallets through their AEGIS accounts (sign-in via email or Google). Transaction construction and signing happen server-side, and broadcasts go to BNB Smart Chain. Swaps route through PancakeSwap, with a dedicated CZN/WBNB pair contract for the CZN token. The design rule that governs all of this: nothing may orphan an existing user's wallet. Any change to wallet architecture requires a published migration plan first.
Audit and stability discipline
Platform events are written to append-only audit logging. Deployment is serverless (Vercel) with CI producing Android builds. The project runs with an explicit stability rule: crashes are fixed first, then broken pages, then UI, then features — and before any change that touches users, the question is asked: will this affect existing production users? If yes, the change ships with an inspection, a blast radius estimate, and a rollback plan.
Roadmap, honestly labeled
Live: wallets, swaps, treasury fee ledger, notifications, AI assistant, this website and docs. In development: the multi-rail Smart Router (banking, mobile money, Stellar, Circle Arc/USDC), the Android app (built; Play Store release pending), the developer SDK. Planned: CZN fee discounts, rewards, governance; a non-custodial wallet option; more rails and coverage. Dates are not published until features ship — the changelog is the record of what is real.
More: roadmap, changelog, AEGIS.