This site requires Javascript to be enabled.
  • Docs
  • Run a node
  • Prerequisites


This guide explains what are the requirements to install and run an Archway full node.

Hardware requirements:

The following hardware requirements are expected:

  • Linux distribution
  • x86_64 processor
  • 16 GB RAM
  • 500 GB to 2 TB storage*
  • Storage size for validators depends on the level of desired pruning.

Installing Prerequisites

Below are the packages that your machine needs to complete the installation process.

# updates and upgrades the list of local packagessudo apt-get update && sudo apt upgrade -y#installs docker, build-essential package and gitsudo apt-get install build-essential docker-ce docker-ce-cli docker-compose-plugin git

Installing Go

Go Version 1.16 or higher is required to run an Archway node. Please find a guide here on how to install Go.

Ensure the Go environment variables are set properly on your system.

As an example, you may need to install Go by running:

sudo apt install golang-go

and set up the GOPATH by launching:

export GOPATH=$HOME/goexport PATH=$PATH:$GOROOT/bin:$GOPATH/bin


export PATH=$PATH:/usr/local/go/bin

and applying those changes with:

source ~/.profile

Docker (optional)

You can also install archwayd by using Docker.



For Linux users, it's recommended to run the Docker daemon in Rootless Mode.

Next Steps

You are ready to go! Let's go forward with installing archwayd

The ARCH tokens will not be offered in the United States or to U.S. persons or to residents of certain other prohibited jurisdictions. Learn more here. The information provided in this website is for general informational purposes only. It does not constitute, and should not be considered, a formal offer to sell or a solicitation of an offer to buy any security in any jurisdiction, legal advice, investment advice, or tax advice. If you are in need of legal advice, investment advice or tax advice, please consult with a professional adviser. The Archway protocol is under development and is subject to change. As such, the protocol documentation and contents of this website may not reflect the current state of the protocol at any given time. The protocol documentation and website content are not final and are subject to change.