status-im/nimbus-eth2
2
0
Fork 0
mirror of https://github.com/status-im/nimbus-eth2.git synced 2025-02-10 13:36:40 +00:00
Code Issues Projects Releases Wiki Activity
nimbus-eth2/docs/the_nimbus_book/src/light-client-data.md
Jacek Sieka 1b90f65f7b
doc updates (#4314) 
* optimise index / landing page real estate, add feature list
* fee recipient in quickstart
* recommend http over websockets  (fewer command line options needed)
* simplify PBS, fee recipient docs
* add VC role / sentry node docs (#4140)
* Update docs/the_nimbus_book/src/rest-api.md

Co-authored-by: tersec <tersec@users.noreply.github.com>
2022-11-13 07:59:55 +01:00

1.7 KiB
Raw Blame History

Light client data

Nimbus is configured by default to serve data that allows light clients to stay in sync with the Ethereum network. Light client data is imported incrementally and does not affect validator performance. Information about the light client sync protocol can be found in the Ethereum consensus specs.

!!! note Nimbus also implements a standalone light client that may be used to sync an execution layer (EL) client.

Configuration

The following configuration options adjust the import and serving of light client data:

Option Description
--light-client-data-serve
  • false: Disable light client data serving
  • true (default): Provide imported light client data to others
--light-client-data-import-mode
  • none: Do not import new light client data
  • only-new (default): Incrementally import new light client data
  • full: Import historic light client data (slow startup)
  • on-demand: Like full, but import on demand instead of on start
--light-client-data-max-periods
  • Controls the maximum number of sync committee periods to retain light client data
  • When unspecified (default), light client data is never pruned

!!! warning Setting --light-client-data-import-mode to full or on-demand imports historic light client data which is computationally expensive. While importing historic light client data, validator duties may be missed.