Becoming a Validator

The command line examples provided in this guide necessitate specific configurations, including chain-id, signer account, and the minimum gas fee, to function correctly. For detailed information on these required settings and how to configure them, please consult the "Using Initiad" section.

Register as Validator

To participate as an Initia validator, submit the following transaction after you have successfully started an Initia node.

initiad tx mstaking create-validator \\
    --amount="<bond_amount>" \\
    --pubkey=$(initiad tendermint show-validator) \\
    --moniker="<your_moniker>" \\
    --identity="<keybase_identity>" \\
    --chain-id="<chain_id>" \\
    --from="<key_name>" \\
    --commission-rate="0.10" \\
    --commission-max-rate="0.20" \\
    --commission-max-change-rate="0.01"

Before submitting your transaction to participate as an Initia validator, ensure that all parameters are correctly configured:

• bond_amount: This is the amount of tokens you wish to self-bond. It can be in uinit or other tokens that are whitelisted as liquidity provider (LP) tokens.

• pubkey: The public key necessary for validator consensus. Typically, this is obtained from the output of the initiad tendermint show-validator command.

• your_moniker: A human-readable name for your validator. This should match either the moniker you used in the initiad init command or a moniker registered in the ~/.initia/config/config.toml file.

• chain_id: The ID of the chain you wish to join as a validator. It must correspond with the ID specified in the genesis.json file.

• key_name: The account address or name used to submit the transaction. The output of initiad keys show <key name> should correctly display your account details. If not, verify the accuracy of your key_name or keyring settings. A fee is required to submit the transaction, paid in the blockchain's native tokens.

• identity: An optional field for adding your Keybase identity information, which allows displaying an icon for your validator. This requires a 16-digit string associated with your Keybase account. Without this, no icon will be displayed in user interfaces.

• commission-rate: The commission rate you charge delegators, expressed as a fraction. It must be set above the min_commission_rate parameter specified by the mStaking protocol.

• commission-max-rate: The maximum commission rate you can charge as a validator.

• commission-max-change-rate: The maximum daily change in commission rate that is permissible for the validator.

Carefully review these parameters to ensure they are set correctly in your transaction. Incorrect settings can lead to transaction failure or unintended outcomes in your validator operations.

It is critical to back up your validator consensus private key and wallet. Ensuring the safety of these items is paramount for maintaining the security and integrity of your operations as a validator on the Initia network. Loss or compromise of these keys can lead to irreparable damage, including the loss of staked tokens and the ability to validate transactions. Always store backups in secure, offline locations to prevent unauthorized access.

Confirm Validator Information

The command line provided below is utilized to obtain information regarding the current network status and to enumerate the validators involved:

initiad query mstaking validators

Executing this command yields a list of validators, detailing their delegation shares, monikers, and whether they are currently jailed.

To identify your specific validator within the list provided by the above command, you can use the following command to reveal your validator's public key:

initiad tendermint show-validator

By comparing the public key obtained from this command with the consensus_pubkey of validators listed from the first command, you can determine which validator entry corresponds to yours. This comparison is only applicable if your validator is part of the active validator set.

Unjailing Validator

If your validator is found to be non-compliant, specifically by missing block signatures, it risks being jailed as a penalizing measure. Being jailed prevents the validator from participating in the consensus process and from earning rewards.

To restore your validator's active status, the following command can be used to unjail it:

initiad tx slashing unjail <validator address>

Replace <validator address> with the actual address of your jailed validator. This action requests the network to reinstate your validator's rights to participate in block validation, assuming all other conditions for being an active validator are met. It's crucial to address the underlying issues that led to jailing to prevent future occurrences.

Restoring your validator

Before proceeding with the restoration of your validator node, it's imperative to ensure that the node is fully halted. Undertaking the restoration process while the validator is active might lead to double signing, a serious offense that could result in the slashing of your delegated shares.

If your validator node stopped running, follow these steps to bring it back to operational status:

• Prepare a New Environment: Set up a new environment for an Initia node, ensuring it syncs to the latest block. This step is crucial for maintaining the integrity and continuity of the blockchain.

• Shutting down the old validator: To prevent double signing, you should shut down the old validator before starting a new validator node. This might result in some blocks missing.

• Replace the priv_validator_key.json File: Navigate to the ~/.initia/config directory on your new setup and replace the existing priv_validator_key.json file with the backup you previously created. This file contains your validator's private key and is essential for participating in the consensus process.

• Restart the Initia Node: Once the replacement is done, you can proceed to restart your Initia node. This action will reintegrate your validator into the network, allowing it to resume its validation duties.

• Clear the old validator: After setting up your new validator, remember to remove the priv_validator_key.json file from your old machine.

By following these steps, you can safely restore your validator node without risking unintended consequences, such as double signing or slashing. Always ensure your node and your environment are secure to prevent unauthorized access and potential security breaches.