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

# Developers

> Build smart contracts and dApps on Autheo Chain — an EVM-compatible blockchain built on Cosmos SDK. Start here.

Autheo Chain is EVM-compatible, so any Solidity contract that runs on Ethereum runs on Autheo with no changes. It is also built on the Cosmos SDK, which means you can interact with native chain modules (staking, governance, IBC) using the `autheod` CLI or the REST/JSON-RPC APIs.

## What you can build

* **EVM smart contracts** — ERC-20 tokens, NFTs, DeFi protocols, any Solidity contract
* **dApps** — Connect MetaMask or WalletConnect; use ethers.js or viem as usual
* **Indexers and analytics** — Query the block explorer REST API or subscribe via WebSocket
* **Cosmos-native integrations** — Interact with `x/license`, `x/staking`, `x/bank` via CLI or gRPC

## Fastest path to first success

<Steps>
  <Step title="Set up your wallet">
    Install MetaMask and add the Autheo network. See [MetaMask install](/getting-started/wallets/metamask-install) and [Connect to testnet](/getting-started/wallets/connect-to-testnet).
  </Step>

  <Step title="Get testnet tokens">
    Request test THEO from the [testnet faucet](/getting-started/network/faucet) to cover gas fees.
  </Step>

  <Step title="Deploy your first contract">
    Open [Remix IDE](https://remix.ethereum.org), paste your Solidity contract, compile, and deploy directly to Autheo Testnet from MetaMask. Follow the step-by-step [deploy a smart contract](/developers/tutorials/deploy-smart-contract) guide.
  </Step>
</Steps>

## Choose your development path

<CardGroup cols={2}>
  <Card title="EVM / Smart Contracts" href="/developers/tutorials/deploy-smart-contract" icon="file-code">
    Deploy Solidity contracts using Remix, Hardhat, or Foundry. MetaMask is the only prerequisite.
  </Card>

  <Card title="Cosmos SDK / CLI" href="/developers/setup/dev-environment" icon="terminal">
    Use the `autheod` CLI to interact with native modules. Required for staking operations, key management, and node operation.
  </Card>
</CardGroup>

<Note>
  For EVM smart contract development with Remix IDE, the `autheod` CLI is optional. You can compile, deploy, and call contracts entirely through MetaMask. Install the CLI only if you need to interact with Cosmos-native modules or operate a node.
</Note>

## Prerequisites

Depending on your path, you may need familiarity with:

| Topic            | Why it matters                                       | Learn                                                         |
| ---------------- | ---------------------------------------------------- | ------------------------------------------------------------- |
| Solidity         | Primary language for EVM contracts on Autheo         | [soliditylang.org](https://soliditylang.org/)                 |
| OpenZeppelin     | Standard library for audited contract templates      | [openzeppelin.com](https://www.openzeppelin.com/)             |
| ethers.js / viem | JavaScript libraries for interacting with EVM chains | [docs.ethers.org](https://docs.ethers.org/)                   |
| MetaMask         | Browser wallet for EVM transaction signing           | [MetaMask install](/getting-started/wallets/metamask-install) |
| Cosmos SDK       | Framework underlying Autheo's native modules         | [docs.cosmos.network](https://docs.cosmos.network/)           |
| Go               | Required for building `autheod` from source          | [go.dev](https://go.dev/dl/)                                  |

## Network reference

| Network | JSON-RPC                          | Chain ID (EVM) | Chain ID (Cosmos) |
| ------- | --------------------------------- | -------------- | ----------------- |
| Mainnet | `https://rpc1.autheo.com`         | `2127`         | `autheo_2127-1`   |
| Testnet | `https://testnet-rpc1.autheo.com` | `785`          | `autheo_785-1`    |

See [Network endpoints](/getting-started/network/endpoints) for the full list including additional RPC endpoints, WebSocket, REST, and explorer URLs.