umeedbinary as this guide assumes you already have it installed and configured.
umeedwill store keys in your OS-backed keyring. You can change this behavior by specifying the
--recoverflag and the
keys addcommand will prompt you for the BIP39 mnemonic.
umeedprocess. The orchestrator requires access to a
gethnode's RPC instance. A
gethlight client can be used, but a full node is preferable.
gethnode or use a publicly available one. However, in production environments, it is recommended that you run your own. Depending on what network you're running your Umee validator on, you'll want to connect to or setup your
gethnode to the appropriate Ethereum network. See the
gethCLI documentation for more information on how to connect to different Ethereum networks.
gethservice is running and healthy. If so, and enable it:
gorc). The orchestrator serves multiple purposes, but it mainly acts as an off-chain relayer and oracle between the Umee network and Ethereum.
gethinstances running, next we configure the Gravity Bridge orchestrator:
gethrunning, you can finally create your validator on the Umee network via a
chain-idthat corresponds to the network you're joining. The key
val-oper-key-namecorresponds to the validator operator key you created earlier.
MsgDelegateKeystransaction. This process allows a validator to associate or "link" their orchestrator's Umee and Ethereum addresses with their validator's operator address:
MsgDelegateKeystransactions have been committed to the Umee network, you can finally start the
gorcservice is running and healthy. If so, and enable it: