Skip to main content
Autheo Chain is an EVM-compatible Layer 1 blockchain derived from Cronos and built on Cosmos SDK v0.53.0. It extends standard staking with a custom NFT license gating system that governs who can operate validators and delegate stake.

Quick reference

ParameterValue
Chain ID (Cosmos) — Mainnetautheo_2127-1
Chain ID (EVM integer) — Mainnet2127
Chain ID (Cosmos) — Testnetautheo_785-1
Chain ID (EVM integer) — Testnet785
Binaryautheod
Current versionv1.0.8
Base denominationaauth
Decimals18 (1 THEO = 10¹⁸ aauth)
Address prefixautheo
Validator address prefixautheovaloper
Key algorithmeth_secp256k1
Block time~5 seconds
ConsensusCometBFT v0.38.17
Cosmos SDKv0.53.0

Key features

NFT license-gated staking — Validators require a Sovereign NFT license. Delegators require a Prime or Core license bound to their target validator. Licenses originate as ERC-721 tokens on Arbitrum and are bridged into the chain automatically via an EVM hook. Three license tiers — Each tier grants different staking rights and earns a fixed annual NFT emission reward.
TierPurposeAnnual THEO emission
SovereignCreate and operate a validator~187,969
PrimeExternal delegation (higher tier)~18,797
CoreExternal delegation (standard tier)~1,880
Dual reward streams — Staking rewards flow from x/mint via x/distribution automatically. NFT emission rewards accrue per block in x/emissions and require a manual claim via x/licensedistribution. Full EVM compatibility — Autheo Chain runs a full Ethermint EVM with Ethereum JSON-RPC on ports 8545 (HTTP) and 8546 (WebSocket). MetaMask, ethers.js, Hardhat, and Foundry all work with Mainnet Chain ID 2127. IBC support — Native interoperability via ibc-go v10.1.1.

Source code

https://github.com/autheo-blockchain/autheo-chain-core

Getting started

If you are a validator operator:
  1. Review Prerequisites
  2. Install the binary
  3. Configure key management
  4. Complete NFT license setup
  5. Follow the production deployment guide
  6. Create your validator
If you are a developer:
  1. Start with System architecture
  2. Review EVM integration
  3. See the Developer overview