Ethereum 101 - Part 2 - Understanding Nodes
ETH101 - Understanding Nodes
When we use the word node within this technical documentation, we're referring to an Ethereum client.
An Ethereum client is a software application that implements the Ethereum specification and communicates over the peer-to-peer network with other Ethereum clients. Different Ethereum clients interoperate if they comply with the reference specification and the standardized communications protocols. While these different clients are implemented by different teams and in different programming languages, they all "speak" the same protocol and follow the same rules. As such, they can all be used to operate and interact with the same Ethereum network.
Author: Andreas M. Antonopoulos, "Mastering Ethereum" Section 03 - Clients.
Geth and Parity are arguably the two most common Ethereum clients. For this reason, we'll walk through how to run these clients in more detail through this documentation.
|Trinity||Python||Ethereum Foundation / Piper Merriam|
|Quorum||Go (a fork for go-ethereum)||JPMorgan Chase|
Source (has been modified from original source) * http://ethdocs.org/en/latest/ethereum-clients/choosing-a-client.html#why-are-there-multiple-ethereum-clients * https://github.com/ConsenSys/ethereum-developer-tools-list#ethereum-clients
The client diversity we enjoy as Ethereum network participants is indicative of a healthy ecosystem. There exists a myriad of different clients, many independently developed each with their own feature set, yet they remain interoperable with other Ethereum client implementations. Interoperability within the network is important, and it further boosts the adoption of software such as "remote clients" and "wallets" that improve the general user's experience.
Running a full node / light node / test node
A few new terms here for you to digest. Let's walk through them at a high level:
You're running a full implementation of the Ethereum network on your machine. This is as robust as it gets. It requires a not insignificant commitment of time and effort, as well as related hardware and bandwidth incurred costs, to support the synchronization and maintenance of a full node.
A full node is not required to develop on Ethereum.
A full node will require 80+ GB of disk storage space to store Ethereum's chaindata. Chaindata is the ever expanding chain from the genesis block to the latest best block.
Generally accepted criteria of a full Ethereum node: * full synchronization of the blockchain, from the genesis block to the latest best block with the highest amount of accumulated work * full replay and validation of all transactions, contract deployments, and contract executions, per block, starting at the genesis to the latest best block * has recomputed the state of each consecutive block, from the genesis to latest best block * has all historical blocks on disk, from the genesis to latest best block * maintains the most recent states, while pruning ancient states
The full node theme here is self-evident: all block data from the genesis block to the latest best block with the highest amount of accumulated work is stored on the full node's disk. State data is allowed to be pruned because when a node holds the record of all historical blocks, it can subsequently recompute any historical state.
The Geth and Parity clients both support quicker synchronization modes, "fast sync" and "warp sync" respectively. The way each client actually syncs is a bit more nuanced.
When a Geth node full syncs, it starts at the genesis block and works through each consecutive transaction, on a per block basis, until it reaches the latest best block. This is a time consuming process.
When a Geth node fast syncs, instead of working through each consecutive transaction, the client downloads the transaction receipts in parallel to all the blocks, then pulls the entire most recent state database, and then switches to full sync mode as described above.
When a Parity node no-warp, archive syncs, it starts at the genesis block and works through each consecutive transaction, on a per block basis, until it reaches the latest best block. Along the way, it computes and saves all state data for each block. This is a time consuming and storage intensive process.
When a Parity node no-warp, fast syncs, it starts at the genesis block and works through each consecutive transaction, on a per block basis, until it reaches the latest block. Along the way, it prunes ancient states, maintaining the most recent states on disk. This is a time consuming process.
When a Parity node warp, fast syncs, it skips almost all of the block processing, instead injecting appropriate data directly into the database. Warp synchronization fetches a recent snapshot from the network, restores it, and then continues syncing to the incoming newly validated blocks.
You're running a truncated implementation of the Ethereum network. A light node validates block headers and only other things that need to be verified.
Additional reading: * Ethereum light client protocol specification: https://github.com/ethereum/wiki/wiki/Light-client-protocol
- Kauri original title: Ethereum 101 - Part 2 - Understanding Nodes
- Kauri original link: https://kauri.io/ethereum-101-part-2-understanding-nodes/48d5098292fd4f11b251d1b1814f0bba/a
- Kauri original author: Wil Barnes (@wil)
- Kauri original Publication date: 2019-02-13
- Kauri original tags: ethereum, geth, nodes, primer, parity, client, light-client
- Kauri original hash: QmNuAE2iSCVNvNB2Utj9MEGStVVoqf9Schj7fqQ6HLHp8W
- Kauri original checkpoint: QmSRv329t5c2hpHHf1Yz4XZomqgeBc8LVh9KNJC9z4PVDS