Compliance and disclosures
This page is general product disclosure, not legal advice. An integrator is responsible for its own licensing, KYC/AML, sanctions, custody, tax, consumer-protection, market-abuse, and jurisdictional analysis.
Mandatory product boundary
Section titled “Mandatory product boundary”- The only registered public-network identity is value-less, wipeable testnet 69420. Its RPC was observed stale/degraded on 2026-07-16. Do not accept deposits of real value or represent it as mainnet.
- Mainnet chain ID 69422 is reserved only; no mainnet network, genesis, or launch date is announced here.
- The mempool is plaintext. Do not promise an encrypted or private transaction-submission lane.
- ML-DSA-65 is the released account-signing path described by the current SDK. No SLH-DSA account, backup-key, or emergency-rotation product is released.
- No in-tree bridge or Foundation-operated production route is available.
- Agent-wallet custody, spending policy, signing, submission, booking, payment, escrow, dispute, and review paths are unavailable.
- An SDK encoder, reserved identifier, old error name, or historical whitepaper section is not activation or audit evidence.
Audit posture
Section titled “Audit posture”The public docs do not claim that unreleased bridge, agent-commerce, spending-policy, escrow, proof-verifier, or recovery surfaces have completed an audit. Before production integration, request the precise source revision, release artifact, audit scope, open findings, remediation evidence, and deployment/activation record for every surface in scope.
Internal plans and raw security material are not public documentation. Public summaries should disclose scope and limitations without publishing secrets, private infrastructure, credentials, exploit details that remain under coordinated remediation, or internal-only documents.
Integrator checklist
Section titled “Integrator checklist”- Pin chain ID and the full genesis hash from the current registered profile.
- Treat any reset or genesis mismatch as a new network.
- Clearly label testnet balances as having no real-world value.
- Keep custody and signing disabled until a separately reviewed production release exists.
- Apply your own sanctions and jurisdiction controls; do not infer them from this site.
- Publish your own audit, custody, incident-response, and risk disclosures.