Phase 0 · deployment status.
The complete v1 system, thirty-five contracts: is live on Base Sepolia testnet, deployed 2026·07·01 in a single broadcast. This page states exactly what is running, who holds which keys, and what has deliberately not been switched on. Testnet, pre-audit; a single external audit of the complete v1 system gates mainnet.
Everything on this page is testnet. Base Sepolia, chainId 84532. No mainnet contract exists. No real money moves through any of it, and there are no real users or volume to report. Those statements will change in governedpublished steps, not quietly.
What went live on 2026·07·01
Phase 0 closed its build with a full fresh redeploy: the entire v1 surface deployed as one unit rather than patching earlier testnet contracts in place. The reason is audit honesty, the system the auditors read is byte-for-byte the system that is running, with no upgrade history to reconstruct.
| Fact | State |
|---|---|
| Network | Base Sepolia (chainId 84532), testnet only |
| Deployed | 2026·07·01, one broadcast, 274 transactions, all successful |
| Contracts | 35, identity, trust, recovery, compliance, payments, savings, reputation, agent economy |
| Source-verified | 34 of 35 on Basescan |
| Audit | Not yet begun, one external audit of this complete system gates mainnet |
The one verification gap is ComplianceCascadea cosmetic compilation-metadata mismatch in the Basescan verifier, not a deployment or functional issue; the contract is live and behaves as its published source. Every address, with per-contract responsibilities and Basescan links, is in the contract registry. The architecture behind the surface is in the whitepaper.
Who holds which keys
Deployment ends with the deployer holding nothing. The production role model was handed over in the same broadcast and asserted on-chain afterward:
| Authority | Held by | Scope |
|---|---|---|
DEFAULT_ADMIN + UPGRADER | TimelockController, 14-day delay | Role administration and contract upgrades. Nothing changes faster than fourteen days. |
PAUSER + operational roles | Foundation multi-sig | Surgical pause and day-to-day operations. |
| Deployer | Nothing | Renounced every setup role, confirmed on-chain on every contract. |
An upgrade travels a fixed path: an RFC with a 14-day public comment window, Technical Advisory Council review, approval by 5 of the 9 multi-sig signers, directors, technical advisors, and ecosystem representatives, and then the 14-day timelock. A bounded emergency pause exists (Charter §4.3): 7 of 9 signers, capped at fourteen days unless community ratification extends it. Emergency patches may bypass the RFC; nothing bypasses the timelock. On-chain voting is the Year-3 roadmap direction, not a live mechanism. A deliberate class of exceptions to the role model: the user-controlled recovery contracts, GuardianRegistry and AbandonmentRegistryare non-upgradeable, non-pausable, and role-free, because user-controlled state sits outside Foundation authority. The full thirteen Articles are in the Foundation charter.
Live, and deliberately dormant
Two whitelists matter here, and only one is armed. ProtocolConfig's five-token launch whitelist is live: USDC, USDT, EURC, cbBTC, and WETH, each with per-token fee configuration. PaymentsRouter is deployed and verified, but its own routing whitelist is empty, the payment rail is dormant. Arming it is a governance action through the 14-day timelock, not a code change; once armed, routing carries the 0.05% protocol fee to Treasury. Shipping the rail dormant is intentional: value should not move, even on testnet, until the arming itself has passed through the same process mainnet will require.
What remains is not "deploy"
The deployment is done. Three tracks remain, none of them a redeploy:
- The wedge. The first usable SDK·
@adunai/sdkin-repo under Apache-2.0, not yet on npm; npm publication lands with the Phase 1 public release, plus test transactions flowing on the live testnet through the cross-border SMB demo dApp, Sign in with Adunaiand the aID reference identity client (a reference-wallet design preview is public; a forkable wallet scaffold is a Phase 1+ decision). - The pre-mainnet audit. One external audit of the complete, running v1 system. Mainnet follows it, never precedes it. See security.
- Phase-2 arming. Rate-signer registration, economic seeding of the settlement layer, and granting the dormant inter-contract roles, each a future timelock or Foundation governance action.
The phase ladder
| Phase | Focus | Where it stands |
|---|---|---|
| 0 | Protocol foundation. 35 contracts on private testnet, first usable SDK, demo dApp, first pilot transaction. | Now |
| 1 | Public testnet. Wallet privacy primitives, stealth addresses per EIP-5564, per-counterparty DID rotation, selective disclosure. Public SDK on npm. The bug bounty opens. | Next |
| 2 | The external audit of the complete v1 system, then a controlled mainnet launch. Off-chain rails, mobile-money bridges, the agent network. First real users. | Gated on Phase 1 |
| 3 | Local-currency stablecoin readiness, cXAF, cNGN, cKES, each backed 1:1 by its own central bank's reserves. Multi-chain expansion. Ecosystem grants at scale. | Roadmap |
| 4+ | Long-term decentralization, continental scale, Foundation hand-off toward community governance. | Roadmap |
Stated plainly
This page is a credibility surface, so the caveats are part of the record:
- Pre-audit. The 35 contracts are live on testnet; the external audit has not begun. Nothing here is audited code.
- No users, no volume. Every transaction on Base Sepolia is a test transaction.
- The Foundation is in pre-formation. Mauritius is the intended jurisdiction, subject to counsel.
- The grants program is launching. No awards have been made.
- Neutrality. This page names no commercial builder. aID is a reference implementation and a reference wallet is held open for Phase 1+ (a design preview is public); the Foundation holds no equity in any builder, and no one picks winners.
Addresses live in the contract registryand the project as a whole is at adunai.org.