Backup Storage

RGB validation data and channel state depend on persistent node data. Securely retain both the mnemonic and a recoverable archive; do not assume on-chain data can reconstruct all local state.

Export and capability scope

Export node archives through the official product workflow; see node data export.

Select the target node in the official product, confirm the export, wait for the archive to become available, then download and securely retain it as instructed. Export may stop the node. Check its status afterward and resume operation as directed by the product; do not assume automatic restart or fixed downtime.

The public API provides no automatic snapshot queries, rollback, Cloud archive import/restore, IPFS/Arweave replica management or post-deletion recovery. Fixed backup frequency, 180-day retention and disk retention after deletion are not part of the public contract; consult the service agreement.

Self-custody and migration

After downloading, verify integrity information provided by the product, such as archive size and SHA-256, and validate recovery against the node software's actual requirements. There is no public one-click restore SDK. Store archives with controlled access, never publicly share them or write them to application logs.

A single online copy

Only one node may be online with the same channel state. Stop the Cloud node before starting a self-hosted copy to avoid channel penalty risks. Keep mnemonics, backups and API Keys secure.

Creating a new node by name cannot restore the original funds identity. Do not delete the original node before confirming your backup is usable.

Further reading: node management, security and access. For historical design context, see from Cloud hosting to self-hosting; current workflows are defined by the official product and current documentation.