Zum Hauptinhalt springen

Supported Chains, Node Types, and Pruning Policies

Aktualisiert am
Sep 01, 2026

Übersicht​

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.

KetteNetzwerkArchivPruning Policy
0gGalileo TestnetJaKeine
0gMainnetJaKeine
AbstractTestnetJaKeine
AbstractMainnetJaKeine
AleoMainnetJaKeine
AptosTestnetJaKeine
AptosMainnetJaKeine
ArcTestnetJaKeine
ArbitrumSepoliaJaKeine
ArbitrumMainnetJaKeine
ArbitrumMainnetJaKeine
AvalancheFuji TestnetJaKeine
AvalancheMainnetJaKeine
AultMainnetJaKeine
AultTestnetJaKeine
B3SepoliaNein128 blocks of state history
B3MainnetNein128 blocks of state history
BaseSepoliaJaKeine
BaseMainnetJaKeine
BerachainBepolia TestnetJaKeine
BerachainMainnetJaKeine
BitcoinTestnetNeinPruning disabled
BitcoinMainnetNeinPruning disabled
BitcoinTestnetJaKeine
BitcoinMainnetJaKeine
BlastSepoliaJaKeine
BlastMainnetJaKeine
BNBTestnetJaKeine
BNBMainnetJaKeine
CelestiaMainnetJaKeine
CelestiaMocha TestnetNeinpruning-keep-recent = "362880"
CeloMainnetJaKeine
CosmosMainnetJaData available starting from cosmoshub-4 (block height 5200791); no support for cosmoshub-1/2/3
CyberSepoliaJaKeine
CyberMainnetJaKeine
DogeTestnetJaKeine
DogeMainnetJaKeine
EthereumSepoliaJaKeine
EthereumMainnetJaKeine
EthereumHoodiJaKeine
FantomMainnetJaKeine
FlareCoston2 TestnetJaKeine
FlareMainnetJaKeine
FlowTestnetNeinRoot of current spork (epoch)
FlowMainnetNeinRoot of current spork (epoch)
FluentMainnetJaKeine
FluentTestnetJaKeine
FraxtalMainnetJaKeine
FuelSepoliaJaKeine
FuelMainnetJaKeine
GIWASepoliaJaKeine
GravityMainnetJaKeine
GravityAlpha MainnetJaKeine
GnosisMainnetJaKeine
HemiTestnetJaKeine
HemiMainnetJaKeine
HederaTestnetJaKeine
HyperliquidMainnetJa/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
HederaMainnetJaKeine
ImmutableTestnetJaKeine
ImmutableMainnetJaKeine
InkSepoliaJaKeine
InkMainnetJaKeine
JOCMainnetJaKeine
InjectiveTestnetNeinpruning-keep-recent = "1832727" and pruning-interval = "16"
InjectiveMainnetNeinpruning-keep-recent = "1832727" and pruning-interval = "16"
KaiaKairos TestnetJaKeine
KatanaMainnetJaKeine
KaiaMainnetJaKeine
LineaMainnetJaKeine
LiskMainnetJaKeine
LitecoinMainnetJaKeine
LitecoinTestnetJaKeine
MantleSepoliaJaKeine
MantleMainnetJaKeine
MegaETHMainnetNeinBlock 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. Mehr erfahren
MocaTestnetNeinpruning-keep-recent = "550000" and pruning-interval = "16"
ModeMainnetJaKeine
MonadTestnetJaOver 40,000 recent blocks available
MonadMainnetJaOver 40,000 recent blocks available
MorphHoodiJaKeine
MorphMainnetJaKeine
NEARTestnetJaKeine
NEARMainnetJaKeine
OptimismSepoliaJaKeine
OptimismMainnetJaKeine
OsmosisMainnetJaKeine
PeaqMainnetJaKeine
PlasmaTestnetJaKeine
PlasmaMainnetJaKeine
PolkadotMainnetJaKeine
PolygonAmoy TestnetJaKeine
PolygonMainnetJaKeine
RobinhoodMainnetJaKeine
RobinhoodTestnetJaKeine
SaharaTestnetJaKeine
ScrollMainnetJaKeine
SeiAtlantic TestnetNein3240000 blocks
SeiPacific MainnetJaKeine
SolanaDevnetNein6578505 slots
SolanaTestnetNein10964176 slots
SolanaMainnetJaKeine
SolanaAlpenglow TestnetNeinbest-effort — not guaranteed. History may reset to near-zero after node maintenance/upgrades or the cluster's periodic re-genesis.
SoneiumMainnetJaKeine
SonicMainnetJaKeine
StacksTestnetJaKeine
StacksMainnetJaKeine
StarknetSepoliaJaKeine
StarknetMainnetJaKeine
StellarTestnetNeinHorizon: ~1.43M ledgers (~90 days) & Stellar RPC: 17280 ledgers (~1 days)
StellarMainnetNeinHorizon: ~1.5M ledgers (~90 days) & Stellar RPC: 120,960 ledgers (~7 days)
DATAAeneid TestnetJaKeine
DATAMainnetJaKeine
SuiMainnetYes (gRPC only)Full nodes: 14 epochs. Older data automatically routed to archive nodes
SuiTestnetNeinFull nodes: 14 epochs
TempoMainnetJaKeine
TempoTestnetJaKeine
TRONNile TestnetJaKeine
TRONMainnetJaKeine
TONMainnetJaKeine
UnichainSepoliaJaKeine
UnichainMainnetJaKeine
VanaMokshaJaKeine
VanaMainnetJaKeine
World ChainSepoliaJaKeine
World ChainMainnetJaKeine
X LayerMainnetJaKeine
X LayerTestnetJaKeine
XRP LedgerTestnetJaFull history after recent network reset
XRP LedgerMainnetJaStarts from ledger 32570 (Genesis)
XRPL EVMTestnetJaKeine
XRPL EVMMainnetJaKeine
ZcashMainnetNeinPruning disabled
ZcashTestnetNeinPruning disabled
ZKSyncSepoliaJaKeine
ZKSyncMainnetJaKeine
ZoraMainnetJaKeine
Zuletzt aktualisiert auf