Difference between revisions of "Ethereum node"
Jump to navigation
Jump to search
↑ https://geth.ethereum.org/docs/fundamentals/node-architecture
| Line 1: | Line 1: | ||
| − | An Ethereum node is composed of two clients: an execution client and a consensus client. <ref>https://geth.ethereum.org/docs/fundamentals/node-architecture</ref> | + | An Ethereum node is composed of two clients: an [[execution client]] and a [[consensus client]]. <ref>https://geth.ethereum.org/docs/fundamentals/node-architecture</ref> |
* [[Full node]] | * [[Full node]] | ||
Revision as of 14:55, 12 July 2023
An Ethereum node is composed of two clients: an execution client and a consensus client. [1]
Related
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:
