概要

Blockchain networks rely on nodes to maintain the integrity and functionality of the network. Nodes perform essential tasks such as validating transactions, storing blockchain data, and facilitating data access for applications and users. Quicknode provides access to nodes on over 70 blockchains, including full and archive nodes, to accommodate various use cases and operational requirements.

This document explains the differences between full and archive nodes, their data storage, and pruning policies. It lists supported chains, networks, archive mode availability, and pruning policies for each.

What is a Full Node?

A Full Node maintains the current state of the blockchain and validates all transactions and blocks according to the network's consensus rules. Full nodes store enough data to process new transactions and build the blockchain's latest state.

Key Features of Full Nodes:

• Current State Data: Full nodes maintain the most up-to-date blockchain state.
• Transaction Validation: They verify transactions and blocks before adding them to the chain.
• Storage Requirements: Full nodes are more storage-efficient compared to archive nodes, as they do not store all historical states. However, you can still verify historical states using block data.
• Applications: Ideal for most blockchain interactions, such as querying balances, interacting with smart contracts, and sending transactions.

What is an Archive Node?

An Archive Node stores the complete history of the blockchain, including all historical states of accounts and contracts. This allows archive nodes to answer queries related to past states of the blockchain, which full nodes cannot.

Key Features of Archive Nodes:

• Complete Data: Archive nodes retain the entire blockchain history, from the genesis block to the current state.
• Advanced Querying: They support queries for any historical block, account, or contract state.
• Storage Requirements: Due to the large volume of data stored, archive nodes require significantly more storage and computational resources.
• Applications: Essential for analytics, blockchain explorers, debugging tools, and compliance requirements.

What is a Pruning Policy?

A Pruning Policy defines how a node manages and retains blockchain data. Pruning is the process of removing older blockchain data to save storage space while retaining the data necessary for current operations.

Key Features of Pruning Policies:

• Reduced Storage: Pruned nodes discard historical data that is no longer needed for validation or current operations.
• Efficiency: Pruning improves storage efficiency and reduces hardware requirements.
• Limitations: Pruned nodes cannot provide access to historical states, making them unsuitable for applications requiring full blockchain history.
• Variations Across Chains: The implementation of pruning policies varies across blockchain networks and can depend on the chain's design and specific use cases.

Supported Chains & Networks

Below is a table that summarizes the availability of archive nodes and pruning policies across Quicknode's supported chains and networks.

Chain	ネットワーク	アーカイブ	Pruning Policy
0g	Galileo Testnet	はい	None
0g	Mainnet	はい	None
Abstract	Testnet	はい	None
Abstract	Mainnet	はい	None
Aleo	Mainnet	はい	None
Aptos	Testnet	はい	None
Aptos	Mainnet	はい	None
Arc	Testnet	はい	None
Arbitrum	Sepolia	はい	None
Arbitrum	Mainnet	はい	None
Arbitrum Nova	Mainnet	はい	None
Avalanche	Fuji Testnet	はい	None
Avalanche	Mainnet	はい	None
Ault	Mainnet	はい	None
Ault	Testnet	はい	None
B3	Sepolia	いいえ	128 blocks of state history
B3	Mainnet	いいえ	128 blocks of state history
Base	Sepolia	はい	None
Base	Mainnet	はい	None
Berachain	Bepolia Testnet	はい	None
Berachain	Mainnet	はい	None
Bitcoin	Testnet	いいえ	Pruning disabled
Bitcoin	Mainnet	いいえ	Pruning disabled
Bitcoin Cash	Testnet	はい	None
Bitcoin Cash	Mainnet	はい	None
Blast	Sepolia	はい	None
Blast	Mainnet	はい	None
BNB	Testnet	はい	None
BNB	Mainnet	はい	None
Celestia	Mainnet	はい	None
Celestia	Mocha Testnet	いいえ	pruning-keep-recent = "362880"
Celo	Mainnet	はい	None
Cosmos	Mainnet	はい	Data available starting from cosmoshub-4 (block height 5200791); no support for cosmoshub-1/2/3
Cyber	Sepolia	はい	None
Cyber	Mainnet	はい	None
Doge	Testnet	はい	None
Doge	Mainnet	はい	None
Ethereum	Sepolia	はい	None
Ethereum	Mainnet	はい	None
Ethereum	Hoodi	はい	None
Fantom	Mainnet	はい	None
Flare	Coston2 Testnet	はい	None
Flare	Mainnet	はい	None
Flow	Testnet	いいえ	Root of current spork (epoch)
Flow	Mainnet	いいえ	Root of current spork (epoch)
Fluent	Mainnet	はい	None
Fluent	Testnet	はい	None
Fraxtal	Mainnet	はい	None
Fuel	Sepolia	はい	None
Fuel	Mainnet	はい	None
GIWA	Sepolia	はい	None
Gravity	Mainnet	はい	None
Gravity	Alpha Mainnet	はい	None
Gnosis	Mainnet	はい	None
Hemi	Testnet	はい	None
Hemi	Mainnet	はい	None
Hedera	Testnet	はい	None
Hyperliquid	Mainnet	はい	/evm → Recent data only; older blocks are periodically pruned (~12 hours retention) /nanoreth → Full historical archive with tracing support /hypercore → HyperCore exchange layer for historical trading data, order book updates, and exchange events Learn more about Hyperliquid endpoints here
Hedera	Mainnet	はい	None
Immutable zkEVM	Testnet	はい	None
Immutable zkEVM	Mainnet	はい	None
Ink	Sepolia	はい	None
Ink	Mainnet	はい	None
JOC	Mainnet	はい	None
Injective	Testnet	いいえ	pruning-keep-recent = "1832727" and pruning-interval = "16"
Injective	Mainnet	いいえ	pruning-keep-recent = "1832727" and pruning-interval = "16"
Kaia	Kairos Testnet	はい	None
Katana	Mainnet	はい	None
Kaia	Mainnet	はい	None
Linea	Mainnet	はい	None
Lisk	Mainnet	はい	None
Litecoin	Mainnet	はい	None
Litecoin	Testnet	はい	None
Mantle	Sepolia	はい	None
Mantle	Mainnet	はい	None
MegaETH	Mainnet	いいえ	Block and transaction data retained indefinitely. Receipt data retained ~15 days in database but also persisted in static files. Historical state queries (eth_call, eth_getBalance at past blocks) limited to ~15-day / 1,296,064-block pruning window. 詳細はこちら
Moca	Testnet	いいえ	pruning-keep-recent = "550000" and pruning-interval = "16"
Mode	Mainnet	はい	None
Monad	Testnet	はい	Over 40,000 recent blocks available
Monad	Mainnet	はい	Over 40,000 recent blocks available
Morph	Hoodi	はい	None
Morph	Mainnet	はい	None
NEAR	Testnet	はい	None
NEAR	Mainnet	はい	None
Optimism	Sepolia	はい	None
Optimism	Mainnet	はい	None
Osmosis	Mainnet	はい	None
Peaq	Mainnet	はい	None
Plasma	Testnet	はい	None
Plasma	Mainnet	はい	None
Polkadot	Mainnet	はい	None
Polygon	Amoy Testnet	はい	None
Polygon	Mainnet	はい	None
Robinhood	Mainnet	はい	None
Robinhood	Testnet	はい	None
Sahara	Testnet	はい	None
Scroll	Mainnet	はい	None
Sei	Atlantic Testnet	いいえ	3240000 blocks
Sei	Pacific Mainnet	はい	None
Solana	Devnet	いいえ	6578505 slots
Solana	Testnet	いいえ	10964176 slots
Solana	Mainnet	はい	None
Solana	Alpenglow Testnet	いいえ	best-effort — not guaranteed. History may reset to near-zero after node maintenance/upgrades or the cluster's periodic re-genesis.
Soneium	Mainnet	はい	None
Sonic	Mainnet	はい	None
Stacks	Testnet	はい	None
Stacks	Mainnet	はい	None
Starknet	Sepolia	はい	None
Starknet	Mainnet	はい	None
Stellar	Testnet	いいえ	Horizon: ~1.43M ledgers (~90 days) & Stellar RPC: 17280 ledgers (~1 days)
Stellar	Mainnet	いいえ	Horizon: ~1.5M ledgers (~90 days) & Stellar RPC: 120,960 ledgers (~7 days)
DATA	Aeneid Testnet	はい	None
DATA	Mainnet	はい	None
Sui	Mainnet	Yes (gRPC only)	Full nodes: 14 epochs. Older data automatically routed to archive nodes
Sui	Testnet	いいえ	Full nodes: 14 epochs
Tempo	Mainnet	はい	None
Tempo	Testnet	はい	None
TRON	Nile Testnet	はい	None
TRON	Mainnet	はい	None
TON	Mainnet	はい	None
Unichain	Sepolia	はい	None
Unichain	Mainnet	はい	None
Vana	Moksha	はい	None
Vana	Mainnet	はい	None
World Chain	Sepolia	はい	None
World Chain	Mainnet	はい	None
X Layer	Mainnet	はい	None
X Layer	Testnet	はい	None
XRP Ledger	Testnet	はい	Full history after recent network reset
XRP Ledger	Mainnet	はい	Starts from ledger 32570 (Genesis)
XRPL EVM	Testnet	はい	None
XRPL EVM	Mainnet	はい	None
Zcash	Mainnet	いいえ	Pruning disabled
Zcash	Testnet	いいえ	Pruning disabled
ZKSync	Sepolia	はい	None
ZKSync	Mainnet	はい	None
Zora	Mainnet	はい	None