Flexible Backup Restoration

There are three strategies for flexible backup restoration:

Manual restore strategy: Users starts the restore function by executing bucket restore command. The storage node only verifies the hash value of the data by default. It can also enable proof verification through the --proof command option. In --proof mode, the storage node will also generate proof for the data and conduct self-verification. For data with incorrect hash values, failed proof self-verification, or data lost, the storage node will first download the data from the network and attempt to pass self-verification. If the self-verification fails, the network data lost will be reported. Reporting data lost does not penalize the storage node.

Scheduled restore strategy: The restore function is automatically executed internally through the storage node service, and this mode is the same as bucket restore mode.

Event listening strategy: This data restore strategy is triggered by listening to the penalty events. When a data proof of a storage node failed verification, the network will punish the storage node. When a storage node hears its own penalty event, it will immediately start the restore strategy for its data, and the restoring process is the same as bucket restore.