Difference between revisions of "Ethereum consensus layer sync modes"
Jump to navigation
Jump to search
| Line 2: | Line 2: | ||
* [[Optimistic sync]] | * [[Optimistic sync]] | ||
| − | * [[Checkpoint sync]]: <code>[[lighthouse]]: [[--checkpoint-block]], [[--checkpoint-state]], [[--checkpoint-sync-url]]</code> | + | * [[Checkpoint sync]]: <code>[[lighthouse beacon_node --help|lighthouse]]: [[--checkpoint-block]], [[--checkpoint-state]], [[--checkpoint-sync-url]]</code> |
== Related == | == Related == | ||
Revision as of 15:36, 12 July 2023
- Optimistic sync
- Checkpoint sync:
lighthouse: --checkpoint-block, --checkpoint-state, --checkpoint-sync-url
Related
See also
- 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:
