Berachain Node Snapshot

Chain ID: mainnet-beacon-80094 | Current Node Version: v1.1.3

Latest
Block Height
Size
Timestamp
Download
4424702 115 GB 6 hours ago berachain_4424702.tar.lz4

Our Berachain Snapshot Server Setup

We take one node snapshot every day. We then delete all the previous snapshots to free up the space on the file server.

This guide assumes that you use reth for the execution client and the reth data is stored in the ~/.beacond/reth folder.

How To Process Berachain Snapshot

Install lz4 if needed

sudo apt install lz4

Download the snapshot

wget -O berachain_4424702.tar.lz4 https://snapshots.polkachu.com/snapshots/berachain/berachain_4424702.tar.lz4 --inet4-only

Stop your node

sudo service berachain stop
sudo service berachain_reth stop

Reset your node. This will erase your node database. If you are already running validator, be sure you backed up your priv_validator_key.json prior to running the the command. The command does not wipe the file. However, you should have a backup of it already in a safe location.

WARNING: If you use this snapshot on a validator node during a chain halt, make sure you back up priv_validator_state.json and then replace it after the snapshot is extracted but before you start the node process. This is very important in order to avoid double-sign. When in doubt, reach out to the project team.

# Back up priv_validator_state.json if needed
cp ~/.beacond/data/priv_validator_state.json  ~/.beacond/priv_validator_state.json

# Reset cometbft data
beacond unsafe-reset-all --home $HOME/.beacond --keep-addr-book

# Reset reth data
rm ~/.beacond/reth/db -rf
rm ~/.beacond/reth/static_files -rf

Decompress the snapshot to your database root location. You database location will be something to the effect of ~/.beacond depending on your node implementation.

lz4 -c -d berachain_4424702.tar.lz4  | tar -x -C ~/.beacond

If everything is good, now restart your node

sudo service berachain start
sudo service berachain_reth start

Remove downloaded snapshot to free up space

rm -v berachain_4424702.tar.lz4

Make sure that your node is running

sudo service berachain status
sudo service berachain_reth status
sudo journalctl -u berachain -f
sudo journalctl -u berachain_reth -f