May 15, 2024

The schedule/criteria for automated snapshots is implemented. This consists of two configuration options, both intervals - bytes and confirmations. The node can very rapidly obtain the byte sum of all store headers and bodies. This is checked for each block arrival and the difference from startup is obtained. When this exceeds configured it backs up and resets the startup value. This can lead to a larger than expected gap if the node is stopped and then started, though this is acceptable. If a snapshot is taken close to stop (which should be expected) then this is moot.