Ir diretamente para o conteúdo principal

Supported Chains, Node Types, and Pruning Policies

Atualizado em
Sep 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.

ChainNetworkArquivoPruning Policy
0gGalileo TestnetSimNenhum
0gMainnetSimNenhum
AbstractTestnetSimNenhum
AbstractMainnetSimNenhum
AleoMainnetSimNenhum
AptosTestnetSimNenhum
AptosMainnetSimNenhum
ArcTestnetSimNenhum
ArbitrumSepoliaSimNenhum
ArbitrumMainnetSimNenhum
Arbitrum NovaMainnetSimNenhum
AvalancheFuji TestnetSimNenhum
AvalancheMainnetSimNenhum
AultMainnetSimNenhum
AultTestnetSimNenhum
B3SepoliaNão128 blocks of state history
B3MainnetNão128 blocks of state history
BaseSepoliaSimNenhum
BaseMainnetSimNenhum
BerachainBepolia TestnetSimNenhum
BerachainMainnetSimNenhum
BitcoinTestnetNãoPruning disabled
BitcoinMainnetNãoPruning disabled
Bitcoin CashTestnetSimNenhum
Bitcoin CashMainnetSimNenhum
BlastSepoliaSimNenhum
BlastMainnetSimNenhum
BNBTestnetSimNenhum
BNBMainnetSimNenhum
CelestiaMainnetSimNenhum
CelestiaMocha TestnetNãopruning-keep-recent = "362880"
CeloMainnetSimNenhum
CosmosMainnetSimData available starting from cosmoshub-4 (block height 5200791); no support for cosmoshub-1/2/3
CyberSepoliaSimNenhum
CyberMainnetSimNenhum
DogeTestnetSimNenhum
DogeMainnetSimNenhum
EthereumSepoliaSimNenhum
EthereumMainnetSimNenhum
EthereumHoodiSimNenhum
FantomMainnetSimNenhum
FlareCoston2 TestnetSimNenhum
FlareMainnetSimNenhum
FlowTestnetNãoRoot of current spork (epoch)
FlowMainnetNãoRoot of current spork (epoch)
FluentMainnetSimNenhum
FluentTestnetSimNenhum
FraxtalMainnetSimNenhum
FuelSepoliaSimNenhum
FuelMainnetSimNenhum
GIWASepoliaSimNenhum
GravityMainnetSimNenhum
GravityAlpha MainnetSimNenhum
GnosisMainnetSimNenhum
HemiTestnetSimNenhum
HemiMainnetSimNenhum
HederaTestnetSimNenhum
HyperliquidMainnetSim/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
HederaMainnetSimNenhum
Immutable zkEVMTestnetSimNenhum
Immutable zkEVMMainnetSimNenhum
InkSepoliaSimNenhum
InkMainnetSimNenhum
JOCMainnetSimNenhum
InjectiveTestnetNãopruning-keep-recent = "1832727" and pruning-interval = "16"
InjectiveMainnetNãopruning-keep-recent = "1832727" and pruning-interval = "16"
KaiaKairos TestnetSimNenhum
KatanaMainnetSimNenhum
KaiaMainnetSimNenhum
LineaMainnetSimNenhum
LiskMainnetSimNenhum
LitecoinMainnetSimNenhum
LitecoinTestnetSimNenhum
MantleSepoliaSimNenhum
MantleMainnetSimNenhum
MegaETHMainnetNãoBlock 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
MocaTestnetNãopruning-keep-recent = "550000" and pruning-interval = "16"
ModeMainnetSimNenhum
MonadTestnetSimOver 40,000 recent blocks available
MonadMainnetSimOver 40,000 recent blocks available
MorphHoodiSimNenhum
MorphMainnetSimNenhum
NEARTestnetSimNenhum
NEARMainnetSimNenhum
OptimismSepoliaSimNenhum
OptimismMainnetSimNenhum
OsmosisMainnetSimNenhum
PeaqMainnetSimNenhum
PlasmaTestnetSimNenhum
PlasmaMainnetSimNenhum
PolkadotMainnetSimNenhum
PolygonAmoy TestnetSimNenhum
PolygonMainnetSimNenhum
RobinhoodMainnetSimNenhum
RobinhoodTestnetSimNenhum
SaharaTestnetSimNenhum
ScrollMainnetSimNenhum
SeiAtlantic TestnetNão3240000 blocks
SeiPacific MainnetSimNenhum
SolanaDevnetNão6578505 slots
SolanaTestnetNão10964176 slots
SolanaMainnetSimNenhum
SolanaAlpenglow TestnetNãobest-effort — not guaranteed. History may reset to near-zero after node maintenance/upgrades or the cluster's periodic re-genesis.
SoneiumMainnetSimNenhum
SonicMainnetSimNenhum
StacksTestnetSimNenhum
StacksMainnetSimNenhum
StarknetSepoliaSimNenhum
StarknetMainnetSimNenhum
StellarTestnetNãoHorizon: ~1.43M ledgers (~90 days) & Stellar RPC: 17280 ledgers (~1 days)
StellarMainnetNãoHorizon: ~1.5M ledgers (~90 days) & Stellar RPC: 120,960 ledgers (~7 days)
DATAAeneid TestnetSimNenhum
DATAMainnetSimNenhum
SuiMainnetYes (gRPC only)Full nodes: 14 epochs. Older data automatically routed to archive nodes
SuiTestnetNãoFull nodes: 14 epochs
TempoMainnetSimNenhum
TempoTestnetSimNenhum
TRONNile TestnetSimNenhum
TRONMainnetSimNenhum
TONMainnetSimNenhum
UnichainSepoliaSimNenhum
UnichainMainnetSimNenhum
VanaMokshaSimNenhum
VanaMainnetSimNenhum
World ChainSepoliaSimNenhum
World ChainMainnetSimNenhum
X LayerMainnetSimNenhum
X LayerTestnetSimNenhum
XRP LedgerTestnetSimFull history after recent network reset
XRP LedgerMainnetSimStarts from ledger 32570 (Genesis)
XRPL EVMTestnetSimNenhum
XRPL EVMMainnetSimNenhum
ZcashMainnetNãoPruning disabled
ZcashTestnetNãoPruning disabled
ZKSyncSepoliaSimNenhum
ZKSyncMainnetSimNenhum
ZoraMainnetSimNenhum
Última atualização em