개요

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	갈릴레오 Testnet	네	없음
0g	Mainnet	네	없음
Abstract	Testnet	네	없음
Abstract	Mainnet	네	없음
Aleo	Mainnet	네	없음
Aptos	Testnet	네	없음
Aptos	Mainnet	네	없음
Arc	Testnet	네	없음
Arbitrum	세폴리아	네	없음
Arbitrum	Mainnet	네	없음
Arbitrum	Mainnet	네	없음
Avalanche	Fuji Testnet	네	없음
Avalanche	Mainnet	네	없음
Ault	Mainnet	네	없음
Ault	Testnet	네	없음
B3	세폴리아	아니요	128 blocks of state history
B3	Mainnet	아니요	128 blocks of state history
Base	세폴리아	네	없음
Base	Mainnet	네	없음
Berachain	베폴리아 Testnet	네	없음
Berachain	Mainnet	네	없음
Bitcoin	Testnet	아니요	Pruning disabled
Bitcoin	Mainnet	아니요	Pruning disabled
Bitcoin	Testnet	네	없음
Bitcoin	Mainnet	네	없음
Blast	세폴리아	네	없음
Blast	Mainnet	네	없음
BNB	Testnet	네	없음
BNB	Mainnet	네	없음
Celestia	Mainnet	네	없음
Celestia	모카 Testnet	아니요	pruning-keep-recent = "362880"
Celo	Mainnet	네	없음
Cosmos	Mainnet	네	Data available starting from cosmoshub-4 (block height 5200791); no support for cosmoshub-1/2/3
Cyber	세폴리아	네	없음
Cyber	Mainnet	네	없음
도지	Testnet	네	없음
도지	Mainnet	네	없음
Ethereum	세폴리아	네	없음
Ethereum	Mainnet	네	없음
Ethereum	후디	네	없음
Fantom	Mainnet	네	없음
Flare	Coston2 Testnet	네	없음
Flare	Mainnet	네	없음
Flow	Testnet	아니요	Root of current spork (epoch)
Flow	Mainnet	아니요	Root of current spork (epoch)
Fluent	Mainnet	네	없음
Fluent	Testnet	네	없음
Fraxtal	Mainnet	네	없음
Fuel	세폴리아	네	없음
Fuel	Mainnet	네	없음
GIWA	세폴리아	네	없음
Gravity	Mainnet	네	없음
Gravity	Alpha Mainnet	네	없음
Gnosis	Mainnet	네	없음
Hemi	Testnet	네	없음
Hemi	Mainnet	네	없음
Hedera	Testnet	네	없음
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	네	없음
Immutable	Testnet	네	없음
Immutable	Mainnet	네	없음
Ink	세폴리아	네	없음
Ink	Mainnet	네	없음
JOC	Mainnet	네	없음
Injective	Testnet	아니요	pruning-keep-recent = "1832727" and pruning-interval = "16"
Injective	Mainnet	아니요	pruning-keep-recent = "1832727" and pruning-interval = "16"
Kaia	Kairos Testnet	네	없음
Katana	Mainnet	네	없음
Kaia	Mainnet	네	없음
Linea	Mainnet	네	없음
Lisk	Mainnet	네	없음
Litecoin	Mainnet	네	없음
Litecoin	Testnet	네	없음
Mantle	세폴리아	네	없음
Mantle	Mainnet	네	없음
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" 및 pruning-interval = "16"
Mode	Mainnet	네	없음
Monad	Testnet	네	Over 40,000 recent blocks available
Monad	Mainnet	네	Over 40,000 recent blocks available
Morph	후디	네	없음
Morph	Mainnet	네	없음
NEAR	Testnet	네	없음
NEAR	Mainnet	네	없음
Optimism	세폴리아	네	없음
Optimism	Mainnet	네	없음
Osmosis	Mainnet	네	없음
Peaq	Mainnet	네	없음
Plasma	Testnet	네	없음
Plasma	Mainnet	네	없음
Polkadot	Mainnet	네	없음
Polygon	아모이 Testnet	네	없음
Polygon	Mainnet	네	없음
Robinhood	Mainnet	네	없음
Robinhood	Testnet	네	없음
Sahara	Testnet	네	없음
Scroll	Mainnet	네	없음
Sei	Atlantic Testnet	아니요	3,240,000 블록
Sei	Pacific Mainnet	네	없음
Solana	Devnet	아니요	6578505 slots
Solana	Testnet	아니요	10964176 slots
Solana	Mainnet	네	없음
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	네	없음
Sonic	Mainnet	네	없음
Stacks	Testnet	네	없음
Stacks	Mainnet	네	없음
Starknet	세폴리아	네	없음
Starknet	Mainnet	네	없음
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	네	없음
DATA	Mainnet	네	없음
Sui	Mainnet	Yes (gRPC only)	Full nodes: 14 epochs. Older data automatically routed to archive nodes
Sui	Testnet	아니요	Full nodes: 14 epochs
Tempo	Mainnet	네	없음
Tempo	Testnet	네	없음
TRON	Nile Testnet	네	없음
TRON	Mainnet	네	없음
TON	Mainnet	네	없음
Unichain	세폴리아	네	없음
Unichain	Mainnet	네	없음
Vana	Moksha	네	없음
Vana	Mainnet	네	없음
World Chain	세폴리아	네	없음
World Chain	Mainnet	네	없음
X Layer	Mainnet	네	없음
X Layer	Testnet	네	없음
XRP Ledger	Testnet	네	Full history after recent network reset
XRP Ledger	Mainnet	네	Starts from ledger 32570 (Genesis)
XRPL EVM	Testnet	네	없음
XRPL EVM	Mainnet	네	없음
Zcash	Mainnet	아니요	Pruning disabled
Zcash	Testnet	아니요	Pruning disabled
ZKSync	세폴리아	네	없음
ZKSync	Mainnet	네	없음
Zora	Mainnet	네	없음