Skip to main content
This guide walks through submitting MsgCreateValidator on Autheo Chain. Complete Prerequisites, Installation, Key management, License setup, and Production deployment before starting.

Pre-flight checklist

  • autheod version returns 1.0.8
  • Sovereign NFT license is in LICENSE_STATUS_BOUND
  • Node is fully synchronized (catching_up: false)
  • Operator account has sufficient aauth balance

Step 1: Confirm your Sovereign license is BOUND

Must show status: BOUND. If showing ISSUED, bind it first:
If binding fails with ErrCooldownNotElapsed, query the cooldown: autheod query license category-policy 1

Step 2: Get your consensus public key

Copy the full JSON output — you need it in the next step.

Step 3: Submit MsgCreateValidator

--amount 1000000000000000000aauth = 1 THEO. Adjust to your desired self-delegation.
THEO uses 18 decimal places. 1 THEO = 10¹⁸ aauth. See Token overview for the full denomination table. Consider your self-delegation amount carefully — validators with higher stake are more competitive for the active set and more attractive to delegators. See Validator economics for guidance.

Step 4: Verify activation

Look for BOND_STATUS_BONDED, LICENSE_STATUS_ACTIVE, and tombstoned: false.

Post-creation operations

Edit validator details

Unjail after downtime

If your validator was tombstoned from double-signing, unjail is not possible. You must create a new validator with a new consensus key.

Day-to-day commands