Prospective integration checklist
Planned
No production exchange, custody, deposit, withdrawal, hot-wallet, bridge, or delegated-spending integration is certified by this page. The registered public-network identity is value-less and resettable testnet 69420; registry identity does not prove liveness. Do not use real funds.
Before technical evaluation
Section titled “Before technical evaluation”- Confirm the exact current chain-registry entry, full genesis hash, release, commit, and binary digest.
- Confirm that mainnet is actually registered and running. Chain ID 69422 is currently reserved only.
- Obtain the precise source, audit scope, open findings, reproducible artifacts, and incident contacts.
- Have legal, compliance, custody, accounting, and market-risk owners approve the scope.
Before custody or signing
Section titled “Before custody or signing”- Independently validate ML-DSA-65 support in the exact signer/HSM and firmware; do not rely on vendor names in old docs.
- Validate address derivation and bech32m rendering against exact-version test vectors.
- Define nonce, replay, fee, resubmission, reconciliation, key ceremony, backup, rotation, and disaster-recovery controls.
- Keep automated signing and withdrawal disabled until the exact released transaction contract is reviewed end to end.
- Do not rely on local MCP caps or prototype spending-policy encoders to protect value.
- Do not pre-register or use an unreleased alternate-signature backup key.
Before deposits or withdrawals
Section titled “Before deposits or withdrawals”- Pin chain ID and full genesis hash at every endpoint and halt on any mismatch or re-genesis.
- Credit only from independently verified committed state under a versioned finality policy; never from the plaintext mempool or a webhook alone.
- Exercise duplicate, delayed, dropped, malformed, wrong-chain, reset, unavailable-indexer, and ambiguous-submit cases.
- Run reconciliation against independent data paths and preserve an immutable audit trail.
- Publish clear network, asset, testnet-value, custody, confirmation, reset, and incident disclosures.
Explicitly out of scope
Section titled “Explicitly out of scope”There is no supported in-tree bridge, Foundation-operated production route, agent-wallet, protocol spending policy, booking, payment, escrow, dispute, or review path. Do not add any of them to a listing checklist until a separately versioned and audited release exists.