Skip to content
Node operators
Node configuration

Node configuration


  • Operating system: MacOS(x86 intel chip) or Ubuntu (tested on 18.04).
  • Hardware: 4 cores, 8-16GB RAM, 512 GB drive, arm64 or amd64. Recommended 6-8 cores, 16-32 GB RAM, 1 TB+ drive.
  • Increase the maximum number of open files on your system. Example: ulimit -n 16384. You may wish to add this command to your shell profile so that you don't need to execute it next time you restart your machine.
  • CLI configuration.

Tip: Planning to run your own validator? Validators have different hardware requirements. See Validator setup.

Download binaries and initialize configuration

Clone the axelerate-community (opens in a new tab) repo:

git clone
cd axelarate-community

Run to download the axelard binary and configure your node:

./scripts/ -n [mainnet|testnet]

Some additional flags:

  • -a : Version of axelard.
  • -d : Home directory path.
  • --help : Print a complete list of flags.

Verifying Binaries

By default, the binary signatures are downloaded and the binary is verified using the axelardev (opens in a new tab) PGP key. To verify the binary manually, you can download the PGP signature and verify using the following commands:

curl | gpg --import
gpg --verify [axelard_binary_signature_path] [axelard_binary_path]

On github the signatures are attached to the releases. To download the signatures from the axelar-releases AWS Bucket, you can add .asc to the end of the binary URL. For example, if the path of the binary is:

The path for the signature will be:

Home directory

By default the script sets the home directory for your node as follows:

NetworkHome directory path

On a fresh install puts the following in your node's home directory:

├── bin
│   ├── axelard -> /Users/gus/.foo/bin/axelard-vx.y.z
│   └── axelard-vx.y.z
├── config
│   ├── app.toml
│   ├── config.toml
│   ├── genesis.json
│   └── seeds.toml
└── logs