Ethereum consensus clients
Revision as of 07:26, 3 June 2024 by Welcome (talk | contribs) (Welcome moved page Consensus clients to Ethereum consensus clients over redirect)
Consensus clients also called Beacons client.
Ports:
- Prysm 13000 TCP, 12000 UDP
- Lighthouse 9000 TCP/UDP
- Teku 9000 TCP/UDP
- Nimbus 9000 TCP/UDP
- Lodestar
- Vouch
Related
- Execution clients:
geth - Consensus layer
- 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 - Ethereum
ETH, Ethereum 2.0, smart contract, EVM, ERC-20, DAG, Ethereum Classic, Polygon, BAT, Solidity, Gas, Nonce, Chainlink, Vitalik Buterin, Gavin Wood, Ethereum Foundation, EIPs, ERC, Lighthouse ethereum client, Prysm, Ethereum clients, Ethereum Gossip Protocol, sETH, ETH1 address, Ganache, Aave, Harmony, Account abstraction, Ethereum node, gwei, NatSpec, Precompiles, Dencun, Eth-keyfile, Ethereum API, Blobs, Ethereum SRB, Ethereum scaling, Ethereum JWT, Ethstats
Advertising:
