Resumen

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.

Cadena	Red	Archivo	Pruning Policy
0g	Galileo Testnet	Sí	Ninguno
0g	Red principal	Sí	Ninguno
Resumen	Red de pruebas	Sí	Ninguno
Resumen	Red principal	Sí	Ninguno
Aleo	Red principal	Sí	Ninguno
Aptos	Red de pruebas	Sí	Ninguno
Aptos	Red principal	Sí	Ninguno
Arco	Red de pruebas	Sí	Ninguno
Arbitrum	Sepolia	Sí	Ninguno
Arbitrum	Red principal	Sí	Ninguno
Arbitrum Nova	Red principal	Sí	Ninguno
Avalancha	Fuji Testnet	Sí	Ninguno
Avalancha	Red principal	Sí	Ninguno
Ault	Red principal	Sí	Ninguno
Ault	Red de pruebas	Sí	Ninguno
B3	Sepolia	No	128 blocks of state history
B3	Red principal	No	128 blocks of state history
Base	Sepolia	Sí	Ninguno
Base	Red principal	Sí	Ninguno
Berachain	Red de pruebas de Bepolia	Sí	Ninguno
Berachain	Red principal	Sí	Ninguno
Bitcoin	Red de pruebas	No	Poda desactivada
Bitcoin	Red principal	No	Poda desactivada
Bitcoin Cash	Red de pruebas	Sí	Ninguno
Bitcoin Cash	Red principal	Sí	Ninguno
Explosión	Sepolia	Sí	Ninguno
Explosión	Red principal	Sí	Ninguno
BNB	Red de pruebas	Sí	Ninguno
BNB	Red principal	Sí	Ninguno
Celestia	Red principal	Sí	Ninguno
Celestia	Mocha Testnet	No	pruning-keep-recent = "362880"
Celo	Red principal	Sí	Ninguno
Cosmos	Red principal	Sí	Data available starting from cosmoshub-4 (block height 5200791); no support for cosmoshub-1/2/3
Cibernética	Sepolia	Sí	Ninguno
Cibernética	Red principal	Sí	Ninguno
Doge	Red principal	Sí	Ninguno
Ethereum	Sepolia	Sí	Ninguno
Ethereum	Red principal	Sí	Ninguno
Ethereum	Hoodi	Sí	Ninguno
Fantom	Red principal	Sí	Ninguno
Bengala	Coston2 Testnet	Sí	Ninguno
Bengala	Red principal	Sí	Ninguno
Flujo	Red de pruebas	No	Root of current spork (epoch)
Flujo	Red principal	No	Root of current spork (epoch)
Con fluidez	Red principal	Sí	Ninguno
Con fluidez	Red de pruebas	Sí	Ninguno
Fraxtal	Red principal	Sí	Ninguno
Combustible	Sepolia	Sí	Ninguno
Combustible	Red principal	Sí	Ninguno
Gravedad	Alpha Mainnet	Sí	Ninguno
Gnosis	Red principal	Sí	Ninguno
Hemi	Red de pruebas	Sí	Ninguno
Hemi	Red principal	Sí	Ninguno
Hedera	Red de pruebas	Sí	Ninguno
Hiperlíquido	Red principal	Sí	/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	Red principal	Sí	Ninguno
zkEVM inmutable	Red de pruebas	Sí	Ninguno
zkEVM inmutable	Red principal	Sí	Ninguno
Tinta	Sepolia	Sí	Ninguno
Tinta	Red principal	Sí	Ninguno
JOC	Red principal	Sí	Ninguno
Inyectiva	Red de pruebas	No	pruning-keep-recent = "1832727" and pruning-interval = "16"
Inyectiva	Red principal	No	pruning-keep-recent = "1832727" and pruning-interval = "16"
Kaia	Kairos Testnet	Sí	Ninguno
Katana	Red principal	Sí	Ninguno
Kaia	Red principal	Sí	Ninguno
Lente	Red principal	Sí	Ninguno
Lente	Red de pruebas	Sí	Ninguno
Linea	Red principal	Sí	Ninguno
Lisk	Red principal	Sí	Ninguno
Litecoin	Red principal	Sí	Ninguno
Litecoin	Red de pruebas	Sí	Ninguno
Manto	Sepolia	Sí	Ninguno
Manto	Red principal	Sí	Ninguno
MegaETH	Red principal	No	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. Más información
Moca	Red de pruebas	No	pruning-keep-recent = "550000" and pruning-interval = "16"
Modo	Red principal	Sí	Ninguno
Mónada	Red de pruebas	Sí	Más de 40 000 bloques recientes disponibles
Mónada	Red principal	Sí	Más de 40 000 bloques recientes disponibles
Morph	Hoodi	Sí	Ninguno
Morph	Red principal	Sí	Ninguno
CERCANO	Red de pruebas	Sí	Ninguno
CERCANO	Red principal	Sí	Ninguno
Optimismo	Sepolia	Sí	Ninguno
Optimismo	Red principal	Sí	Ninguno
Ósmosis	Red principal	Sí	Ninguno
Peaq	Red principal	Sí	Ninguno
Plasma	Red de pruebas	Sí	Ninguno
Plasma	Red principal	Sí	Ninguno
Polkadot	Red principal	Sí	Ninguno
Polígono	Amoy Testnet	Sí	Ninguno
Polígono	Red principal	Sí	Ninguno
Polygon zkEVM	Cardona Testnet	Sí	Ninguno
Polygon zkEVM	Red principal	Sí	Ninguno
Redstone	Red principal	Sí	Ninguno
Robinhood	Red principal	Sí	Ninguno
Robinhood	Red de pruebas	Sí	Ninguno
Sáhara	Red de pruebas	Sí	Ninguno
Desplazarse	Red de pruebas	Sí	Ninguno
Desplazarse	Red principal	Sí	Ninguno
Sei	Atlantic Testnet	No	3240000 blocks
Sei	Pacific Mainnet	Sí	Ninguno
Solana	Devnet	No	6578505 slots
Solana	Red de pruebas	No	10964176 slots
Solana	Red principal	Sí	Ninguno
Solana	Alpenglow Testnet	No	best-effort — not guaranteed. History may reset to near-zero after node maintenance/upgrades or the cluster's periodic re-genesis.
Soneium	Red principal	Sí	Ninguno
Sonic	Red principal	Sí	Ninguno
Sofón	Red principal	Sí	Ninguno
Pilas	Red de pruebas	No	Poda desactivada
Pilas	Red principal	No	Poda desactivada
Starknet	Sepolia	Sí	Ninguno
Starknet	Red principal	Sí	Ninguno
Estelar	Red de pruebas	No	Horizon: ~1.43M ledgers (~90 days) & Soroban: 17280 ledgers (~1 days)
Estelar	Red principal	No	Horizon: ~1.5M ledgers (~90 days) & Soroban: 120,960 ledgers (~7 days)
DATA	Aeneid Testnet	Sí	Ninguno
DATA	Red principal	Sí	Ninguno
Sui	Red principal	Yes (gRPC only)	Full nodes: 14 epochs. Older data automatically routed to archive nodes
Sui	Red de pruebas	No	Full nodes: 14 epochs
Tempo	Red principal	Sí	Ninguno
Tempo	Red de pruebas	Sí	Ninguno
TRON	Red principal	Sí	Ninguno
TON	Red principal	Sí	Ninguno
Unichain	Sepolia	Sí	Ninguno
Unichain	Red principal	Sí	Ninguno
Vana	Moksha	Sí	Ninguno
Vana	Red principal	Sí	Ninguno
World Chain	Sepolia	Sí	Ninguno
World Chain	Red principal	Sí	Ninguno
Capa X	Red principal	Sí	Ninguno
Capa X	Red de pruebas	Sí	Ninguno
Xai	Red de pruebas	Sí	Ninguno
Xai	Red principal	Sí	Ninguno
XRP Ledger	Red de pruebas	Sí	Full history after recent network reset
XRP Ledger	Red principal	Sí	Starts from ledger 32570 (Genesis)
XRPL EVM	Red de pruebas	Sí	Ninguno
XRPL EVM	Red principal	Sí	Ninguno
Zcash	Red principal	No	Poda desactivada
Zcash	Red de pruebas	No	Poda desactivada
ZKSync	Sepolia	Sí	Ninguno
ZKSync	Red principal	Sí	Ninguno
Zora	Red principal	Sí	Ninguno

Nos encantan los comentarios ❤️

❓ We want to hear from you! Please take a few minutes to fill out our feedback form and share your thoughts about this page. This helps us further improve the documentation.