概覽

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.

鏈條	網路	檔案庫	Pruning Policy
0g	Galileo Testnet	是的	無
0g	Mainnet	是的	無
Abstract	Testnet	是的	無
Abstract	Mainnet	是的	無
Aleo	Mainnet	是的	無
Aptos	Testnet	是的	無
Aptos	Mainnet	是的	無
Arc	Testnet	是的	無
Arbitrum	Sepolia	是的	無
Arbitrum	Mainnet	是的	無
Arbitrum	Mainnet	是的	無
Avalanche	富士Testnet	是的	無
Avalanche	Mainnet	是的	無
Ault	Mainnet	是的	無
Ault	Testnet	是的	無
B3	Sepolia	不	128 blocks of state history
B3	Mainnet	不	128 blocks of state history
Base	Sepolia	是的	無
Base	Mainnet	是的	無
Berachain	Bepolia Testnet	是的	無
Berachain	Mainnet	是的	無
Bitcoin	Testnet	不	Pruning disabled
Bitcoin	Mainnet	不	Pruning disabled
Bitcoin Cash	Testnet	是的	無
Bitcoin Cash	Mainnet	是的	無
Blast	Sepolia	是的	無
Blast	Mainnet	是的	無
BNB	Testnet	是的	無
BNB	Mainnet	是的	無
Celestia	Mainnet	是的	無
Celestia	Mocha 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	Sepolia	是的	無
Cyber	Mainnet	是的	無
Doge	Testnet	是的	無
Doge	Mainnet	是的	無
Ethereum	Sepolia	是的	無
Ethereum	Mainnet	是的	無
Ethereum	Hoodi	是的	無
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	Sepolia	是的	無
Fuel	Mainnet	是的	無
GIWA	Sepolia	是的	無
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	Sepolia	是的	無
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	Sepolia	是的	無
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" and pruning-interval = "16"
Mode	Mainnet	是的	無
Monad	Testnet	是的	Over 40,000 recent blocks available
Monad	Mainnet	是的	Over 40,000 recent blocks available
Morph	Hoodi	是的	無
Morph	Mainnet	是的	無
NEAR	Testnet	是的	無
NEAR	Mainnet	是的	無
Optimism	Sepolia	是的	無
Optimism	Mainnet	是的	無
Osmosis	Mainnet	是的	無
Peaq	Mainnet	是的	無
Plasma	Testnet	是的	無
Plasma	Mainnet	是的	無
Polkadot	Mainnet	是的	無
Polygon	Amoy Testnet	是的	無
Polygon	Mainnet	是的	無
Robinhood	Mainnet	是的	無
Robinhood	Testnet	是的	無
Sahara	Testnet	是的	無
Scroll	Mainnet	是的	無
Sei	Atlantic Testnet	不	3240000 blocks
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	Sepolia	是的	無
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	Sepolia	是的	無
Unichain	Mainnet	是的	無
Vana	Moksha	是的	無
Vana	Mainnet	是的	無
World Chain	Sepolia	是的	無
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	Sepolia	是的	無
ZKSync	Mainnet	是的	無
Zora	Mainnet	是的	無