🏟️ Join the Testnet
Here is a list of Migaloo testnets along with their current status. You will need to know the version tag for installation of the
migaloodbinary. To install
migalood, follow the instructions in the installing migalood section.
To keep up with upgrades and syncing information on the active testnet, refer to the testnets repository, which is the definitive source of truth.
Operating System: Linux or macOS Disk Space: At least 100GB of free space is recommended. CPU: Multi-core processor, 4+ cores recommended RAM: 8GB+ recommended Network: Good internet connectivity
These specifications are the minimum recommended. As Migaloo Network is an open smart contract platform, it can at times be very demanding on hardware. Low spec validators WILL get stuck on difficult to process blocks.
It is important to note that the data on testnets increases as the blockchain progresses, thus requiring an expansion of storage as the blockchain database grows over time.
For this guide, we will be using shell variables. This will enable the use of the client commands verbatim. It is important to remember that shell commands are only valid for the current shell session, and if the shell session is closed, the shell variables will need to be re-defined.
If you want variables to persist for multiple sessions, then set them explicitly in your shell
.profile, as you did for the Go environment variables.
To clear a variable binding, use
unset $VARIABLE_NAME. Shell variables should be named with ALL CAPS.
<moniker-name>, this can be any name of your choosing and will identify your validator in the explorer. Set the
MONIKER_NAME="Moby Dick Validator"
Running a node is different from running a Validator. In order to run a Validator, you must create and sync a node, and then upgrade it to a Validator.
These instructions will direct you on how to initialise your node, synchronise to the network and upgrade your node to a validator.
migalood init $MONIKER_NAME --chain-id $CHAIN_ID
This will generate the following files in
Note that this means if you jumped ahead and already downloaded the genesis file, this command will replace it and you will get an error when you attempt to start the chain.
curl https://raw.githubusercontent.com/White-Whale-Defi-Platform/migaloo-chain/main/networks/testnet/genesis.json > ~/.migalood/config/genesis.json
This will replace the genesis file created using
migalood initcommand with the genesis file for the testnet.
#Set the base repo URL for the testnet & retrieve peers
PEERS=[email protected]:26656,[email protected]:26656,[email protected]:2000,[email protected]:3340,[email protected]:2550,[email protected]:37095,[email protected]:20756,[email protected]:26656,[email protected]:26656,[email protected]:20756,[email protected]:26656,[email protected]:20756,[email protected]:20756,[email protected]:26656,[email protected]:2000,[email protected]:3000,[email protected]:20756,[email protected]:26656,[email protected]:26656,[email protected]:20756
# check it worked
#Update persistent_peers setting in config.toml.
sed -i.bak -e "s/^persistent_peers *=.*/persistent_peers = \"$PEERS\"/" $HOME/.migalood/config/config.toml
$HOME/.migalood/config/app.toml, set gas prices:
#note testnet denom
sed -i.bak -e "s/^minimum-gas-prices *=.*/minimum-gas-prices = \"0uwhale\"/" ~/.migalood/config/app.toml
Create a new key pair or restore a key for your validator:
# Create new keypair
migalood keys add <key-name>
# Restore existing migaloo wallet with mnemonic seed phrase.
# You will be prompted to enter mnemonic seed.
migalood keys add <key-name> --recover
# Query the keystore for your public address
migalood keys show <key-name> -a
<key-name>with a key name of your choosing.
After creating a new key, the key information and seed phrase will be shown. It is essential to write this seed phrase down and keep it in a safe place. The seed phrase is the only way to restore your keys.
To request tokens type
$request <your-public-address> narwhalin the message field and press enter.
After starting the
migalooddaemon, the chain will begin to sync to the network. The time to sync to the network will vary depending on your setup, but could take a very long time. To query the status of your node:
# Query via the RPC (default port: 26657)
curl http://localhost:26657/status | jq .result.sync_info.catching_up
If this command returns
truethen your node is still catching up. If it returns
falsethen your node has caught up to the network current block and you are safe to proceed to upgrade to a validator node.
To upgrade the node to a validator, you will need to submit a
migalood tx staking create-validator \
--amount 9000000uwhale \
--commission-max-change-rate "0.1" \
--commission-max-rate "0.20" \
--commission-rate "0.1" \
--min-self-delegation "1" \
--details "validators write bios too" \
--pubkey=$(migalood tendermint show-validator) \
--moniker $MONIKER_NAME \
--chain-id $CHAIN_ID \
--gas-prices 0uwhale \
There are certain files that you need to backup to be able to restore your validator if, for some reason, it damaged or lost in some way. Please make a secure backup of the following files located in
It is recommended that you encrypt the backup of these files.