跳转至主要内容

Supported Chains, Node Types, and Pruning Policies

更新于
Sep 01, 2026

概述

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伽利略Testnet
0gMainnet
AbstractTestnet
AbstractMainnet
AleoMainnet
AptosTestnet
AptosMainnet
ArcTestnet
Arbitrum塞波利亚
ArbitrumMainnet
ArbitrumMainnet
AvalancheFuji Testnet
AvalancheMainnet
AultMainnet
AultTestnet
B3塞波利亚128 blocks of state history
B3Mainnet128 blocks of state history
Base塞波利亚
BaseMainnet
BerachainBepolia Testnet
BerachainMainnet
BitcoinTestnetPruning disabled
BitcoinMainnetPruning disabled
BitcoinTestnet
BitcoinMainnet
Blast塞波利亚
BlastMainnet
BNBTestnet
BNBMainnet
CelestiaMainnet
CelestiaMocha Testnetpruning-keep-recent = "362880"
CeloMainnet
CosmosMainnetData available starting from cosmoshub-4 (block height 5200791); no support for cosmoshub-1/2/3
Cyber塞波利亚
CyberMainnet
DogeTestnet
DogeMainnet
Ethereum塞波利亚
EthereumMainnet
EthereumHoodi
FantomMainnet
FlareCoston2 Testnet
FlareMainnet
FlowTestnetRoot of current spork (epoch)
FlowMainnetRoot of current spork (epoch)
FluentMainnet
FluentTestnet
FraxtalMainnet
Fuel塞波利亚
FuelMainnet
GIWA塞波利亚
GravityMainnet
GravityAlpha Mainnet
GnosisMainnet
HemiTestnet
HemiMainnet
HederaTestnet
HyperliquidMainnet/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
HederaMainnet
ImmutableTestnet
ImmutableMainnet
Ink塞波利亚
InkMainnet
JOCMainnet
InjectiveTestnetpruning-keep-recent = "1832727" 且 pruning-interval = "16"
InjectiveMainnetpruning-keep-recent = "1832727" 且 pruning-interval = "16"
KaiaKairos Testnet
KatanaMainnet
KaiaMainnet
LineaMainnet
LiskMainnet
LitecoinMainnet
LitecoinTestnet
Mantle塞波利亚
MantleMainnet
MegaETHMainnetBlock 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. 了解更多
MocaTestnetpruning-keep-recent = "550000" and pruning-interval = "16"
ModeMainnet
MonadTestnetOver 40,000 recent blocks available
MonadMainnetOver 40,000 recent blocks available
MorphHoodi
MorphMainnet
NEARTestnet
NEARMainnet
Optimism塞波利亚
OptimismMainnet
OsmosisMainnet
PeaqMainnet
PlasmaTestnet
PlasmaMainnet
PolkadotMainnet
PolygonAmoy Testnet
PolygonMainnet
RobinhoodMainnet
RobinhoodTestnet
SaharaTestnet
ScrollMainnet
SeiAtlantic Testnet3240000 blocks
SeiPacific Mainnet
SolanaDevnet6578505 slots
SolanaTestnet10964176 slots
SolanaMainnet
SolanaAlpenglow Testnetbest-effort — not guaranteed. History may reset to near-zero after node maintenance/upgrades or the cluster's periodic re-genesis.
SoneiumMainnet
SonicMainnet
StacksTestnet
StacksMainnet
Starknet塞波利亚
StarknetMainnet
StellarTestnetHorizon: ~1.43M ledgers (~90 days) & Stellar RPC: 17280 ledgers (~1 days)
StellarMainnetHorizon: ~1.5M ledgers (~90 days) & Stellar RPC: 120,960 ledgers (~7 days)
DATAAeneid Testnet
DATAMainnet
SuiMainnetYes (gRPC only)Full nodes: 14 epochs. Older data automatically routed to archive nodes
SuiTestnetFull nodes: 14 epochs
TempoMainnet
TempoTestnet
TRONNile Testnet
TRONMainnet
TONMainnet
Unichain塞波利亚
UnichainMainnet
VanaMoksha
VanaMainnet
World Chain塞波利亚
World ChainMainnet
X LayerMainnet
X LayerTestnet
XRP LedgerTestnetFull history after recent network reset
XRP LedgerMainnetStarts from ledger 32570 (Genesis)
XRPL EVMTestnet
XRPL EVMMainnet
ZcashMainnetPruning disabled
ZcashTestnetPruning disabled
ZKSync塞波利亚
ZKSyncMainnet
ZoraMainnet