Difference between revisions of "Ethereum execution layer synchronization nodes"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
== Related == | == Related == | ||
* <code>[[geth --syncmode]] [ full | light | snap ]</code> | * <code>[[geth --syncmode]] [ full | light | snap ]</code> | ||
| + | * [[Consensus layer sync modes]] | ||
== See also == | == See also == | ||
* {{execution clients}} | * {{execution clients}} | ||
* {{eth2}} | * {{eth2}} | ||
Revision as of 10:55, 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
geth --syncmode [ full | light | snap ]- Consensus layer sync modes
See also
- Execution clients:
geth, besu, reth, Nethermind, Erigon, 30303, 8551, 8547, Prysm, Nimbus, lighthouse - Ethereum 2.0, API, Ethereum tasks, Beacon Chain, Ethereum Staking, validator, Consensus clients, Execution clients, Validation clients, Mainnet, testnets: Prater, Goerli ETH, Inclusion distance, Ethereum attestation, Attestation effectiveness, Attestation Reward Scale, slot, Ethereum upgrades: The Merge, Epoch, Slots, rETH, sETH, stETH, Lido Staked ETH, faucet, Ethereum ports, Subjectivity, Lido Staked ETH, ENR, Sharding,
Ethers.js, Yellow paper, synchronization, ECFSDS
Advertising:
