Threat model

Locked

The registered public-network profile is a value-less, wipeable development testnet. Current endpoint health is reported separately. This page is not a security certification, production operating procedure, custody recommendation, economic-loss bound, or substitute for source review and an independent audit.

Verified boundary

The registered topology is four clusters of ten operators; each cluster certificate requires seven independent ML-DSA-65 signatures.
The mempool is plaintext, so pending contents may be observable.
The registered transport profile uses ML-KEM-768 Noise.
Mainnet is not running, and no production uptime, recovery-time, finality, slashing, insurance, or asset-redemption promise is made.

Risks to evaluate

Independent review must cover consensus safety and liveness under Byzantine and network faults; equivocation and fork evidence; key theft and signing compromise; implementation and supply-chain failures; endpoint identity and re-genesis; denial of service; state corruption; indexer divergence; wallet review and address substitution; plaintext-mempool disclosure; operator concentration; and incident coordination.

Design names such as DVT, deterministic DAG ordering, hardened operator OS, or post-quantum algorithms do not eliminate these risks. In particular, deterministic ordering is not transaction confidentiality or a guarantee that MEV is absent.

Unavailable safeguards and value paths

No active in-tree bridge or bridge drain-cap system, CLOB market, private-value path, agent spending policy, escrow, autonomous remediation, or SLH-DSA emergency-rotation flow may be assumed. The public docs also do not publish a machine-executable incident runbook for real funds.

For an incident, preserve evidence, verify the complete registry/runtime identity, stop ambiguous writes, and follow authenticated instructions issued for the exact active release. Do not improvise recovery calls from historical whitepaper text or an agent-generated plan.