Skip to main content
NEAR nodes provide RPC access to the network: exchanges use them to query balances, read blocks and receipt outcomes, and submit transactions. There are two types of RPC nodes: regular and archival. A regular RPC node keeps approximately 36 hours of history - 5 epochs of the NEAR blockchain, meanwhile, archival RPC nodes preserve older blocks, and account states for queries at earlier blocks. Exchanges can operate a regular RPC node and use its own archival node or an archival RPC provider for older data. Storage recommendations: RPC hardware · Archival hardware.

​
Regular RPC Node

A regular RPC node provides a gateway for day-to-day exchange operations. Use it to:
  • Read finalized blocks and receipt outcomes to monitor incoming deposits.
  • Submit withdrawals and track their execution.
  • Query current native and fungible-token balances for reconciliation.

​
Resources

​
Running an Archival Node

An archival RPC node provides past blocks, transaction and receipt outcomes, and account and contract states. Use it to:
  • Backfill deposits after downtime that exceeds a regular RPC node’s retention window.
  • Investigate older deposits, withdrawals, and their receipt chains.
  • Query native or fungible-token balances at older block heights for reconciliation.

​
Resources

​
Frequently Asked Questions

Yes, with an archival configuration and a complete history source. The run flag is:
Follow split-storage archival setup and select an appropriate snapshot for the network and supported node version. The flag does not restore history missing from a pruned snapshot.
Yes. JSON-RPC can be enabled or disabled; configure its listening address with rpc.addr in the node’s config.json file.
Yes.
Yes. GET /status and GET /health provide this interface.
  • /status: node version, block context, and syncing status. Use network RPC for peer information.
  • /health: success/failure if node is up running & progressing
Yes. Use a supported neard release or container image, persist the node’s home and storage volumes, and supply the network’s genesis and configuration. Pin the release and follow node operation guidance.
Mainnet is running. Select the appropriate network and use its supported genesis, configuration, and snapshot when starting a node.
Nodes signal supported protocol versions, and upgrades activate according to the protocol upgrade rules. Normal upgrades preserve the chain’s genesis and history. Follow supported node releases and test your integration before an activation boundary.