Break-glass cryptographic migration
There is no supported break-glass cryptographic migration procedure in the active release. ML-DSA-65 is the released account-signing path; no SLH-DSA account, backup-key, dual-acceptance, key-rotation, freeze-and-claim, or automatic emergency-fork path is available.
Do not generate alternate keys, pre-register a prototype backup, patch algorithm identifiers, or rehearse value-bearing transactions from historical whitepaper text. Those steps would invent a protocol and wallet contract that the active release does not provide.
Any future migration requires, at minimum, a threat-specific design; cryptographic review; protocol and wallet implementation; compatibility and downgrade analysis; test vectors; recovery semantics; independently rehearsed operator choreography; signed release artifacts; registry updates; and public activation criteria. Until then, a credible break requires coordinated incident analysis and a separately released response—not this page.