Difference between revisions of "Ethereum consensus clients"
Jump to navigation
Jump to search
| Line 12: | Line 12: | ||
| − | + | ||
== Related == | == Related == | ||
* [[Execution clients]]: <code>[[geth]], [[geth --syncmode]]</code> | * [[Execution clients]]: <code>[[geth]], [[geth --syncmode]]</code> | ||
* [[Consensus layer]]: [[Block Proposal]] | * [[Consensus layer]]: [[Block Proposal]] | ||
| + | * [[Ethereum task]] | ||
* [[Out of sync]] | * [[Out of sync]] | ||
* <code>[[WARN Local chain is post-merge, waiting for beacon client sync switch-over...]]</code> | * <code>[[WARN Local chain is post-merge, waiting for beacon client sync switch-over...]]</code> | ||
Revision as of 08:56, 8 August 2024
Consensus clients also called Beacons client.
Ports:
- Prysm (Go) 13000 TCP, 12000 UDP
- Lighthouse (Rust) 9000 TCP/UDP
- Teku 9000 TCP/UDP
- Nimbus 9000 TCP/UDP
- Lodestar
- Vouch
- Caplin
Related
- Execution clients:
geth, geth --syncmode - Consensus layer: Block Proposal
- Ethereum task
- Out of sync
WARN Local chain is post-merge, waiting for beacon client sync switch-over...- geth:
WARN Post-merge network, but no beacon client seen. Please launch one to follow the chain! - Validator Client (VC)
- Consensus node
- Beacon client
See also
- Consensus clients,
lighthouse, Teku, Prysm, Nimbus, Caplin and Lodestar - Consensus, Proof of Stake (PoS), Consensus clients, Execution clients,
Prysm, Lighthouse, Lodestar, Teku, Nimbus, Consensus Layer (CL), Beacon client - Execution clients:
geth, besu, reth, Nethermind, Erigon, 30303, 8551, 8547, Prysm, Nimbus, lighthouse - Block (Crypto), Block proposal, Block construction, Slots/sec, tps, Block time
Advertising:
