Skip to main content

AI‑Chain

AI‑Chain — 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).

AI‑Chain — a project/brand, AICHAIN (ERC‑20 token AIT). A conflict was found in the sources: the domains aichain.me and aichain.finance look like different web properties, and no Tier‑1 confirmation that this is the same project/token was found (see Evidence).

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 public blockchain/protocol (there is an official Go implementation, go-aichain) + the ERC‑20 token AIT on the Ethereum network.
  • Who it’s for: developers/node operators who run an AICHAIN node; users/integrators who need access to the network/JSON-RPC (per the repository README).
  • Why onchain/token: the AIT token is confirmed by an onchain artifact on Ethereum; no Tier‑1 confirmation of the role of the AIT token in “AI computation” (as payment/incentives) was found. Claims about a “decentralized AI computing network” on aichain.finance are not confirmed as relating to the AIT token.

How it works (very briefly)

  1. The user does: sends an AI task to the network (per the project’s claim).
  2. The system does: distributes the task among nodes that perform computations (per the project’s claim).
  3. The user gets: the computation result.
  4. Where the blockchain is: the project claims publication/recording of results on the blockchain for transparency.
  5. Token role: not confirmed by Tier‑1 for specific product flows (payment/incentives/governance).

Quick links: AI thesis fit

Project passport

Field Value
Project name AI‑Chain
Also known as (aliases) AIChain
Logo (logo) ../assets/686_aichain_logo.png
Token symbol (ticker) AIT
Category AI/Other | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) —
Token (standard) ERC-20
Token contract 0x79650799e7899a802cb96c0bc33a6a8d4ce4936c
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) Not confirmed by Tier‑1.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) decentralized AI compute network
Use‑case (use_case) distributed-node execution of AI tasks
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 1 / 1 / 1
Last verified 2026-02-11

General project overview

Per Tier‑1 sources (official GitHub), there is an AICHAIN node implementation in Go (go-aichain) with a CLI client, JSON‑RPC and launch instructions. Separately, there is an ERC‑20 token, AIT, on the Ethereum network.

However, a source conflict was found: the website aichain.finance describes a “decentralized AI computing network”, but no Tier‑1 confirmation that this relates to the AIT token (contract on Ethereum) and/or the AICHAIN-CORE repositories was found. Therefore, flags that depend on “AI computation/marketplace” have been set conservatively.

Features/modules

  • Decentralized execution of AI computation by distributed nodes (per the project’s claim).
  • Claimed computation privacy mechanisms (ZK/FHE/MPC) — the implementation requires re‑checking (see Evidence).
  • Publication/recording of results on the blockchain (per the project’s claim).

Typical scenarios

  • Scenario 1: a developer submits an inference/analytics task → the network distributes computations → the developer receives the result (per the project’s claim).
  • Scenario 2: an operator sets up an AICHAIN node and provides JSON‑RPC/participates in the p2p network (per the repository README).

Getting started (wallet/network)

  • What you need: source code/instructions from go-aichain (Tier‑1).
  • Network/chain: Ethereum for the AIT token; a separate AICHAIN network/protocol is mentioned in go-aichain, while the mainnet explorer is “stopped” per the README.
  • Fees: standard Ethereum network fees apply to transactions of the ERC‑20 token AIT; fees/the economy of the AICHAIN network are not confirmed by Tier‑1 in this card.

Architecture/tech (non‑AI)

  • Components: an AICHAIN node (Go client), a p2p network, JSON‑RPC interfaces (per the repository README).
  • Participant roles: node operators/RPC users.
  • Where logic runs: onchain logic relates to the AICHAIN network/protocol (per the repository); the AI computation layer is not confirmed by Tier‑1 as part of this protocol.
  • Dependencies: not confirmed by Tier‑1 (other than the build/launch requirements from the repository).

Token/economics (expanded, no forecasts)

  • Token utility: not confirmed by Tier‑1.
  • Protocol necessity drivers: not confirmed by Tier‑1.
  • Who pays fees: Ethereum network fees are paid by senders of AIT token transactions.
  • Where fees go: to the Ethereum network validators (standard gas logic).
  • Issuance/burn: not confirmed by Tier‑1.
  • Security/incentive mechanisms: not confirmed by Tier‑1.
  • Distribution and token issuance schedule: not confirmed by Tier‑1.
  • Treasury: not confirmed by Tier‑1.

Governance

  • Who makes decisions: not confirmed by Tier‑1.
  • How protocol parameters change: not confirmed by Tier‑1.
  • Where decisions are discussed/made: not confirmed by Tier‑1.
  • Keys/multisig: not confirmed by Tier‑1.

Security and incidents

  • Audits: not confirmed by Tier‑1.
  • Bug bounty: not confirmed by Tier‑1.
  • Incidents: not confirmed by Tier‑1.
  • Threat model: not confirmed by Tier‑1.

Project status and timeline

  • Current status: not confirmed by Tier‑1.
  • Key releases/milestones: there are public go-aichain releases on GitHub (Tier‑1), without a link to product metrics/usage.
  • Roadmap: see links_*.

Ecosystem/integrations

  • Integrations: not confirmed by Tier‑1.
  • Partners: not confirmed by Tier‑1.
  • Where it’s actually used: not confirmed by Tier‑1.

AI component of the project

  • What is real AI here? No Tier‑1 confirmation of an AI component/AI‑intent for the AIT token and the go-aichain protocol was found (there is a source conflict with aichain.finance).
  • What is truly onchain? The onchain artifact of the AIT token is available in the Ethereum explorer; an AICHAIN node implementation (code) also exists, but the mainnet explorer is “stopped” per the README.
  • Why is a token needed? Not confirmed by Tier‑1 (there is no description of the protocol necessity of the AIT token).
  • Red flags (based on the information found): source/brand conflict; the absence of a Tier‑1 description of token utility; the absence of proof of an AI component.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 AI‑intent/roadmap for the AIT token and the go-aichain protocol was identified.
  • Evidence: Tier‑1 — https://github.com/AICHAIN-CORE/go-aichain ; https://etherscan.io/token/0x79650799e7899a802cb96c0bc33a6a8d4ce4936c
  • Why sufficient / why not (one line): the available Tier‑1 sources describe the node/protocol and the token, but do not confirm AI‑intent as part of the protocol/product.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Users submit AI tasks, and the network performs AI computation through nodes (per the project’s claim).
  • Evidence: Tier‑1 — https://github.com/AICHAIN-CORE/go-aichain
  • Why sufficient / why not (one line): No Tier‑1 confirmation of “AI tasks/AI computation” was found in the available sources.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demo/product example of “what you can touch” was found.
  • Evidence: Tier‑1 — https://github.com/AICHAIN-CORE/go-aichain
  • Why sufficient / why not (one line): there is no demo flow of AI computation/the product in Tier‑1 sources.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not confirmed by Tier‑1.
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://github.com/AICHAIN-CORE/go-aichain
  • Why sufficient / why not (one line): verifiable quality metrics/benchmarks for the AI subsystem are absent.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): There is a technical description/instructions for running a node (CLI, JSON-RPC) in the official go-aichain repository.
  • Evidence: Tier‑1 — https://github.com/AICHAIN-CORE/go-aichain
  • Why sufficient / why not (one line): The repository README and wiki provide technical context for the node/protocol.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ERC‑20 token: 0x79650799e7899a802cb96c0bc33a6a8d4ce4936c
  • Evidence: Tier‑1 — https://etherscan.io/token/0x79650799e7899a802cb96c0bc33a6a8d4ce4936c
  • Why sufficient / why not (one line): there is a Tier‑1 onchain artifact (the token contract).
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not confirmed by Tier‑1 (other than the ERC‑20 token); the existence of the AICHAIN network as “product onchain logic” is not justified in this card.
  • Evidence: Tier‑1 — https://github.com/AICHAIN-CORE/go-aichain
  • Why sufficient / why not (one line): there is node code, but no Tier‑1 onchain artifacts of the network (addresses/mainnet explorer) or a description of useful onchain logic of the product.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification of onchain criticality was found (why without the blockchain the product breaks down).
  • Evidence: Tier‑1 — https://aichain.finance/
  • Why sufficient / why not (one line): the criticality claim is not proven per the operational test.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has an ERC‑20 token (per the explorer).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x79650799e7899a802cb96c0bc33a6a8d4ce4936c
  • Why sufficient / why not (one line): the existence of the token is confirmed by an onchain artifact.
  • Conflict note (if any): —

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 0
  • Claim (one line): No Tier‑1 confirmation of payment for the service/computation with the AIT token was found.
  • Evidence: Tier‑1 — https://github.com/AICHAIN-CORE/go-aichain ; https://etherscan.io/token/0x79650799e7899a802cb96c0bc33a6a8d4ce4936c
  • Why sufficient / why not (one line): there is no explicit Tier‑1 description of “payment for the service” in terms of the token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): No Tier‑1 confirmation of incentives/staking mechanics of the AIT token in the protocol was found.
  • Evidence: Tier‑1 — https://github.com/AICHAIN-CORE/go-aichain
  • Why sufficient / why not (one line): there is no description of incentives/staking in terms of the AIT token in the available Tier‑1 sources.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): No Tier‑1 confirmation of the governance role of the token was found.
  • Evidence: Tier‑1 — https://github.com/AICHAIN-CORE/go-aichain
  • Why sufficient / why not (one line): there is no description of a governance process tied to the token.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The replaceability of the token is not confirmed by Tier‑1.
  • Evidence: Tier‑1 — https://github.com/AICHAIN-CORE/go-aichain
  • Why sufficient / why not (one line): Tier‑1 argumentation “replaceable/irreplaceable” is absent.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://github.com/AICHAIN-CORE/go-aichain Tier‑1 artifact: Go implementation of an AICHAIN node (CLI, JSON‑RPC, network description).
Tier‑1 https://etherscan.io/token/0x79650799e7899a802cb96c0bc33a6a8d4ce4936c Onchain artifact: ERC‑20 token AIT (contract on Ethereum) + a list of official links.
Tier‑1 https://aichain.finance/ Source conflict: a separate web property describing a “decentralized AI computing network”; a Tier‑1 connection to the AIT token/AICHAIN-CORE repositories is not confirmed.
Tier‑1 — No Tier‑1 source for claim “there is a demo/product you can touch (AI_2)” was found.
Tier‑1 — No Tier‑1 source for claim “the role of the AIT token in the protocol (TK_1..TK_3)” was found.

No comments to display

Back to top