Bitcoin: Loading wallet produces “last wallet synchronisation goes beyond pruned data” after a few days on a pruned bitcoin core node

Bitcoin Node Slicing Issues and Solutions

Since my last update, Bitcoin Core nodes can sometimes experience wallet sync issues, resulting in errors like “last wallet sync exceeds truncated data.” However, by understanding the root cause and implementing a few tweaks, you should be able to run a truncated Bitcoin Core node on Linux indefinitely without encountering this issue.

Problem: Slicing

Bitcoin Core’s truncating mechanism is designed to reduce storage requirements for nodes with low network activity. During truncating, certain data structures are removed from the blockchain, which can lead to synchronization issues if not managed properly. The “last wallet sync exceeds truncated data” error typically occurs when a node attempts to update its local wallet information after a truncating, but cannot find enough synchronized data to match the block headers.

Causes of Slicing Errors

Before we dive into the solutions, let’s briefly discuss why slicing errors can occur:

• High transaction fees or frequent transactions

• Limited network activity (e.g., a node that hasn’t been updated in months)

• Insufficient storage capacity on the node

Solutions to Resolve Slicing Errors

To avoid or resolve slicing errors, consider implementing the following strategies:

1.
Increase Network Activity

If possible, try to increase your network activity by sending more transactions or paying higher fees. This will help move the node away from a node with low activity and reduce the likelihood of slicing errors.

2.
Adjust Transaction Fees

Reduce transaction fees to encourage more frequent transactions, which should help keep the node active and reduce slicing errors.

3.
Optimize Storage

If you are using limited storage capacity, consider increasing it or switching to a larger storage model that can meet your needs.

4.
Enable Advanced Sync

In Bitcoin Core 0.20.1 and later, an advanced sync method called “batch” is available for pruning nodes. To enable batch sync:

• Download the Bitcoin Core package from the official website.

• During the installation process, select the option to use batch sync.

• Run ./bitcoincore-cli --version after installation.

5.
Disable Pruning

If none of the above solutions work, you may need to disable pruning completely:

• Go to your Bitcoin Core node’s configuration file (~/.bitcoincore/config.json) and find the pruning field.

• Set prune to `false.

6.
Use a custom configuration

If disabling slicing doesn't work, you can try creating a custom configuration:

• Create a new file calledbitcoin.conf` in your home directory with the following content:

[heart]
slicing = false
[wallet]

Then restart your Bitcoin Core node.

7.
Consider running on a hardware wallet

If you are having issues with slicing errors and cannot resolve them using software solutions, it may be worth considering running your Bitcoin wallet on a hardware wallet such as Ledger or Trezor. These devices are designed to keep your funds safe and can prevent slicing errors.

Conclusion

Slicing errors on Bitcoin Core nodes can occur due to a variety of factors such as low network activity, insufficient storage capacity, or high transaction fees. By implementing the solutions above and being aware of the possible causes, you should be able to run a hacked Bitcoin Core node on Linux indefinitely without encountering hacking errors.