Backup and restore a node

Locked

No public production node backup or restore procedure is certified. Do not copy key locations, state paths, commands, or retention rules from historical drafts.

A future runbook must be bound to an exact signed node release and selected registered network identity. It must separate irreplaceable key material from reproducible node state, define encryption and offline custody, prevent accidental double-signing, verify restore integrity in isolation, and include revocation, audit, and disaster-recovery tests.

The Foundation-operated development testnet is value-less and resettable; it is not evidence that a production recovery path is safe. Consumer wallet recovery is a separate boundary described at Recovery phrase.