Sync a node
Download the Axelar blockchain, from a snapshot or from genesis.
There are two ways to sync your node:
- From a snapshot (recommended): download a recent snapshot of the blockchain and let your node catch up from there. This is the fastest way.
- From genesis: download the whole blockchain from the Axelar peer-to-peer network, switching
axelardversions at each upgrade height.
Prerequisites
- Set up your node as per Node setup.
- Ensure the
AXELARD_HOMEvariable is set in your current session. See Home directory (e.g.AXELARD_HOME="$HOME/.axelar").
Sync from a snapshot
Download the latest Axelar blockchain snapshot
Download the latest Axelar blockchain snapshot for your chosen network (testnet or mainnet) from a provider:
Axelar does not support state sync, so a snapshot should be more than 100GB in size.
The following instructions assume you downloaded the pruned snapshot from quicksync.io.
Let SNAPSHOT_FILE denote the file name of the snapshot you downloaded. Example file names:
- Mainnet:
axelar-dojo-1-pruned.xyz.tar.lz4 - Testnet:
axelartestnet-lisbon-3-pruned.xyz.tar.lz4
Decompress the downloaded snapshot into your ${AXELARD_HOME}/data directory.
# Ensure AXELARD_HOME env var is set or substitute it below
# Remove any existing data if it exists
rm -r ${AXELARD_HOME}/data
lz4 -dc --no-sparse [SNAPSHOT_FILE] | tar xfC - ${AXELARD_HOME}
# Verify that snapshot data was uncompressed
ls $AXELARD_HOME/dataStart your node
$AXELARD_HOME/bin/axelard start [moniker] --home $AXELARD_HOME >> $AXELARD_HOME/logs/axelard.log 2>&1 &Your Axelar node will launch and begin downloading the rest of the blockchain after the snapshot.
View your logs in real time
tail -f $AXELARD_HOME/logs/axelard.logYou should see the height (representing the downloaded blockchain) increasing in the logs.
... executed block height=690578 ...
... executed block height=690579 ...Sync from genesis
Follow the upgrade path
Configure your system as per Node setup except specify the correct version of axelard according to your network and position in the upgrade path:
| Core Version | Start Height | Upgrade Height |
|---|---|---|
| v0.10.7 | 0 | 384000 |
| v0.13.6 | 384001 | 1060850 |
| v0.14.1 | 1060851 | 1263450 |
| v0.15.0 | 1105250 | 1336350 |
| v0.16.1 | 1336350 | 1889000 |
| v0.17.3 | 1889000 | 2471750 |
| v0.18.3 | 2471750 | 2472290 |
| v0.19.4 | 2472290 | 3331350 |
| v0.20.0 | 3331350 | 3643500 |
| v0.21.1 | 3643500 | 3644000 |
| v0.24.0 | 3644000 | 3852250 |
| v0.26.5 | 3852250 | 4984950 |
| v0.28.0 | 4984950 | 5030000 |
| v0.29.1 | 5030000 | 5853000 |
| v0.31.2 | 5853000 | 6895400 |
| v0.33.2 | 6895400 | 9151750 |
| v0.34.3 | 9151750 | 11795700 |
| v0.35.5 | 11795700 | 14231100 |
| v1.0.5 | 14231100 | 15890800 |
| v1.1.2 | 15890800 | 16837700 |
| v1.2.1 | 16837700 | N/A |
| Core Version | Start Height | Upgrade Height |
|---|---|---|
| v0.13.6 | 690489 | 897350 |
| v0.14.1 | 897350 | 1105250 |
| v0.15.0 | 1105250 | 1249660 |
| v0.16.1 | 1249660 | 1619950 |
| v0.17.3 | 1619950 | 2183275 |
| v0.18.3 | 2183275 | 2257265 |
| v0.19.4 | 2257265 | 3356100 |
| v0.20.0 | 3356100 | 3429625 |
| v0.21.1 | 3429625 | 3445200 |
| v0.22.1 | 3445200 | 3536040 |
| v0.23.0 | 3536040 | 3620300 |
| v0.24.0 | 3620300 | 3827825 |
| v0.25.0 | 3827825 | 3842800 |
| v0.26.5 | 3842800 | 4868740 |
| v0.27.0 | 4868740 | 4874000 |
| v0.28.0 | 4874000 | 5093500 |
| v0.29.1 | 5093500 | 5895180 |
| v0.31.2 | 5895180 | 6315000 |
| v0.32.2 | 6315000 | 6939420 |
| v0.33.1 | 6939420 | 8528500 |
| v0.33.2 | 8528500 | 9462850 |
| v0.34.3 | 9462850 | 12017025 |
| v0.35.3 | 12017025 | 14625900 |
| v1.0.0 | 14625900 | 16665600 |
| v1.1.2 | 16665600 | 17629900 |
| v1.2.1 | 17629900 | N/A |
First, you have to change directory to "axelarate-community" repository.
cd axelarate-communityTo run setup-node.sh you have to specify the network (mainnet, testnet) and the axelard core version you want to use. You must follow the upgrade path as specified in the table above (it is different for each network). setup-node.sh will download axelard binary version you specified in "$AXELARD_HOME/bin" folder and create a symbolic link.
-rwxr-xr-x 1 kalid staff 70832530 Jul 6 11:04 axelard-v0.13.6
lrwxr-xr-x 1 kalid staff 48 Jul 6 11:04 axelard -> /Users/kalid/.axelar_testnet/bin/axelard-v0.13.6./scripts/setup-node.sh -n mainnet -a v0.10.7./scripts/setup-node.sh -n testnet -a v0.13.6Start your node with the newly configured axelard version:
$AXELARD_HOME/bin/axelard start --home $AXELARD_HOME >> $AXELARD_HOME/logs/axelard.log 2>&1 &Your Axelar node will resume downloading the blockchain.
View your logs in real time:
tail -f $AXELARD_HOME/logs/axelard.logAfter your blockchain has reached UPGRADE_HEIGHT you will see a panic in the logs like
panic: UPGRADE {NAME} NEEDED at height: {UPGRADE_HEIGHT}:Repeat this process for each entry in the upgrade path when the "panic" message appears in the logs.