> ## 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.

# Validator setup checklist

> A complete ordered checklist for setting up and activating a Sovereign validator on Autheo Chain, from license acquisition through validator operation and reward management.

Use this page as your navigator. Complete the steps in order — each links to the full guide for that step.

> [!WARNING]
>
> **Choose your validator carefully:** Autheo does not support redelegation. After delegating THEO, you must unstake and wait approximately **21 days** for the tokens to unbond before you can delegate them to a different validator. Review the validator's commission and other relevant details before delegating.

## Setup checklist

**1. Acquire a Sovereign NFT license**

Purchase a Sovereign license on the [Node Sale Platform](https://tsp.autheo.com). The license is an ERC-721 token on Arbitrum and is required to create a validator.

Full guide → [Purchasing a license](https://docs.autheo.com/web-apps/node-sale/purchasing-a-license.md)

**2. Bridge the license to Autheo Chain**

Use the [Autheo Bridge](https://hyper.autheo.com) 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](https://docs.autheo.com/web-apps/bridge/making-a-transfer.md)

**3. Verify prerequisites**

Confirm your server meets the hardware requirements: minimum **16 vCPU, 32 GB RAM, and 1 TB NVMe SSD**, with an additional 8–16 GB of RAM recommended for MemIAVL. Confirm that Ubuntu 22.04 LTS and the required firewall configuration are in place.

Full guide → [Prerequisites](https://docs.autheo.com/nodes/node-setup/node-setup.md)

**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](https://docs.autheo.com/nodes/node-setup/installation.md)

**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](https://docs.autheo.com/nodes/node-setup/license-setup.md)

**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 deployment](https://docs.autheo.com/nodes/node-setup/configuration.md)

Key management reference → [Key management](https://docs.autheo.com/developers/guides/key-management.md)

**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](https://docs.autheo.com/nodes/validator-lifecycle/register-validator.md)

**8. Claim rewards**

Once your validator is `ACTIVE`, two reward streams can accrue:

* **Staking rewards** — associated with delegated THEO.
* **NFT emission rewards** — associated with the active Sovereign license.

The two reward streams are separate and use different reward mechanisms.

Full guide → [Staking and rewards](https://docs.autheo.com/token/staking-and-rewards.md)

## Pre-launch verification

Before submitting `MsgCreateValidator`, confirm all of these:

```bash theme={null}
# 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>
```

> **Sovereign license required:** `MsgCreateValidator` can only be submitted when the validator operator's Sovereign license is in `BOUND` status. Prime and Core licenses are used for delegation and cannot be used to create a validator.

## Ongoing operations

After your validator is live:

| Task | Frequency | Command |
| - | - | - |
| Check node health | Daily | `autheod status` |
| Claim staking rewards | As needed | `autheod tx distribution withdraw-all-rewards` |
| Claim NFT emission rewards | As needed | `autheod tx licensedistribution claim-nft-rewards <license-id>` |
| Check for binary upgrades | Weekly | `autheod version` vs. [latest release](https://github.com/autheo-blockchain/autheo-chain-core/releases) |
| Unjail (if jailed) | When needed | `autheod tx slashing unjail --from <key>` |


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.