Ga naar de hoofdinhoud

Supported Chains, Node Types, and Pruning Policies

Bijgewerkt op
1 juli 2026

Overzicht​

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.

KettingNetwerkArchiefPruning Policy
0gGalileo-testnetJaGeen
0gMainnetJaGeen
SamenvattingTestnetJaGeen
SamenvattingMainnetJaGeen
AleoMainnetJaGeen
AptosTestnetJaGeen
AptosMainnetJaGeen
BoogTestnetJaGeen
ArbitrumSepoliaJaGeen
ArbitrumMainnetJaGeen
Arbitrum NovaMainnetJaGeen
LawineFuji TestnetJaGeen
LawineMainnetJaGeen
AultMainnetJaGeen
AultTestnetJaGeen
B3SepoliaNee128 blokken staatsgeschiedenis
B3MainnetNee128 blokken staatsgeschiedenis
BasisSepoliaJaGeen
BasisMainnetJaGeen
BerachainBepolia TestnetJaGeen
BerachainMainnetJaGeen
BitcoinTestnetNeePruning disabled
BitcoinMainnetNeePruning disabled
Bitcoin CashTestnetJaGeen
Bitcoin CashMainnetJaGeen
ExplosieSepoliaJaGeen
ExplosieMainnetJaGeen
BNBTestnetJaGeen
BNBMainnetJaGeen
CelestiaMainnetJaGeen
CelestiaMocha TestnetNeepruning-keep-recent = "362880"
CeloMainnetJaGeen
CosmosMainnetJaData available starting from cosmoshub-4 (block height 5200791); no support for cosmoshub-1/2/3
CyberSepoliaJaGeen
CyberMainnetJaGeen
DogeMainnetJaGeen
EthereumSepoliaJaGeen
EthereumMainnetJaGeen
EthereumHoodiJaGeen
FantomMainnetJaGeen
FlareCoston2 TestnetJaGeen
FlareMainnetJaGeen
StroomTestnetNeeRoot of current spork (epoch)
StroomMainnetNeeRoot of current spork (epoch)
VloeiendMainnetJaGeen
VloeiendTestnetJaGeen
FraxtalMainnetJaGeen
BrandstofSepoliaJaGeen
BrandstofMainnetJaGeen
ZwaartekrachtAlpha MainnetJaGeen
GnosisMainnetJaGeen
HemiTestnetJaGeen
HemiMainnetJaGeen
HederaTestnetJaGeen
HypervloeibaarMainnetJa/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
HederaMainnetJaGeen
Onveranderlijke zkEVMTestnetJaGeen
Onveranderlijke zkEVMMainnetJaGeen
InktSepoliaJaGeen
InktMainnetJaGeen
JOCMainnetJaGeen
InjectiefTestnetNeepruning-keep-recent = "1832727" and pruning-interval = "16"
InjectiefMainnetNeepruning-keep-recent = "1832727" and pruning-interval = "16"
KaiaKairos TestnetJaGeen
KatanaMainnetJaGeen
KaiaMainnetJaGeen
LensMainnetJaGeen
LensTestnetJaGeen
LineaMainnetJaGeen
LiskMainnetJaGeen
LitecoinMainnetJaGeen
LitecoinTestnetJaGeen
MantelSepoliaJaGeen
MantelMainnetJaGeen
MegaETHMainnetNeeBlock 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. Meer informatie
MocaTestnetNeepruning-keep-recent = "550000" and pruning-interval = "16"
ModusMainnetJaGeen
MonadeTestnetJaOver 40,000 recent blocks available
MonadeMainnetJaOver 40,000 recent blocks available
MorphHoodiJaGeen
MorphMainnetJaGeen
NEARTestnetJaGeen
NEARMainnetJaGeen
OptimismeSepoliaJaGeen
OptimismeMainnetJaGeen
OsmoseMainnetJaGeen
PeaqMainnetJaGeen
PlasmaTestnetJaGeen
PlasmaMainnetJaGeen
PolkadotMainnetJaGeen
PolygonAmoy TestnetJaGeen
PolygonMainnetJaGeen
Polygon zkEVMCardona-testnetJaGeen
Polygon zkEVMMainnetJaGeen
RedstoneMainnetJaGeen
RobinhoodMainnetJaGeen
RobinhoodTestnetJaGeen
SaharaTestnetJaGeen
ScrollenTestnetJaGeen
ScrollenMainnetJaGeen
SeiAtlantic TestnetNee3240000 blocks
SeiPacific MainnetJaGeen
SolanaDevnetNee6578505 slots
SolanaTestnetNee10964176 slots
SolanaMainnetJaGeen
SolanaAlpenglow TestnetNeebest-effort — not guaranteed. History may reset to near-zero after node maintenance/upgrades or the cluster's periodic re-genesis.
SoneiumMainnetJaGeen
SonicMainnetJaGeen
SophonMainnetJaGeen
StapelsTestnetNeePruning disabled
StapelsMainnetNeePruning disabled
StarknetSepoliaJaGeen
StarknetMainnetJaGeen
StellarTestnetNeeHorizon: ~1.43M ledgers (~90 days) & Soroban: 17280 ledgers (~1 days)
StellarMainnetNeeHorizon: ~1.5M ledgers (~90 days) & Soroban: 120,960 ledgers (~7 days)
GEGEVENSAeneid TestnetJaGeen
GEGEVENSMainnetJaGeen
SuiMainnetYes (gRPC only)Full nodes: 14 epochs. Older data automatically routed to archive nodes
SuiTestnetNeeFull nodes: 14 epochs
TempoMainnetJaGeen
TempoTestnetJaGeen
TRONMainnetJaGeen
TONMainnetJaGeen
UnichainSepoliaJaGeen
UnichainMainnetJaGeen
VanaMokshaJaGeen
VanaMainnetJaGeen
World ChainSepoliaJaGeen
World ChainMainnetJaGeen
Laag XMainnetJaGeen
Laag XTestnetJaGeen
XaiTestnetJaGeen
XaiMainnetJaGeen
XRP-ledgerTestnetJaFull history after recent network reset
XRP-ledgerMainnetJaStarts from ledger 32570 (Genesis)
XRPL EVMTestnetJaGeen
XRPL EVMMainnetJaGeen
ZcashMainnetNeePruning disabled
ZcashTestnetNeePruning disabled
ZKSyncSepoliaJaGeen
ZKSyncMainnetJaGeen
ZoraMainnetJaGeen

We ❤️ feedback​

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

Laatst bijgewerkt op
Deel dit document