Run a Validator
Learn how to setup and run a validator node
Create Your Validator
Your node consensus public key (haqqvalconspub...) can be used to create a new validator by staking ISLM tokens. You can find your validator pubkey by running:
haqqd tendermint show-validator
🚨 DANGER: Never create your mainnet validator keys using a test keying backend. Doing so might result in a loss of funds by making your funds remotely accessible via the eth_sendTransaction JSON-RPC endpoint.
Ref: Security Advisory: Insecurely configured geth can make funds remotely accessible
To create your validator on Testnet
haqqd tx staking create-validator \
--amount=1000000aISLM \
--pubkey=$(haqqd tendermint show-validator) \
--moniker="choose a moniker" \
--chain-id="haqq_54211-3" \
--commission-rate="0.05" \
--commission-max-rate="0.10" \
--commission-max-change-rate="0.01" \
--min-self-delegation="1000000" \
--gas-adjustment=1.15 \
--gas=auto \
--from=<key_name> \
--node https://rpc.tm.testedge2.haqq.network:443
To create your validator on Mainnet
haqqd tx staking create-validator \
--amount=1000000aISLM \
--pubkey=$(haqqd tendermint show-validator) \
--moniker="choose a moniker" \
--chain-id="haqq_11235-1" \
--commission-rate="0.05" \
--commission-max-rate="0.10" \
--commission-max-change-rate="0.01" \
--min-self-delegation="1000000" \
--gas-adjustment=1.15 \
--gas=auto \
--from=<key_name> \
--node https://rpc.tm.haqq.network:443
When specifying commission parameters, the commission-max-change-rate is used to measure % point change over the commission-rate. E.g. 1% to 2% is a 100% rate increase, but only 1 percentage point.
Edit Validator Description
You can edit your validator's public description. This info is to identify your validator, and will be relied on by delegators to decide which validators to stake to. Make sure to provide input for every flag below. If a flag is not included in the command the field will default to empty (--moniker defaults to the machine name) if the field has never been set or remain the same if it has been set in the past.
The <key_name> specifies which validator you are editing. If you choose to not include certain flags, remember that the --from flag must be included to identify the validator to update.
The --identity can be used as to verify identity with systems like Keybase or UPort. When using with Keybase --identity should be populated with a 16-digit string that is generated with a keybase.io account. It's a cryptographically secure method of verifying your identity across multiple online networks. The Keybase API allows us to retrieve your Keybase avatar. This is how you can add a logo to your validator profile.
haqqd tx staking edit-validator
--new-moniker="choose a moniker" \
--website="https://islamiccoin.net" \
--identity=6A0D65E29A4CBC8E \
--details="To infinity and beyond!" \
--chain-id=<chain_id> \
--gas="auto" \
--gas-prices="0.025aISLM" \
--from=<key_name> \
--commission-rate="0.10"
The commission-rate value must adhere to the following invariants:
- Must be between 0 and the validator's
commission-max-rate - Must not exceed the validator's
commission-max-change-ratewhich is maximum % point change rate per day. In other words, a validator can only change its commission once per day and withincommission-max-change-ratebounds.
View Validator Description
View the validator's information with this command:
haqqd query staking validator <account_validator>
Track Validator Signing Information
In order to keep track of a validator's signatures in the past you can do so by using the signing-info command:
haqqd query slashing signing-info $(haqqd tendermint show-validator)\
--chain-id=<chain_id>
Unjail Validator
When a validator is "jailed" for downtime, you must submit an Unjail transaction from the operator account in order to be able to get block proposer rewards again (depends on the zone fee distribution).
haqqd tx slashing unjail \
--from=<key_name> \
--chain-id=<chain_id>
Confirm Your Validator is Running
Your validator is active if the following command returns anything:
haqqd query tendermint-validator-set | grep "$(haqqd tendermint show-address)"
You should now see your validator in one of Haqq explorers. You are looking for the bech32 encoded address in the ~/.haqqd/config/priv_validator.json file.
To be in the validator set, you need to have more total voting power than the 100th validator.
Halting Your Validator
When attempting to perform routine maintenance or planning for an upcoming coordinated
upgrade, it can be useful to have your validator systematically and gracefully halt.
You can achieve this by either setting the halt-height to the height at which
you want your node to shutdown or by passing the --halt-height flag to haqqd.
The node will shutdown with a zero exit code at that given height after committing
the block.
Common Problems
Problem #1: My validator has voting_power: 0
Your validator has become jailed. Validators get jailed, i.e. get removed from the active validator set, if they do not vote on 500 of the last 10000 blocks, or if they double sign.
If you got jailed for downtime, you can get your voting power back to your validator. First, if haqqd is not running, start it up again:
haqqd start
Wait for your full node to catch up to the latest block. Then, you can unjail your validator
Lastly, check your validator again to see if your voting power is back.
haqqd status
You may notice that your voting power is less than it used to be. That's because you got slashed for downtime!
Problem #2: My node crashes because of too many open files
The default number of files Linux can open (per-process) is 1024. haqqd is known to open more than 1024 files. This causes the process to crash. A quick fix is to run ulimit -n 4096 (increase the number of open files allowed) and then restart the process with haqqd start. If you are using systemd or another process manager to launch haqqd this may require some configuration at that level. A sample systemd file to fix this issue is below:
# /etc/systemd/system/haqqd.service
[Unit]
Description=Haqq Node
After=network.target
[Service]
Type=simple
User=ubuntu
WorkingDirectory=/home/ubuntu
ExecStart=/home/ubuntu/go/bin/haqqd start
Restart=on-failure
RestartSec=3
LimitNOFILE=4096
[Install]
WantedBy=multi-user.target
Problem #3: My node crashes because of validator set is nil in genesis and still empty after InitChain
Make sure you have a genesis file in $HOME/.haqqd/config/genesis.json if you don't have this file you can find it here
curl -OL https://raw.githubusercontent.com/haqq-network/mainnet/master/genesis.json && \
mv genesis.json $HOME/.haqqd/config/genesis.json
And also you can validate genesis file using this command
haqqd validate-genesis
Problem #4: I have an error while running validator wrong Block.Header.AppHash.
First of all, you should make sure that your bin file is up to date
haqq@haqq-node:~# haqqd -v
haqqd version "1.7.0" 1cdd044523cffd0a2428b139f611a48a60045a1b
We are currently using version 1.7.0 on Mainnet.
This error can also occur if you run the validator from a period when blocks were produced on a different version of the binary.
From this point, we recommend starting the node using statesync. More information you can find here
Unknown problems
If you encounter bugs that are not covered in our documentation portal, we'd love to see your bug report on our discord
Validator FAQ
If you have any problems with validator setting up you can visit our Validator FAQ page.