Skip to main content

Aethir

Aethir (ATH) — a reference card for a crypto project: what the product does and how verifiable the project’s key claims are; also — alignment with the Decentralized AI thesis (DecAI Fit).

Aethir describes itself as “distributed GPU-based compute infrastructure” (a decentralized GPU infrastructure) for AI applications/cloud computing/virtualized computing; the blockchain is used as a settlement layer for recording transactions and supporting incentives.

Disclaimer

Important: this page is a reference overview of the project. Within DecAIHub, we separately record a verification based on open sources within the AI thesis (what is real AI/onchain/why a token, and which sources this is based on).
This is not financial advice and not a recommendation to buy/sell/hold any asset. We do not assess price, returns, or entry/exit timing.
Conclusions are based on publicly available materials found as of the verification date. The absence of confirmation does not imply the absence of the technology.

TL;DR (for readers who are not into AI)

  • What it is: a compute infrastructure/marketplace (GPU compute), where some participants provide resources and others buy capacity.
  • Who it’s for: GPU providers (node operators) and compute consumers (including developers/companies that need capacity).
  • Why onchain/token: the blockchain — as the settlement/incentive accounting layer; the ATH token — for settlements within the ecosystem, staking requirements for operators and (claimed) governance.
  • What you can actually touch (Tier‑1): the docs contain a step‑by‑step guide to renting bare‑metal GPU servers “Aethir Earth” (AI/ML use‑case).

How it works (very briefly)

  1. The user does: buys compute (as a demand-side participant) or connects their own GPUs as a provider.
  2. The system does: matches resources to requirements, ensures quality and session accounting via the network components (Containers / Checkers / Indexers).
  3. The user gets: computing capacity (for AI workloads and other scenarios) or a reward for providing compute.
  4. Where the blockchain is: a settlement layer for recording transactions and incentives; the ATH token is issued as ERC‑20 (Ethereum) with cross‑chain use (Arbitrum/Solana via a bridge).
  5. Token role: a means of settlement, staking (including as a deposit for SLA/quality) and the claimed basis for future DAO governance.

Quick links: AI thesis fit

Project passport

Field Value
Project name Aethir
Also known as (aliases) Aethir Cloud, ATH
Logo (logo) ../assets/aethir_logo.svg
Token symbol (ticker) ATH
Category AI/Compute | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2024-06-12
Project status (status) active
Token (standard) ERC-20
Token contract 0xbe0ed4138121ecfc5c0e56b40517da27e6c5226b
Token model (token_type) utility (payments + staking + governance)
Max supply 42000000000 (ATH cap)
Issuance fixed (capped supply)
Tokenomics (tokenomics, brief) total supply 42B; utility: payments + staking + governance (DAO planned)
Governance company (DAO planned)
Admins/keys multisig (Ownable owner)
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) decentralized GPU cloud for AI/ML workloads
Use‑case (use_case) GPU compute rental/sales
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 3 / 3
Last verified 2026-02-10

General project overview

Aethir positions itself as a network/platform for supplying GPU compute “on demand”. According to the documentation, the “stack” distinguishes the roles of resource owners (GPU owners) and the internal network components (Containers/Checkers/Indexers), while the blockchain acts as a settlement layer for recording transactions and operating incentives.

From the “verifiability” standpoint, the Tier‑1 documentation contains a practical artifact: the workflow for renting Aethir Earth servers is described (choice of region/GPU/term/payment/access). This does not prove AI metrics, but it confirms the existence of a “product that can be launched”.

Features/modules

  • Containers / Checkers / Indexers: the network components mentioned in the docs for hosting compute, quality control and matchmaking against requirements.
  • Tokenomics + staking: ATH is used as a means of settlement and as a stake requirement for some operators.

Typical scenarios

  • Scenario 1 (compute buyer): a client buys computing capacity → pays in ATH → gets access to GPU resources.
  • Scenario 2 (compute provider): an operator connects compute → holds a stake (where required) → receives a reward.
  • Scenario 3 (renting GPU servers for AI/ML): a user rents an “Aethir Earth” server → chooses a region and GPU → gets access to a bare‑metal resource for their AI/ML workload (according to the step‑by‑step guide in the docs).

Getting started (wallet/network)

  • What you need: an EVM wallet (for Ethereum) for operations with ATH; for interactions with L2/bridge — the corresponding network.
  • Network/chain: the canonical ATH contract — Ethereum Mainnet; the docs also describe using ATH on Arbitrum L2 and bridging to Solana.
  • Fees: network fees (gas) + possible service fees (per the docs).

Architecture/tech (non‑AI)

  • Participant roles: resource owners (GPU suppliers), compute buyers, internal network components (Containers/Checkers/Indexers), treasury, settlement layer.
  • Where logic runs: compute execution — offchain; settlements/incentive accounting — via the blockchain settlement layer (as described in the docs).

Token/economics (expanded, no forecasts)

  • Token utility: ATH is described as a “medium of exchange” within Aethir (payment for compute), plus governance/participation and staking.
  • Staking and operator requirements: edge/IDC operators are “required to stake ATH”; the stake is described as a deposit that can be used for slashing if the SLA is not met.
  • Supply: total supply 42,000,000,000 ATH (capped).

Governance

The documentation speaks of moving toward a DAO (“moves towards establishing its DAO”), where ATH is used for governance; the current implementation of onchain governance is not specified in the sources above.

Security and incidents

  • Audits: no public audit report was found in the provided Tier‑1 sources.
  • Security advisories: a link to advisories in the checker-client GitHub repository is present.
  • Bug bounty: not found in Tier‑1 sources.

Project status and timeline

  • Current status: the project is active; the ATH token (listing date) is given as 2024‑06‑12.
  • Key milestones: listing/token overview (2024‑06‑12); release notes are published in the docs.
  • Roadmap: given in the docs.

Ecosystem/integrations

  • Repositories: the public checker-client.
  • Community channels: X/Discord/Telegram are listed in links_*.

AI component of the project

  • What is real AI here? At the level of Tier‑1 sources, Aethir describes “AI applications” scenarios as one of the main business cases for compute consumption; at the same time, this is infrastructure for AI workloads, not an “AI model in the protocol”.
  • What is truly onchain? The ATH token (ERC‑20, Ethereum) and the claimed settlement layer; explicit onchain logic beyond the token is not specified in the sources above.
  • Why is a token needed? ATH is used as a means of settlement in the ecosystem and as a staking requirement for operators; governance/DAO are declared as a direction.
  • Red flags (based on the information found): the absence in Tier‑1 of AI quality metrics/benchmarks (this is compute infrastructure); onchain‑washing (no explicit onchain logic beyond the token), token‑washing (details are needed: where exactly ATH is mandatory vs replaceable). The Tier‑1 “demo” shows renting GPU servers, but does not prove the uniqueness of “decentralization” as a property of the product (which is why OC_3 remains 0).

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality high 2
Onchain necessity low 1
Token necessity high 3
Evidence Tier‑1 present 3
Details

AI reality

AI_0 — AI intent (Tier‑1 roadmap) (1/0)

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 2.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Aethir provides GPU compute for AI/machine learning workloads (as a service/infrastructure), without claiming its own AI model as a protocol component.
  • Evidence: Tier‑1 — https://docs.aethir.com/aethir-cloud-customer-guide/dashboard
  • Why sufficient / why not (one line): Tier‑1 directly links “Aethir Earth” to AI/ML tasks; this is about infrastructure, not about the “project’s model”.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The Tier‑1 docs contain a step‑by‑step guide to renting “Aethir Earth” (GPU servers) for AI/ML tasks — a reproducible example of using the compute service.
  • Evidence: Tier‑1 — https://docs.aethir.com/aethir-cloud-customer-guide/how-to-rent-an-aethir-earth-server
  • Why sufficient / why not (one line): there are concrete steps (choice of GPU/region/term/payment/access), i.e. a demo surface of the product.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://docs.aethir.com/
  • Why sufficient / why not (one line): the available Tier‑1 pages contain no numerical AI quality metrics/benchmarks.
  • Conflict note (if any): —

AI_4 — tech description/architecture/versions (1/0)

  • AI_4 (decision): 0
  • Claim (one line): the architecture of the compute network is described, but not a technical description of an AI model/versions as the project’s own component.
  • Evidence: Tier‑1 — https://docs.aethir.com/aethir-network
  • Why sufficient / why not (one line): the architecture of a compute network ≠ documentation of the project’s AI model.
  • Conflict note (if any): —

Onchain necessity

OC_1 — contracts/addresses/chain (1/0)

  • OC_1 (decision): 1
  • Chain: Ethereum Mainnet (canonical token contract)
  • Addresses/identifiers: ATH ERC‑20: 0xbe0ed4138121ecfc5c0e56b40517da27e6c5226b
  • Evidence: Tier‑1 — https://docs.aethir.com/aethir-tokenomics/token-overview , https://etherscan.io/token/0xbe0ed4138121ecfc5c0e56b40517da27e6c5226b
  • Why sufficient / why not (one line): there is a specific token contract and Tier‑1 confirmation of the supply/address.
  • Conflict note (if any): —

OC_2 — onchain beyond just a token (1/0)

  • OC_2 (decision): 0
  • What useful logic is onchain: the Tier‑1 sources above do not specify concrete addresses/contracts of onchain logic (other than the token).
  • Evidence: Tier‑1 — https://docs.aethir.com/aethir-network
  • Why sufficient / why not (one line): the settlement layer is described as a concept, but without verifiable onchain addresses/mechanics.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: based on the available Tier‑1 sources, it cannot be strictly proven that without onchain the product “breaks down” rather than turning into an ordinary compute service.
  • Evidence: Tier‑1 — https://docs.aethir.com/aethir-network
  • Why sufficient / why not (one line): there is no specification of critical trustless onchain mechanics.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, ATH (ERC‑20).
  • Evidence: Tier‑1 — https://docs.aethir.com/aethir-tokenomics/token-overview
  • Why sufficient / why not (one line): the token overview records ATH and its parameters.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): ATH is described as a “medium of exchange” for buying compute from node operators.
  • Evidence: Tier‑1 — https://docs.aethir.com/aethir-tokenomics/ath-tokens-utility-and-purpose
  • Why sufficient / why not (one line): the docs explicitly state that the demand side pays operators in ATH.
  • Conflict note (if any): —

TK_2 — incentives/collateral/penalties (1/0)

  • TK_2 (decision): 1
  • Claim (one line): edge/IDC operators must stake ATH; the stake is a deposit for slashing in case of SLA violations.
  • Evidence: Tier‑1 — https://docs.aethir.com/aethir-tokenomics/ath-tokens-utility-and-purpose
  • Why sufficient / why not (one line): the source contains an explicit statement about the mandatory stake and the slashing motivation.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): Aethir declares a transition to a DAO; ATH holders will be able to propose and vote on changes.
  • Evidence: Tier‑1 — https://docs.aethir.com/aethir-tokenomics/ath-tokens-utility-and-purpose
  • Why sufficient / why not (one line): the docs describe the role of ATH in governance as a direction/intent.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token (for example, with a stablecoin) is not strictly proven in Tier‑1 sources.
  • Evidence: Tier‑1 — https://docs.aethir.com/aethir-tokenomics/ath-tokens-utility-and-purpose
  • Why sufficient / why not (one line): the text describes the current role of ATH, but does not perform a strict “replaceable/irreplaceable” test.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.aethir.com/aethir-network The Aethir stack and the explicit statement that the blockchain is used as a settlement layer for transactions/incentives
Tier‑1 https://docs.aethir.com/aethir-cloud-customer-guide/dashboard Aethir Earth is described in the docs as renting servers “typically for AI/machine learning tasks” (a link to AI workloads).
Tier‑1 https://docs.aethir.com/aethir-cloud-customer-guide/how-to-rent-an-aethir-earth-server A step‑by‑step guide to renting Aethir Earth GPU servers (a reproducible example of using the compute product).
Tier‑1 https://docs.aethir.com/aethir-tokenomics/token-overview ATH token parameters (ticker, listing date 2024‑06‑12, total supply 42B, Ethereum contract)
Tier‑1 https://docs.aethir.com/aethir-tokenomics/ath-tokens-utility-and-purpose the role of ATH: payments (medium of exchange), staking for operators, governance (DAO intent), AI applications as a use case
Tier‑1 https://etherscan.io/token/0xbe0ed4138121ecfc5c0e56b40517da27e6c5226b onchain confirmation: the ATH contract and “Max Total Supply 42,000,000,000 ATH”
Tier‑1 https://docs.aethir.com/checker-guide/release-notes the existence of a changelog/release notes as an artifact of product maintenance (Tier‑1)

No comments to display

Back to top