Documentation for the --with-deposit-snapshot option (#4440)
This commit is contained in:
parent
2184fd2322
commit
94a87da4a2
|
@ -106,11 +106,11 @@ The following options are available:
|
|||
a validator with the same index (a doppelganger), before sending an attestation
|
||||
itself. This protects against slashing (due to double-voting) but means you will
|
||||
miss two attestations when restarting. [=true].
|
||||
--validator-monitor-auto Automatically monitor locally active validators [=false].
|
||||
--validator-monitor-auto Automatically monitor locally active validators (BETA) [=false].
|
||||
--validator-monitor-pubkey One or more validators to monitor - works best when --subscribe-all-subnets is
|
||||
enabled.
|
||||
enabled (BETA).
|
||||
--validator-monitor-totals Publish metrics to single 'totals' label for better collection performance when
|
||||
monitoring many validators [=false].
|
||||
monitoring many validators (BETA) [=false].
|
||||
--suggested-fee-recipient Suggested fee recipient.
|
||||
--payload-builder Enable external payload builder [=false].
|
||||
--payload-builder-url Payload builder URL.
|
||||
|
|
|
@ -3,11 +3,11 @@
|
|||
!!! note ""
|
||||
This feature is available from `v1.7.0` onwards
|
||||
|
||||
When you [start the beacon node](./quick-start.md) for the first time, it will connect to the beacon chain network and start syncing automatically - a process that can take several days.
|
||||
When you [start the beacon node](./quick-start.md) 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 that exposes the [Beacon API](./rest-api.md) (for example a locally running backup node).
|
||||
To use trusted node sync, you must have access to a node that you trust and that exposes the [Beacon API](./rest-api.md) (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.
|
||||
|
||||
|
@ -80,6 +80,13 @@ The `head` root is also printed in the log output at regular intervals.
|
|||
|
||||
## Advanced
|
||||
|
||||
### Skip syncing the history of deposits
|
||||
|
||||
The recently standardized Beacon API endpoint `/eth/v1/beacon/deposit_snapshot` allows a client to skip downloading the entire history of deposit by downloading a small snapshot of the state of the validator deposit contract. To take advantage of this functionality, make sure you are syncing against a beacon node which supports it (e.g. Nimbus 22.12.0 or later) and specify the the command line option `--with-deposit-snapshot` when executed the `trustedNodeSync` command.
|
||||
|
||||
!!! tip
|
||||
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 the state and the full block history will be downloaded from the trusted node.
|
||||
|
|
Loading…
Reference in New Issue