Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.autheo.com/llms.txt

Use this file to discover all available pages before exploring further.

Use this page as your navigator. Complete the steps in order — each links to the full guide for that step.
MsgBeginRedelegate is permanently disabled on Autheo Chain. Once you delegate stake, you must unbond and wait the ~21-day unbonding period before moving it to a different validator. Choose your validator configuration carefully from the start.

​
Setup checklist

1

Acquire a Sovereign NFT license

Purchase a Sovereign license on the Node Sale Platform. The license is an ERC-721 token on Arbitrum and is required to create a validator.Full guide → Purchasing a license
2

Bridge the license to Autheo Chain

Use the Autheo Bridge to transfer your NFT from Arbitrum to your Autheo Chain EVM address. This automatically mints a LicenseRecord on-chain with status ISSUED.Full guide → Making a transfer
3

Verify prerequisites

Confirm your server meets the hardware requirements (minimum 16 vCPU, 32 GB RAM + 8–16 GB for MemIAVL, 2 TB NVMe SSD) and that your OS and firewall are configured correctly.Full guide → Node setup
4

Install autheod

Download the pre-built binary or build from source. Bootstrap with a snapshot to reduce sync time from ~24 hours to ~1 hour.Full guide → Installation
5

Bind the license on-chain

Submit MsgBindLicense to transition your license from ISSUED to BOUND. This step must be completed before you can create a validator.Full guide → License setup
6

Configure and start the node

Create your operator key and consensus key, configure config.toml and app.toml, set up the systemd service, and verify the node is syncing.Full guide → Production deploymentKey management reference → Key management
7

Register the validator

Confirm your license is BOUND, your node is fully synced (catching_up: false), and your operator account is funded. Then submit MsgCreateValidator.Full guide → Register validator
8

Claim rewards

Once your validator is ACTIVE, two reward streams accrue: staking rewards (via x/distribution) and NFT emission rewards (via x/licensedistribution). Both must be claimed manually.Full guide → Staking and rewards

​
Pre-launch verification

Before submitting MsgCreateValidator, confirm all of these: 
# Node is fully synced (catching_up must be false)
autheod status | jq '.SyncInfo.catching_up'

# License is BOUND
autheod query license license <license-id>

# Operator key exists and shows correct address
autheod keys show <key-name> --keyring-backend file

# Operator account has sufficient funds
autheod query bank balances <cosmos-address>
Self-delegation amount (the --amount flag in MsgCreateValidator) affects your position in the active validator set. A higher self-delegation signals commitment and can attract external delegators. See Validator program economics for guidance on competitive amounts and commission rates.

​
Ongoing operations

After your validator is live:
TaskFrequencyCommand
Check node healthDailyautheod status
Claim staking rewardsAs neededautheod tx distribution withdraw-all-rewards
Claim NFT emission rewardsAs neededautheod tx licensedistribution claim-nft-rewards <license-id>
Check for binary upgradesWeeklyautheod version vs. latest release
Unjail (if jailed)When neededautheod tx slashing unjail --from <key>