Difference between revisions of "Ethereum execution clients"
Jump to navigation
Jump to search
| (28 intermediate revisions by 3 users not shown) | |||
| Line 1: | Line 1: | ||
Execution clients are upgraded versions of existing [[Ethereum clients]] like [[Besu]], [[EthereumJS]], [[Erigon]], [[Geth]] and [[Nethermind]]. These clients have had the proof-of-work components removed and now rely upon a Consensus Client to perform the functions of a consensus mechanism. | Execution clients are upgraded versions of existing [[Ethereum clients]] like [[Besu]], [[EthereumJS]], [[Erigon]], [[Geth]] and [[Nethermind]]. These clients have had the proof-of-work components removed and now rely upon a Consensus Client to perform the functions of a consensus mechanism. | ||
| − | |||
Execution client Default Port | Execution client Default Port | ||
| − | * [[ | + | * <code>[[geth]]</code> [[30303]] TCP/UDP ([[Go]]), <code>[[geth version]]</code> |
| − | * [[Besu]] 30303 TCP/UDP | + | * [[Besu]] 30303 TCP/UDP ([[Java]], https://besu.hyperledger.org/en/stable/) |
* [[Nethermind]] 30303 TCP/UDP | * [[Nethermind]] 30303 TCP/UDP | ||
* [[Erigon]] 30303 TCP/UDP | * [[Erigon]] 30303 TCP/UDP | ||
| + | * <code>[[reth]]</code> ([[Rust]]) | ||
| − | + | == Activities == | |
| − | * [[ | + | * Read about why beacon node controls the [[execution node]] and you must have one execution node per beacon node in lighthouse: https://github.com/sigp/lighthouse/blob/stable/book/src/merge-migration.md#connecting-to-an-execution-engine |
| − | + | * [[Ethereum execution layer synchronization nodes]] | |
| − | |||
| − | * [[ | ||
| − | |||
| + | == Related == | ||
| + | * <code>[[cast]]</code> | ||
| − | + | * {{Consensus clients}} | |
| − | * [[ | + | * [[8551]] [[Ethereum]] [[execution API]] |
| + | * [[Paul Hauner]] | ||
| + | * [[Execution node]] | ||
| + | * [[ganache]] | ||
| + | * [[Ethereum node]] | ||
| + | * [[Parity-ethereum]] | ||
== See also == | == See also == | ||
| + | * {{rollup}} | ||
| + | * {{execution clients}} | ||
* {{eth2}} | * {{eth2}} | ||
| − | |||
[[Category:Ethereum]] | [[Category:Ethereum]] | ||
Latest revision as of 11:13, 12 September 2024
Execution clients are upgraded versions of existing Ethereum clients like Besu, EthereumJS, Erigon, Geth and Nethermind. These clients have had the proof-of-work components removed and now rely upon a Consensus Client to perform the functions of a consensus mechanism.
Execution client Default Port
geth30303 TCP/UDP (Go),geth version- Besu 30303 TCP/UDP (Java, https://besu.hyperledger.org/en/stable/)
- Nethermind 30303 TCP/UDP
- Erigon 30303 TCP/UDP
reth(Rust)
Activities[edit]
- Read about why beacon node controls the execution node and you must have one execution node per beacon node in lighthouse: https://github.com/sigp/lighthouse/blob/stable/book/src/merge-migration.md#connecting-to-an-execution-engine
- Ethereum execution layer synchronization nodes
Related[edit]
- Consensus clients,
lighthouse, Teku, Prysm, Nimbus, Caplin and Lodestar - 8551 Ethereum execution API
- Paul Hauner
- Execution node
- ganache
- Ethereum node
- Parity-ethereum
See also[edit]
- L2: Rollup, execution layer, Optimistic Rollups (ORs), Optimistic Rollup Protocol, ZK rollup,
op-node, Rollup node, Replica, Rollup Node Specification, Fuel.network - Execution clients:
geth, besu, reth, Nethermind, Erigon, 30303, 8551, 8547, Prysm, Nimbus, lighthouse - 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:
