Difference between revisions of "Ethereum consensus layer sync modes"
Jump to navigation
Jump to search
| Line 6: | Line 6: | ||
== Related == | == Related == | ||
* [[Ethereum execution layer synchronization nodes]] | * [[Ethereum execution layer synchronization nodes]] | ||
| − | * [[lighthouse beacon_node]] | + | * [[lighthouse beacon_node]], [[lighthouse beacon node --help]] |
== See also == | == See also == | ||
Latest revision as of 08:30, 10 June 2024
- Optimistic sync
- Checkpoint sync:
lighthouse: --checkpoint-block, --checkpoint-state, --checkpoint-sync-url
Related[edit]
- Ethereum execution layer synchronization nodes
- lighthouse beacon_node, lighthouse beacon node --help
See also[edit]
- Execution clients:
geth, besu, reth, Nethermind, Erigon, 30303, 8551, 8547, Prysm, Nimbus, lighthouse - Ethereum nodes: full node, archive node, light nodes, Node Discovery Protocol v5
- 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:
