Difference between revisions of "Ethereum consensus clients"
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| + | [[Consensus client]]s also called [[Beacon]]s client. | ||
| − | + | ||
| + | Ports: | ||
* [[Prysm]] 13000 TCP, 12000 UDP | * [[Prysm]] 13000 TCP, 12000 UDP | ||
* [[Lighthouse]] 9000 TCP/UDP | * [[Lighthouse]] 9000 TCP/UDP | ||
Revision as of 15:23, 21 August 2022
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
Related
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:
