Difference between revisions of "Ethereum node"
Jump to navigation
Jump to search
↑ https://geth.ethereum.org/docs/fundamentals/node-architecture
| Line 12: | Line 12: | ||
* [[Blockchain explorer]] | * [[Blockchain explorer]] | ||
* [[Ethereum validator]] | * [[Ethereum validator]] | ||
| − | * [[Ethereum consensus layer sync modes]] | + | * [[Ethereum sync]]: [[Ethereum consensus layer sync modes]], [[Ethereum execution layer synchronization nodes]] |
| − | |||
== See also == | == See also == | ||
Revision as of 15:35, 12 July 2023
An Ethereum node is composed of two clients: an execution client and a consensus client. [1]
Related
- Ethereum archive node
- DAppNode
- Blockscout
- Blockchain explorer
- Ethereum validator
- Ethereum sync: Ethereum consensus layer sync modes, Ethereum execution layer synchronization nodes
See also
- Ethereum clients,
geth, Prysm, Nimbus,lighthouse - 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, abidump
Advertising:
