ETH-ECC nodes connect to the WorldLand network and synchronize to keep up with the latest state of the WorldLand network. There are two types of node methods and two types of synchronization methods that use different mechanisms to synchronize up to the head of the chain.
The basic node method is the Full Node method. The main feature of full nodes is to save storage space by maintaining the state of 128 blocks at the latest block height and removing past state data. It removes past state data but keeps checkpoints from which state data can be recreated. If you need historical data, you can recreate it with checkpoints. The full node approach effectively saves storage space but is inefficient when fast querying of historical data is required.
The archive node does not remove all historical data. It retains it by itself. All data is directly accessible from the node itself, so there is no need to regenerate data with checkpoints. Since the node owns all blockchain data, it is a true blockchain node. However, since Archive node takes up a lot of disk space, it is not suitable for all users.
The key differences between an Archive Node and a Full Node:
| Full Node | Archive Node | |
|---|---|---|
Full Node:
CPU with 2+ cores
4GB RAM
500GB free storage space to sync the Mainnet
8 MBit/sec download Internet service
Archive Node:
Fast CPU with 4+ cores
8GB+ RAM
High-performance SSD with at least 1TB of free space
25+ MBit/sec download Internet service
Snap sync starts with a relatively recent block and syncs to the head of the chain, keeping only the most recent 128 block states in memory. Between the initial sync block and the most recent 128 blocks, nodes save intermittent snapshots that can be used to rebuild intermediate states "on the fly". The difference between a snap sync node and a full block-by-block sync node is that a snap sync node starts at an initial checkpoint that is more recent than the genesis block. Snap sync is much faster than Genesis' full block-by-block sync. To start the node with snap sync, pass on startup.
Full block-by-block synchronization starts with the genesis block and executes all blocks to create the current state. Full sync re-executes transactions across the entire historical sequence of blocks to independently verify block origins and all state transitions. Only the most recent 128 block states are stored across all nodes. Stale block states are periodically pruned and marked as a series of checkpoints from which old states can be recreated on demand. 128 blocks is a record of about 21.3 minutes with a block time of 10 seconds.
| Snap Sync | Full Sync | |
|---|---|---|
Data Retention
Retains only the latest block data
Retains all block data
Data Storage Size
Relatively smaller
Very large
Synchronization Time
Comparatively shorter
Lengthy
Purpose
Transaction broadcasting and network security maintenance
Block exploration and historical data verification
Higher Storage Costs
No
Yes
Data Download Method
Download snapshot file and sync
Sequentially download all blocks for synchronization
Download Time
Faster
Takes longer
Purpose
Useful for quickly syncing new nodes
Required to verify full network history.
Network Load
Low
High
