Difference between revisions of "Ethereum full node"
Jump to navigation
Jump to search
↑ https://www.quicknode.com/guides/infrastructure/node-setup/ethereum-full-node-vs-archive-node
| Line 1: | Line 1: | ||
| + | Full Node: Stores and maintains recent block data (i.e., the last 128 blocks) <ref>https://www.quicknode.com/guides/infrastructure/node-setup/ethereum-full-node-vs-archive-node</ref> | ||
Megabytes of memory allocated to internal caching (default = 4096 mainnet [[full node]], 128 [[light mode]]) | Megabytes of memory allocated to internal caching (default = 4096 mainnet [[full node]], 128 [[light mode]]) | ||
Revision as of 18:41, 27 July 2024
Full Node: Stores and maintains recent block data (i.e., the last 128 blocks) [1]
Megabytes of memory allocated to internal caching (default = 4096 mainnet full node, 128 light mode)
Related
See also
- 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:
