Difference between revisions of "Ethereum node"
Jump to navigation
Jump to search
↑ https://geth.ethereum.org/docs/fundamentals/node-architecture
| Line 14: | Line 14: | ||
* [[Ethereum validator]] | * [[Ethereum validator]] | ||
* [[Ethereum sync]]: [[Ethereum consensus layer sync modes]], [[Ethereum execution layer synchronization nodes]] | * [[Ethereum sync]]: [[Ethereum consensus layer sync modes]], [[Ethereum execution layer synchronization nodes]] | ||
| + | * [[Node Discovery Protocol v5]] | ||
== See also == | == See also == | ||
Latest revision as of 13:41, 13 October 2024
An Ethereum node is composed of two clients: an execution client and a consensus client. [1]
- Full node store all the blockchain’s data and participate in block validation
- Light node
- Archive node An archive node is a full node that additionally maintains storage of historical blockchain state
- Node tracker: https://etherscan.io/nodetracker
Related[edit]
- Ethereum archive node
- DAppNode
- Blockscout
- Blockchain explorer
- Ethereum validator
- Ethereum sync: Ethereum consensus layer sync modes, Ethereum execution layer synchronization nodes
- Node Discovery Protocol v5
See also[edit]
- Ethereum nodes: full node, archive node, light nodes, Node Discovery Protocol v5
- 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:
