概述
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 | Galileo Testnet | 是 | 无 |
| 0g | 主网 | 是 | 无 |
| 摘要 | 测试网 | 是 | 无 |
| 摘要 | 主网 | 是 | 无 |
| Aleo | 主网 | 是 | 无 |
| 阿普托斯 | 测试网 | 是 | 无 |
| 阿普托斯 | 主网 | 是 | 无 |
| Arc | 测试网 | 是 | 无 |
| Arbitrum | Sepolia | 是 | 无 |
| Arbitrum | 主网 | 是 | 无 |
| Arbitrum Nova | 主网 | 是 | 无 |
| 雪崩 | 富士测试网 | 是 | 无 |
| 雪崩 | 主网 | 是 | 无 |
| 奥尔特 | 主网 | 是 | 无 |
| 奥尔特 | 测试网 | 是 | 无 |
| B3 | Sepolia | 不 | 128 blocks of state history |
| B3 | 主网 | 不 | 128 blocks of state history |
| Base | Sepolia | 是 | 无 |
| Base | 主网 | 是 | 无 |
| 贝拉海因 | Bepolia Testnet | 是 | 无 |
| 贝拉海因 | 主网 | 是 | 无 |
| 比特币 | 测试网 | 不 | Pruning disabled |
| 比特币 | 主网 | 不 | Pruning disabled |
| 比特币现金 | 测试网 | 是 | 无 |
| 比特币现金 | 主网 | 是 | 无 |
| 爆炸 | Sepolia | 是 | 无 |
| 爆炸 | 主网 | 是 | 无 |
| BNB | 测试网 | 是 | 无 |
| BNB | 主网 | 是 | 无 |
| 塞莱斯蒂娅 | 主网 | 是 | 无 |
| 塞莱斯蒂娅 | Mocha Testnet | 不 | pruning-keep-recent = "362880" |
| Celo | 主网 | 是 | 无 |
| 宇宙 | 主网 | 是 | Data available starting from cosmoshub-4 (block height 5200791); no support for cosmoshub-1/2/3 |
| 网络 | Sepolia | 是 | 无 |
| 网络 | 主网 | 是 | 无 |
| Doge | 主网 | 是 | 无 |
| 以太坊 | Sepolia | 是 | 无 |
| 以太坊 | 主网 | 是 | 无 |
| 以太坊 | Hoodi | 是 | 无 |
| Fantom | 主网 | 是 | 无 |
| Flare | Coston2 Testnet | 是 | 无 |
| Flare | 主网 | 是 | 无 |
| Flow | 测试网 | 不 | Root of current spork (epoch) |
| Flow | 主网 | 不 | Root of current spork (epoch) |
| 流利 | 主网 | 是 | 无 |
| 流利 | 测试网 | 是 | 无 |
| Fraxtal | 主网 | 是 | 无 |
| 燃料 | Sepolia | 是 | 无 |
| 燃料 | 主网 | 是 | 无 |
| 重力 | Alpha Mainnet | 是 | 无 |
| 诺斯替主义 | 主网 | 是 | 无 |
| Hemi | 测试网 | 是 | 无 |
| Hemi | 主网 | 是 | 无 |
| Hedera | 测试网 | 是 | 无 |
| 超流体 | 主网 | 是 | /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 eventsLearn more about Hyperliquid endpoints here |
| Hedera | 主网 | 是 | 无 |
| 不可变 zkEVM | 测试网 | 是 | 无 |
| 不可变 zkEVM | 主网 | 是 | 无 |
| 墨水 | Sepolia | 是 | 无 |
| 墨水 | 主网 | 是 | 无 |
| JOC | 主网 | 是 | 无 |
| 单射 | 测试网 | 不 | pruning-keep-recent = "1832727" and pruning-interval = "16" |
| 单射 | 主网 | 不 | pruning-keep-recent = "1832727" and pruning-interval = "16" |
| 凯亚 | Kairos Testnet | 是 | 无 |
| Katana | 主网 | 是 | 无 |
| 凯亚 | 主网 | 是 | 无 |
| 镜头 | 主网 | 是 | 无 |
| 镜头 | 测试网 | 是 | 无 |
| Linea | 主网 | 是 | 无 |
| Lisk | 主网 | 是 | 无 |
| 莱特币 | 主网 | 是 | 无 |
| 莱特币 | 测试网 | 是 | 无 |
| Mantle | Sepolia | 是 | 无 |
| Mantle | 主网 | 是 | 无 |
| MegaETH | 主网 | 不 | Block 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. 了解更多 |
| Moca | 测试网 | 不 | pruning-keep-recent = "550000" and pruning-interval = "16" |
| 模式 | 主网 | 是 | 无 |
| Monad | 测试网 | 是 | Over 40,000 recent blocks available |
| Monad | 主网 | 是 | Over 40,000 recent blocks available |
| Morph | Hoodi | 是 | 无 |
| Morph | 主网 | 是 | 无 |
| NEAR | 测试网 | 是 | 无 |
| NEAR | 主网 | 是 | 无 |
| 乐观主义 | Sepolia | 是 | 无 |
| 乐观主义 | 主网 | 是 | 无 |
| 渗透 | 主网 | 是 | 无 |
| Peaq | 主网 | 是 | 无 |
| 等离子体 | 测试网 | 是 | 无 |
| 等离子体 | 主网 | 是 | 无 |
| 波卡 | 主网 | 是 | 无 |
| Polygon | Amoy Testnet | 是 | 无 |
| Polygon | 主网 | 是 | 无 |
| Polygon zkEVM | Cardona Testnet | 是 | 无 |
| Polygon zkEVM | 主网 | 是 | 无 |
| 雷德斯通 | 主网 | 是 | 无 |
| Robinhood | 主网 | 是 | 无 |
| Robinhood | 测试网 | 是 | 无 |
| 撒哈拉 | 测试网 | 是 | 无 |
| 滚动 | 测试网 | 是 | 无 |
| 滚动 | 主网 | 是 | 无 |
| Sei | Atlantic Testnet | 不 | 3240000 blocks |
| Sei | Pacific Mainnet | 是 | 无 |
| 索拉纳 | Devnet | 不 | 6578505 slots |
| 索拉纳 | 测试网 | 不 | 10964176 slots |
| 索拉纳 | 主网 | 是 | 无 |
| 索拉纳 | Alpenglow Testnet | 不 | best-effort — not guaranteed. History may reset to near-zero after node maintenance/upgrades or the cluster's periodic re-genesis. |
| 索尼厄姆 | 主网 | 是 | 无 |
| 索尼克 | 主网 | 是 | 无 |
| 索福尼 | 主网 | 是 | 无 |
| Stacks | 测试网 | 不 | Pruning disabled |
| Stacks | 主网 | 不 | Pruning disabled |
| Starknet | Sepolia | 是 | 无 |
| Starknet | 主网 | 是 | 无 |
| Stellar | 测试网 | 不 | Horizon: ~1.43M ledgers (~90 days) & Soroban: 17280 ledgers (~1 days) |
| Stellar | 主网 | 不 | Horizon: ~1.5M ledgers (~90 days) & Soroban: 120,960 ledgers (~7 days) |
| DATA | Aeneid Testnet | 是 | 无 |
| DATA | 主网 | 是 | 无 |
| 隋 | 主网 | Yes (gRPC only) | Full nodes: 14 epochs. Older data automatically routed to archive nodes |
| 隋 | 测试网 | 不 | Full nodes: 14 epochs |
| Tempo | 主网 | 是 | 无 |
| Tempo | 测试网 | 是 | 无 |
| TRON | 主网 | 是 | 无 |
| TON | 主网 | 是 | 无 |
| Unichain | Sepolia | 是 | 无 |
| Unichain | 主网 | 是 | 无 |
| 瓦纳 | Moksha | 是 | 无 |
| 瓦纳 | 主网 | 是 | 无 |
| 世界链 | Sepolia | 是 | 无 |
| 世界链 | 主网 | 是 | 无 |
| X 层 | 主网 | 是 | 无 |
| X 层 | 测试网 | 是 | 无 |
| Xai | 测试网 | 是 | 无 |
| Xai | 主网 | 是 | 无 |
| XRP 账本 | 测试网 | 是 | Full history after recent network reset |
| XRP 账本 | 主网 | 是 | Starts from ledger 32570 (Genesis) |
| XRPL EVM | 测试网 | 是 | 无 |
| XRPL EVM | 主网 | 是 | 无 |
| Zcash | 主网 | 不 | Pruning disabled |
| Zcash | 测试网 | 不 | Pruning disabled |
| ZKSync | Sepolia | 是 | 无 |
| ZKSync | 主网 | 是 | 无 |
| 佐拉 | 主网 | 是 | 无 |
我们 ❤️ 反馈
❓ 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.