Skip to content

Latest commit

 

History

History
53 lines (34 loc) · 1.4 KB

changing_onchain_ip_address.md

File metadata and controls

53 lines (34 loc) · 1.4 KB

Update On-chain Node Discovery

Changing the IP address of your node so that validators and fullnodes can discover your node.

YOUR NODE WILL NOT BE REACHABLE FOR CONSENSUS IF:

  • The IDs in your yaml file diverge from what your mnemonic produces.
  • The IDs in your yaml file diverge from the on-chain configs.

Check your current on-chain configs

Use the query cli to print out your current on-chain configs.

ol query --val-config

Check what your curreny ID is

This tool uses your mnemonic to see what are the EXPECTED identities and public keys for this account.

ol whoami

Check what your node.yaml file uses as ID

Your node.yaml could be malformed. You'll want to check that the IDs used in the file correspond to what your mnemonic produces (with ol whoami).

ol whoami --check-yaml <path/to/node.yaml>

If YOUR node.yaml file does not match what your ol whoami shows you may need to redo the node configs.

ol init --val
ol inti --vfn

Update the on-chain configs

You will need to have two IP addresses 1) The validator IP, and 2) the VFN validator fullnode. After displaying the new configs, you will be asked to confirm the changes.

# send tx. Note the `-o` which means you are sending this from the "operator" account.
txs -o val-config --val_ip <IP> --vfn-ip <OTHER/IP>

# check if those changes persisted and if they are able to be read.
ol query --val-config