Pular para o conteúdo principal

Archive Node


An archive node keeps all the past blocks. It plays a vital role on a blockchain: it connects users and dApps to the blockchain through WS and RPC endpoints. The public endpoints you can see in network details are running archive nodes.

Dapp projects need to run their own archive node to retrieve blockchain data they use in order not to rely on public infrastructure that will respond slower because of the large amount of users connected.


Be careful of the confusion with a full node that has a prunned database: a full node only keeps the past configured number of blocks (256 blocks by default) and uses much less storage space.

We are manitaining 3 different networks: the testnet Shibuya, Shiden as a parachain of Kusama, and Astar as a parachain of Polkadot.

Astar chainRelay ChainNameToken
TestnetTokyo (hosted by Astar)Shibuya$SBY



  • Storage space will increase as the network grows.
  • In case with Archive node, depending on the amount and frequency of data requested by a dApp, it may require a larger server.
SystemUbuntu 20.04
CPU8 cores
Memory16 GB
Hard Disk400 GB SSD NVMe


The Astar node runs in parachain configuration: they will listen at different ports by default for both the parachain and the embeeded relay chain.

DescriptionParachain PortRelaychain PortCustom Port Flag

For all types of nodes, port 30333 and 30334 need to be opened for imcoming traffics at Firewall. Collator node should not expose WS and RPC ports to the public.


There are 2 different ways to run an Astar node:

Using Binary - run the node from binary file and set it up as systemd service

Using Docker - run the node within a Docker container