Node Data Export

Node data export backs up or migrates node data out of the cloud. Export is an official product capability and is not offered through the public management API Key today: third parties should start the export, watch progress and fetch the archive through the official product. Note the difference between the public API and console-provided capabilities; do not assume an API Key can call export endpoints.

Archive contents

The node archive contains node and wallet state so the node can be rebuilt through the recovery flow its software supports. The archive typically includes:

• Node and wallet state: seed/master fingerprint, node alias, chain parameters
• Channel state and RGB validation data, consignments
• An archive manifest (format version, network, creation time, file size and SHA-256)

Export may stop the node. After it completes, check the node state and restore operation per the product's guidance; do not assume an automatic restart or a fixed downtime. Exact archive contents and retention follow what the official product shows.

Safety notes

Keep backups safe and follow the recovery flow the node software supports. Only one node may be online for a given channel state: when migrating, stop the cloud node first and then run the self-hosted copy, to avoid channel penalties. Platform automatic backups do not replace your own backups.

Further reading: Storage Backup, Node Compute Engine, Node Management.