PQ-native signing boundary
The exact published TypeScript package used by these docs is @monolythium/[email protected]. It exposes local ML-DSA-65 key derivation, signing, verification, and address helpers. This does not certify an HSM, custody adapter, transaction envelope, fee policy, submission flow, or production exchange integration.
Verified constants in that package are a 1,952-byte public key and a 3,309-byte signature. The signing guide compiles and runs a deterministic local test vector without constructing or submitting a transaction.
Custody boundary
Section titled “Custody boundary”Before using ML-DSA-65 for custody, independently validate the exact cryptographic implementation and signer boundary; key generation and backup; firmware and module behavior; entropy; message-domain separation; address binding; zeroization; concurrency; rate limits; authorization; audit logging; disaster recovery; and transaction review. A package-level local backend is not an HSM integration.
No real funds should be placed on testnet 69420. No supported hot-wallet autosigning or protocol spending-policy path is released. No SLH-DSA account, backup-key, dual-signature, or emergency-rotation path is released.
Deliberate omission
Section titled “Deliberate omission”This page includes no build-sign-submit recipe. A future production transaction guide must be compiled against an exact SDK, exercised against an exact registered runtime, reviewed for custody safety, and coupled to unambiguous submission and reconciliation behavior before publication.