Difference between revisions of "Ethereum execution layer synchronization nodes"
Jump to navigation
Jump to search
| (5 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
* [[Light sync]] | * [[Light sync]] | ||
| + | == Related == | ||
| + | * <code>[[geth --syncmode]] [ full | light | snap ]</code> | ||
| + | * [[Ethereum consensus layer sync modes]] | ||
== See also == | == See also == | ||
| + | * {{geth --syncmode}} | ||
* {{execution clients}} | * {{execution clients}} | ||
| − | + | ||
| + | |||
| + | [[Category:Ethereum]] | ||
Latest revision as of 14:30, 12 July 2023
- Full sync Full sync downloads all blocks (including headers, transactions, and receipts) and generates the state of the blockchain incrementally by executing every block from genesis. Minimizes trust and offers the highest security by verifying every transaction. With an increasing number of transactions, it can take days to weeks to process all transactions.
- Fast sync, synchronization takes only a few hours.
- Light sync
Related[edit]
geth --syncmode [ full | light | snap ]- Ethereum consensus layer sync modes
See also[edit]
geth --syncmode [ snap (default) | --syncmode full | --syncmode light | --syncnode fast (Deprecated) ],op-node --syncmode- Execution clients:
geth, besu, reth, Nethermind, Erigon, 30303, 8551, 8547, Prysm, Nimbus, lighthouse
Advertising:
