-
Notifications
You must be signed in to change notification settings - Fork 11
Creating the Testnet Genesis
This document details the steps necessary to create a genesis file, specifically for the testnet.
There are two main sets of instructions, those for the host node that will compile the final genesis file and those for the other genesis nodes that will be part of the genesis validator set.
Both the host node and genesis validators should generate an app key pair.
To add your app key, you can use the uniond keys interface to either create a new key pair or import an existing key pair.
Note: The variable $KEY_NAME is to be replaced by whatever name you desire to locally refer to your app key by.
Create the new key pair, making sure to note the mnemonic seed and public key:
uniond keys add $KEY_NAMEEnsure the public key and other details match:
uniond keys show $KEY_NAME -aRestore existing Union wallet with mnemonic seed phrase:
uniond keys add $KEY_NAME --recoverEnsure the public key and other details match:
uniond keys show $KEY_NAME -aBefore anything else, an initial genesis file must be created with some basic configurations.
To create the initial genesis file at ~/.uniond/config/genesis.json, both the host node and genesis validators should run:
uniond init $MONIKER bn254This creates a new genesis file with the current time as the genesis_time.
At this point, you can move your consensus key from earlier to ~/.uniond/config/priv_validator_key.json.
Now, configuration of the genesis file can begin.
Before configuring other options of the genesis file, it's important to define the genesis tokens that will be present in our testnet.
For example, we could define nunion (nano Union) as having one billion indivisible units. We then replace instances of stake with nunion in ~/.uniond/config/genesis.json
Genesis accounts and their balances will need to be added to the genesis.json. This can be done manually, or with the uniond add-genesis-account command.
Each genesis validator will need to be added in this step. This means you should know the address and balance of each validator before this point. By default, a minimum stake of 10000000 is required for validators.
For example, to add Alice with 128000000000000 nunion you would run:
uniond add-genesis-account union1wupuxf8sqz3h24kzd90thrynh9w0ry7y9eu3jc 128000000000000nunionThe genesis.json file has many options for configuration. A good summary of what's available can be found in Cosmos Hub's Genesis File documentation.
Most notably, the sections:
At this point, the host node should supply the current genesis.json to the genesis validators so that they can create their genesis transactions.
Before the host node is able to produce the final genesis config, each validator needs to produce a genesis transaction and supply it to the host node.
Before continuing, replace ~/.uniond/config/genesis.json with the proto-config supplied by the host node.
To generate the genesis transaction, we will use uniond gentx.
The following values should be defined as follows:
-
KEY_NAMEName of the app key you created/restored earlier. -
STAKEThe stake you will put down to be a validator "1000000000000muno"(10000000 <= STAKE < genesis_balance). -
PUBKEYthe value returned fromuniond tendermint show-validator -
MONIKERYour moniker ID.
uniond genesis gentx $KEY_NAME $STAKE --chain-id union-testnet-7 --pubkey $PUBKEY --moniker $MONIKER --home $UNION_CONFIGNOTE: Make sure to pass the --home flag, even if use the default directory.
You can gentx for your validator in one command like this:
uniond genesis gentx $KEY_NAME $STAKE --chain-id union-testnet-7 --pubkey $(uniond tendermint show-validator --home $UNION_CONFIG) --moniker $MONIKER --home $UNION_CONFIG
This should create a .json file under ~/.uniond/config/gentx/. This .json file should be provided to the host node.
Ensure that the result of
cat path/to/your/priv_validator_key.json | jq ".pub_key.value"is identical to the result of
cat path/to/your/gentx-____.json | jq ".body.messages[0].pubkey.key"If these are identical, then you have used the correct priv_validator_key for the generation of your gentx.
The final step to produce a genesis file is to aggregate the genesis transactions created by the genesis validators.
The host node will be responsible for aggregating the transactions and dispersing the final genesis file.
Once the host node has all the genesis transaction files, they need to be moved to ~/.uniond/config/gentx.
Once the transaction files are all together, you can then run:
uniond collect-gentxsThis completes the creation of the genesis configuration.
Now the time has come to ensure each of the genesis validators have the final genesis file.
We have a repository for this at unionfi/genesis.
Here we should create a folder for the testnet and copy our genesis file into it.
mkdir union-testnet
cp ~/.uniond/config/genesis.json union-testnet/After you have contributed the genesis file, genesis validators will be able to obtain the final genesis config.
The last step for genesis validators is to obtain the genesis configuration and overwrite their current one with it.
To do this, run:
curl https://raw.githubusercontent.com/unionlabs/union/networks/genesis/union-testnet-3/genesis.json > ~/.union/config/genesis.jsonThis concludes the instructions for creating and sharing the genesis file.
Each validator that is part of the Genesis configuration (ie, expects that their gentx is included), should run
cat genesis.json | grep $(cat priv_validator_key.json | jq ".pub_key.value") to confirm that their validator key is included in the genesis.json.