Sync from a trusted node
This feature is available from
When you start the beacon node for the first time, it connects to the beacon chain network and starts syncing automatically - a process that can take several days.
Trusted node sync allows you to get started more quickly by fetching a recent checkpoint from a trusted node - you can get started in minutes instead of days.
To use trusted node sync, you must have access to a node that you trust and that exposes the Beacon API (for example a locally running backup node).
Should this node, or your connection to it, be compromised, your node will not be able to detect whether or not it is being served false information.
It is possible to use trusted node sync with a third-party API provider -- see here for how to verify that the chain you are given corresponds to the canonical chain at the time.
A list of community-operated checkpoint sync nodes can be found here - always verify after after a checkpoint sync that the right chain was provided by the node.
Perform a trusted node sync
Make sure to replace
http://localhost:5052 in the commands below with the appropriate endpoint of the trusted beacon node.
http://localhost:5052 is the default endpoint exposed by Nimbus, but this is not consistent across all clients.
For example, if your trusted node is a Prysm node, it exposes
127.0.0.1:3500 by default. Which means you would run the commands below with
The path specified for
--data-dir must be an empty directory as trusted node sync needs to be started from a fresh database.
To start trusted node sync, run:
If the command was executed succesfully, following log lines will be visible:
After this the application will terminate and you can now start the beacon node as usual.
Because trusted node sync by default copies blocks via REST, you may hit API limits if you are using a third-party provider. If this happens to you, you may need to use the
--backfill option to delay the backfill of the block history.
Verify you synced the correct chain
When performing a trusted node sync, you can manually verify that the correct chain was synced by comparing the head hash with other sources (e.g. your friends, forums, chats and web sites). If you're syncing using your own backup node you can retrieve the current head from the node using:
head root is also printed in the log output at regular intervals.
The same Beacon API request works with any API provider.
For example, to compare it out with our mainnet testing server, you can run:
curl -X GET http://testing.mainnet.beacon-api.nimbus.team/eth/v1/beacon/blocks/head/root
Sync deposit history
This feature is available from
--with-deposit-snapshot allows syncing deposit history via REST, avoiding the need to search the execution client for this information and thus allowing the client to more quickly start producing blocks.
The API endpoint for downloading this information was recently added to the Beacon API specification and is available on nodes running Nimbus v22.12.0 and later. For other checkpoint sources, consult their documentation with regards to the
It's safe to always specify this option. Nimbus will produce a warning if the specified beacon node doesn't support the required endpoint. Future versions of Nimbus will enable the option by default.
Delay block history backfill
By default, both state and block history will be downloaded from the trusted node.
It is possible to get started more quickly by delaying the backfill of the block history using the
--backfill=false parameter. In this case, the beacon node will first sync to the current head so that it can start performing its duties, then backfill the blocks from the network.
You can also resume the trusted node backfill at any time by simply running the trusted node sync command again.
While backfilling blocks, your node will not be able to answer historical requests or sync requests. This might lead to you being de-scored, and eventually disconnected, by your peers.
Modify sync point
By default, the node will sync up to the latest finalized checkpoint of the node that you're syncing with. While you can choose a different sync point using a state hash or a slot number, this state must fall on an epoch boundary:
Sync from checkpoint files
If you have a state file available, you can start the node using the
# Obtain a state and a block from a Beacon API - these must be in SSZ format: curl -o state.32000.ssz \ -H 'Accept: application/octet-stream' \ http://localhost:5052/eth/v2/debug/beacon/states/32000 # Start the beacon node using the downloaded state as starting point ./run-mainnet-beacon-node.sh \ --finalized-checkpoint-state=state.32000.ssz
Recreate historical state access indices
When performing trusted node sync, the historical state data from the time before the trusted is not available. To recreate the indices and caches necessary for historical state access, run trusted node sync with the
--reindex flag - this can be done on an already-synced node as well, in which case the process will simply resume where it left off:
To recreate a historical index from before the checkpoint, it is necessary to first download an era archive containing the deep block history.