● One source of truth

Status

What runs, what is built but off, what is not ready.

This table is the reference for the project's state. If another page says something different, this page wins — and please tell us. It is updated with every release, and each row names the code version it refers to. Updated 2026-10-25.

Read from the chain right now
Chain id…
Node binary…
Source commit…
Block height…
Governance proposals…
Status by component

“Internal multi-model AI review” means independent read-only review rounds by AI models until they agree (see Security & Audit). It is not an independent human audit — that column says None yet until an external audit is done.

ComponentStatusCode versionInternal reviewExternal reviewNotes
Chain
Sovereign chain sunima_8081-2 (Cosmos SDK + CometBFT + EVM)Running on testnetv17—None yetRe-created 2026-09-02; upgrades only by governance vote (#1 v15, #2 v16, #3 v17).
Operator program x/operators: registration, bond, probationRunning on testnetv17Internal multi-model AI reviewNone yet
Court-order disclosure x/courtorder: intake, vote, threshold decryptionRunning on testnetv16 keys · v17Internal multi-model AI reviewNone yetKey is 6-of-8 across validators, dealt by one party in v16.
Court-order key generated by validators (DKG, 75 %, auto re-share)Built, switched offv17Internal multi-model AI reviewNone yetNeeds the key group enabled by governance.
Validator key groups x/threshold_signatures (DKG, re-share, FROST)Built, switched offv17Internal multi-model AI reviewNone yetEach group is enabled by a governance vote; none enabled yet.
Vault door key Key_A / Key_B (OpenCore)Not readyv17Internal multi-model AI reviewNone yetKeys not generated on the live network yet.
Exit breaker on the private vault · founder pause auto-expiry 72 hRunning on testnetv17Internal multi-model AI reviewNone yet
Address freezingRemovedv14——Removed 2026-07-23. No one can freeze an address.
Privacy
Halo2-KZG confidential deposits and transfers x/layer7_coreRunning on testnetv17In progressNone yetTestnet quality; mainnet privacy layer still being hardened.
In-browser Halo2-KZG proverRunning on testnetweb—None yetShielded send ≈19.5 s.
Bridge
FrostVerifier · SunimaBridge v9 · btUSD on Arbitrum SepoliaRunning on testnetcontracts 2026-10-25Attack-vector review of FrostVerifier + BIP-340 test vectorsNone yetTestnet contracts.
Bridge fast tier on Sunima (validator attestations)Built, switched offv17Internal multi-model AI reviewNone yetGovernance proposal #4 is enabling it.
Bridge attester agents on validatorsNot ready——None yetNext after proposal #4.
Bridge final tier (Ethereum light client)Not ready——None yet
Operators and network
One-command installer operator.sh + signed upgrade kitRunning on testnetkit 2026-10-24.1Internal multi-model AI reviewNone yet
Season 1: quests, operator / validator grants, points → stakeRunning on testnetoff-chain services—None yetTestnet program.
Security and launch
External audit (Sherlock, Pashov Audit Group, Go / Cosmos-SDK specialist)Not ready——None yetFirms confirmed when engaged.
Immunefi bug bountyNot ready———Starts at mainnet.
MainnetNot ready———Gated on the items above. No date.
What is hidden and what is visible (testnet, v17)
StepVisible to everyoneHidden
Enter the private pool (deposit)Funding address, amount, time—
Transfer inside the pool (Halo2-KZG shielded notes)That a private transfer happened, the number of inputs and outputs, the account that broadcast it, timeAmounts, sender and receiver inside the pool, which notes were spent
Leave the pool (exit)Recipient address, amount, timeWhich deposit the money came from
Plain wallet transfers outside the poolEverything, as on any public chain—

So: amounts and links are hidden inside the pool; entering and leaving are public. With little traffic, an observer can try to match entries and exits by amount and timing — the privacy set grows with usage. Splitting amounts and waiting before exit helps. Not yet externally audited.

Who can do what — and what if the founder disappears

Every key or group that can change the network, move protocol funds, approve disclosure or stop something. Team-held keys are listed as such.

RoleHeld byThresholdRotationIf the founder disappears
Chain upgrades and parameters (x/gov)All stakers, by stakeQuorum 67 %, yes 67 %, veto 33.4 % (expedited: 75 %)VoteUnaffected — validators and stakers keep governing.
Validator set12 validators; most stake on foundation-run nodesCometBFT: >2/3 of power signs each blockAnyone can join through the operator programChain keeps running; foundation stake stays delegated.
Founder pauseFounder key1 keyUpgradeNot needed. Any pause expires by itself after 72 h (v17).
Court-order filing gateTwo team keys: automated form check + founder approvalBoth signatures on every orderUpgrade onlyNo new court orders can be filed until governance replaces the keys by upgrade. Known centralisation point; to be replaced before mainnet.
Court-order decryption key8 validators, one share each6 of 8 (75 %)Re-deal by upgrade today; automatic DKG re-sharing built in v17, not yet onUnaffected.
Vault door key (OpenCore: Key_A + Key_B)Key_A: validators (75 %) · Key_B: founder, 4 of 5 partsBoth halvesKey_B recovery: recovery key or 3 of 5 parts + passed vote + 14-day delayNot generated on the live network yet.
Bridge v9 administration (Arbitrum Sepolia)Temporary threshold key held by the teamThreshold Schnorr signature + strict nonceRotate by signed governance call; target: validator key groupRecovery address (team) can rotate; to be replaced by the validator key group.
Stage 1–4 contracts (Arbitrum Sepolia)Founder EOA 0x61DA…1D9f1 keyPlanned Safe multisig, not doneContracts frozen in their current state. Testnet research only; not used by the sovereign chain.
Upgrade release signing (cosmovisor kit)Team key1 keyRe-key by publishing a new kitValidators can still upgrade by hand.
Testnet faucet and foundation delegatorTeam hot keys1 key each—Testnet only. Mainnet has no faucet.