This guide describes the process to configure and register an Omni Omega validator.

Pre-requisites

What you'll do

This guide will take you through the following steps:

  1. Update halo.toml config to include xchain.evm-rpc-endpoints for x-chain (cross chain) votes/attestations (L1 + L2).
  2. Obtain the halo consensus public key by running a docker compose command.
  3. Generate an operator address, or use an existing Ethereum EOA account.
  4. Fund the operator address with 200 OMNI on the Omni Omega chain.
  5. Add the operator address to the omni staking allow list.
  6. Run theomni operator create-validator CLI command to register the validator.

Instructions

1. Update halo.toml

Halo nodes running as validators require RPC endpoints for L1 and L2 cross chain validation duties. This must to be configured under [xchain.evm-rpc-endpoints] in the halo config file ~/.omni/omega/halo/config/halo.toml. The chains currently required are: arb_sepolia, base_sepolia, holesky, op_sepolia.

#######################################################################
###                             X-Chain                             ###
#######################################################################

[xchain]

# Cross-chain EVM RPC endpoints to use for voting; only required for validators. One per supported EVM is required.
# It is strongly advised to operate fullnodes for each chain and NOT to use free public RPCs.
[xchain.evm-rpc-endpoints]

arb_sepolia = "<http://my.arbitrum-sepolia.node:8545>"
base_sepolia = "<http://my.base-sepolia.node:8545>"
holesky = "<http://my.ethereum-holesky.node:8545>"
op_sepolia = "<http://my.op-sepolia.node:8545>"

Note that a halo node that is a validator will crash if all xchain RPC endpoints are not configured. Normal full nodes do not however need to connect to xchain RPCs, so this config is ignored by full nodes.