Sync Besu
Besu supports two node types, commonly referred to as full nodes and archive nodes.
Full nodes have the current state of the blockchain. They can't serve the network with all data requests (for example, the balance of an account at an old block). Full nodes can guarantee the latest state for the blockchain (and some older states, but not all). You can check current balances, sign and send transactions, and look at current dapp data.
Archive nodes also store the intermediary state of every account and contract for every block since the genesis block. Archive nodes can do everything full nodes do, and they can access historical state data. Archive nodes require more disk space than full nodes.
Besu must connect with other peers to sync with the network. If your node is having trouble peering, try troubleshooting peering.
Sync times
To sync with a public network, Besu runs two processes in parallel: the world state sync and the blockchain download.
The following table shows the average world state sync time for each sync mode on Mainnet. All times are hardware dependent; this table is based on running AWS instances m6gd.2xlarge. Each sync mode also has its own world state database size.
| Sync mode | Time to sync world state | Disk usage |
|---|---|---|
| Snap | ~6 hours | Average disk |
| Checkpoint | ~5 hours | Smallest disk |
| Fast | ~1.5 days | Average disk |
| Full | ~weeks | Largest disk |
As of late 2022, an average Mainnet snap sync consumes around 750 GB using Bonsai Tries. Read more about storage requirements across data storage formats and sync modes.
Testnets take significantly less time and space to sync.
While the world state syncs, Besu downloads and imports the blockchain in the background. The blockchain download time depends on CPU, the network, Besu's peers, and disk speed. It generally takes longer than the world state sync.
Besu must catch up to the current chain head and sync the world state to participate on Mainnet.
Storage
You can store the world state using Forest of Tries or Bonsai Tries. We recommend using Bonsai Tries for the lowest storage requirements.
Run a full node
You can run a full node using snap synchronization (snap sync), checkpoint synchronization (checkpoint sync), or fast synchronization (fast sync).
Snap synchronization
We recommend using snap sync over fast sync because snap sync can be faster by several days.
We recommend using snap sync with the Bonsai data storage format for the fastest sync and lowest storage requirements.
Enable snap sync using --sync-mode=X_SNAP. You need Besu version 22.4.0 or later to use snap sync.
Instead of downloading the state trie node by node, snap sync downloads as many leaves of the trie as possible, and reconstructs the trie locally.
You can't switch from fast sync to snap sync. If your node is blocked in the middle of a fast sync, you can start over using snap sync instead by stopping the node, deleting the data directory, and starting over using --sync-mode=X_SNAP.
You can restart Besu during a snap sync in case of hardware or software problems. The sync resumes from the last valid world state and continues to download blocks starting from the last downloaded block.
See how to read the Besu metrics charts when using snap sync.
Checkpoint synchronization
Checkpoint sync is an early access feature.
Enable checkpoint sync using --sync-mode=X_CHECKPOINT. You need Besu version 22.4.3 or later to use checkpoint sync.
Checkpoint sync behaves like snap sync, but instead of syncing from the genesis block, it syncs from a specific checkpoint block configured in the Besu genesis file.
Ethereum Mainnet and the Goerli testnet configurations already define default checkpoints, so you don't have to add this yourself.
For other networks, you can configure a checkpoint in the genesis file by specifying the block hash, number, and total difficulty as in the following example.
"checkpoint": {
"hash": "0x844d581cb00058d19f0584fb582fa2de208876ee56bbae27446a679baf4633f4",
"number": 14700000,
"totalDifficulty": "0xA2539264C62BF98CFC6"
}
If using Clique consensus, the checkpoint must be the beginning of an epoch.
If you enable checkpoint sync without a checkpoint configuration in the genesis file, Besu snap syncs from the genesis block.
You can restart Besu during a checkpoint sync in case of hardware or software problems. The sync resumes from the last valid world state and continues to download blocks starting from the last downloaded block.
Fast synchronization
It might become impossible to sync Ethereum Mainnet using fast sync in the future. If you sync for the first time or ever need to re-sync, update Besu to a version that supports newer sync methods.
Enable fast sync using --sync-mode=FAST.
Fast sync downloads the block headers and transaction receipts, and verifies the chain of block headers from the genesis block.
When starting fast sync, Besu first downloads the world state for a recent block verified by its peers (referred to as a pivot block), and then begins fast sync from the genesis block.
Fast sync is the default for named networks specified using the --network option, except for the dev development network. It's also the default if connecting to Ethereum Mainnet by not specifying the --network or --genesis-file options.
Using fast sync with private transactions isn't supported.
You can observe the besu_synchronizer_fast_sync_* and besu_synchronizer_world_state_* metrics to monitor fast sync.
When fast syncing, block numbers increase until close to the head block, then the process pauses while the world state download completes. This may take a significant amount of time depending on world state size, during which the current head block doesn't increase. For example, Mainnet may take several days or more to fast sync. Fast sync time may increase because Besu picks new pivot blocks, or because peers prune the world state before it completes downloading.
When running Besu on some cloud providers, a known RocksDB issue causes fast sync to fail occasionally. The following error is displayed repeatedly:
EthScheduler-Services-1 (importBlock) | ERROR | PipelineChainDownloader | Chain download failed. Restarting after short delay.
java.util.concurrent.CompletionException: org.hyperledger.besu.plugin.services.exception.StorageException: org.rocksdb.RocksDBException: block checksum mismatch:
The failure has been seen on AWS and Digital Ocean. On AWS, A full restart of the VM is required to restart the fast sync. Fast sync isn't currently supported on Digital Ocean.
When fast syncing, the pending state nodes count is the number of nodes yet to be downloaded, and it should change constantly. Pending state nodes trend to 0 during fast sync and then goes to 0.
If the number stays constant, this could mean your node isn't syncing against any peers.
In the following example, the pivot block is 0 and the pending state nodes value is constant. This means the node isn't syncing against any peers. The fact that state nodes have been downloaded means at some stage it was syncing.
The easiest solution in this scenario is to restart fast sync to obtain a new pivot block.
Run an archive node
To run an archive node, enable full synchronization (full sync) using --sync-mode=FULL.
Full sync starts from the genesis block and reprocesses all transactions.