Ir diretamente para o conteúdo principal

Supported Chains, Node Types, and Pruning Policies

Atualizado em
Jul 01, 2026

Visão geral

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.

CorrenteRedeArquivoPruning Policy
0gGalileo TestnetSimNenhum
0gRede principalSimNenhum
ResumoRede de testeSimNenhum
ResumoRede principalSimNenhum
AleoRede principalSimNenhum
AptosRede de testeSimNenhum
AptosRede principalSimNenhum
ArcoRede de testeSimNenhum
ArbitrumSepoliaSimNenhum
ArbitrumRede principalSimNenhum
Arbitrum NovaRede principalSimNenhum
AvalancheFuji TestnetSimNenhum
AvalancheRede principalSimNenhum
AultRede principalSimNenhum
AultRede de testeSimNenhum
B3SepoliaNo128 blocks of state history
B3Rede principalNo128 blocks of state history
BaseSepoliaSimNenhum
BaseRede principalSimNenhum
BerachainBepolia TestnetSimNenhum
BerachainRede principalSimNenhum
BitcoinRede de testeNoPruning disabled
BitcoinRede principalNoPruning disabled
Bitcoin CashRede de testeSimNenhum
Bitcoin CashRede principalSimNenhum
ExplosãoSepoliaSimNenhum
ExplosãoRede principalSimNenhum
BNBRede de testeSimNenhum
BNBRede principalSimNenhum
CelestiaRede principalSimNenhum
CelestiaMocha TestnetNopruning-keep-recent = "362880"
CeloRede principalSimNenhum
CosmosRede principalSimData available starting from cosmoshub-4 (block height 5200791); no support for cosmoshub-1/2/3
CibernéticoSepoliaSimNenhum
CibernéticoRede principalSimNenhum
DogeRede principalSimNenhum
EthereumSepoliaSimNenhum
EthereumRede principalSimNenhum
EthereumHoodiSimNenhum
FantomRede principalSimNenhum
Sinal de fogoCoston2 TestnetSimNenhum
Sinal de fogoRede principalSimNenhum
FluxoRede de testeNoRoot of current spork (epoch)
FluxoRede principalNoRoot of current spork (epoch)
FluenteRede principalSimNenhum
FluenteRede de testeSimNenhum
FraxtalRede principalSimNenhum
CombustívelSepoliaSimNenhum
CombustívelRede principalSimNenhum
GravidadeAlpha MainnetSimNenhum
GnoseRede principalSimNenhum
HemiRede de testeSimNenhum
HemiRede principalSimNenhum
HederaRede de testeSimNenhum
HiperlíquidoRede principalSim/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
HederaRede principalSimNenhum
zkEVM imutávelRede de testeSimNenhum
zkEVM imutávelRede principalSimNenhum
TintaSepoliaSimNenhum
TintaRede principalSimNenhum
JOCRede principalSimNenhum
InjetivaRede de testeNopruning-keep-recent = "1832727" and pruning-interval = "16"
InjetivaRede principalNopruning-keep-recent = "1832727" and pruning-interval = "16"
KaiaKairos TestnetSimNenhum
KatanaRede principalSimNenhum
KaiaRede principalSimNenhum
LenteRede principalSimNenhum
LenteRede de testeSimNenhum
LineaRede principalSimNenhum
LiskRede principalSimNenhum
LitecoinRede principalSimNenhum
LitecoinRede de testeSimNenhum
MantoSepoliaSimNenhum
MantoRede principalSimNenhum
MegaETHRede principalNoBlock 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. Saiba mais
MocaRede de testeNopruning-keep-recent = "550000" and pruning-interval = "16"
ModoRede principalSimNenhum
MonadRede de testeSimOver 40,000 recent blocks available
MonadRede principalSimOver 40,000 recent blocks available
MorphHoodiSimNenhum
MorphRede principalSimNenhum
PERTORede de testeSimNenhum
PERTORede principalSimNenhum
OtimismoSepoliaSimNenhum
OtimismoRede principalSimNenhum
OsmoseRede principalSimNenhum
PeaqRede principalSimNenhum
PlasmaRede de testeSimNenhum
PlasmaRede principalSimNenhum
PolkadotRede principalSimNenhum
PolígonoAmoy TestnetSimNenhum
PolígonoRede principalSimNenhum
Polygon zkEVMCardona TestnetSimNenhum
Polygon zkEVMRede principalSimNenhum
RedstoneRede principalSimNenhum
RobinhoodRede principalSimNenhum
RobinhoodRede de testeSimNenhum
SaaraRede de testeSimNenhum
DeslizarRede de testeSimNenhum
DeslizarRede principalSimNenhum
SeiAtlantic TestnetNo3240000 blocks
SeiPacific MainnetSimNenhum
SolanaDevnetNo6578505 slots
SolanaRede de testeNo10964176 slots
SolanaRede principalSimNenhum
SolanaAlpenglow TestnetNobest-effort — not guaranteed. History may reset to near-zero after node maintenance/upgrades or the cluster's periodic re-genesis.
SoneiumRede principalSimNenhum
SonicRede principalSimNenhum
SofonRede principalSimNenhum
PilhasRede de testeNoPruning disabled
PilhasRede principalNoPruning disabled
StarknetSepoliaSimNenhum
StarknetRede principalSimNenhum
EstelarRede de testeNoHorizon: ~1.43M ledgers (~90 days) & Soroban: 17280 ledgers (~1 days)
EstelarRede principalNoHorizon: ~1.5M ledgers (~90 days) & Soroban: 120,960 ledgers (~7 days)
DATAAeneid TestnetSimNenhum
DATARede principalSimNenhum
SuiRede principalYes (gRPC only)Full nodes: 14 epochs. Older data automatically routed to archive nodes
SuiRede de testeNoFull nodes: 14 epochs
TempoRede principalSimNenhum
TempoRede de testeSimNenhum
TRONRede principalSimNenhum
TONRede principalSimNenhum
UnichainSepoliaSimNenhum
UnichainRede principalSimNenhum
VanaMokshaSimNenhum
VanaRede principalSimNenhum
World ChainSepoliaSimNenhum
World ChainRede principalSimNenhum
Camada XRede principalSimNenhum
Camada XRede de testeSimNenhum
XaiRede de testeSimNenhum
XaiRede principalSimNenhum
Registo XRPRede de testeSimFull history after recent network reset
Registo XRPRede principalSimStarts from ledger 32570 (Genesis)
XRPL EVMRede de testeSimNenhum
XRPL EVMRede principalSimNenhum
ZcashRede principalNoPruning disabled
ZcashRede de testeNoPruning disabled
ZKSyncSepoliaSimNenhum
ZKSyncRede principalSimNenhum
ZoraRede principalSimNenhum

Adoramos ❤️ os vossos comentários

❓ 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.

Partilhar este documento