website: remove mention of EL light sync (#31197)

This commit is contained in:
Sina M 2025-02-18 06:46:52 +01:00 committed by GitHub
parent e99487c152
commit 6e30f1bb51
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 1 additions and 3 deletions

View File

@ -44,9 +44,7 @@ It is also possible to create a partial/recent archive node where the node was s
## Light nodes {#light-nodes}
A light node syncs very quickly and stores the bare minimum of blockchain data. Light nodes only process block headers, not entire blocks. This greatly reduces the computation time, storage and bandwidth required relative to a full node. This means light nodes are suitable for resource-constrained devices and can catch up to the head of the chain much faster when they are new or have been offline for a while. The trade-off is that light nodes rely heavily on data served by altruistic full nodes. A light client can be used to query data from Ethereum and submit transactions, acting as a locally-hosted Ethereum wallet. However, because they don't keep local copies of the Ethereum state, light nodes can't validate blocks in the same way as full nodes - they receive a proof from the full node and verify it against their local header chain. To start a node in light mode, pass `--syncmode light`. Be aware that full nodes serving light data are relatively scarce so light nodes can struggle to find peers. **Light nodes are not currently working on proof-of-stake Ethereum**.
Read more about light nodes on our [LES page](/docs/fundamentals/les).
Geth offers no EL light client at the moment as a sync mode. To have a lighter set-up it is recommended to run a [beacon light sync together](/docs/fundamentals/blsync) with snap sync mode.
## Consensus layer syncing {#consensus-layer-syncing}