Skip to main content

infraX

infraX — 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).

infraX — an AI/Compute \| Infra project on the Ethereum network, token (symbol: INFRA).

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 platform that claims to provide GPU/AI resources: GPU rental/lending, AI node rental and AI API endpoints (Tier‑1 docs).
  • Who it’s for: users and teams that need GPU/AI resources and compute (claimed).
  • Why onchain/token: the INFRA token is observable onchain; the docs claim payments/tariffs in $INFRA (for example, $INFRA “needed to run GPU’s p/h”) and staking of $INFRA for ETH rewards.

How it works (very briefly)

  1. The user does: submits a request for a GPU/AI resource (rental/nodes/endpoints), or provides a GPU for lending (claimed).
  2. The system does: distributes requests across the network of AI nodes and returns the results; the docs claim the steps “Submission/Processing/Verification/Delivery”.
  3. The user gets: access to the resources/processing results (claimed).
  4. Where the blockchain is: the INFRA token is observable onchain; the docs claim “leveraging Blockchain technology” and payment/staking of the token.
  5. Token role: payment/participation in the platform economy (for example, tariffs in $INFRA) and staking of $INFRA for ETH rewards (claimed).

Quick links: AI thesis fit

Project passport

Field Value
Project name infraX
Also known as (aliases) INFRA
Logo (logo) ../assets/580_infrax_logo.png
Token symbol (ticker) INFRA
Category AI/Compute | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xe9eccde9d26fcbb5e93f536cfc4510a7f46274f8
Token model (token_type) utility (payments + staking)
Max supply 1,000,000 INFRA (max total supply)
Issuance fixed
Tokenomics (tokenomics, brief) Max total supply in the Explorer; the docs claim tariffs/participation in the network in $INFRA and staking of $INFRA for ETH rewards.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) GPU rental/lending + AI endpoints + AI nodes
Use‑case (use_case) access to GPU/AI resources (rental, nodes, endpoints)
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

infraX is positioned as a platform for “GPU and AI resources”: GPU lending, GPU rental, rental of AI nodes (nodes/servers) and a set of AI request endpoints (for example, for image/video processing). The documentation also mentions PAYG nodes and staking of $INFRA with ETH rewards (claimed). The Tier‑1‑verifiable onchain part is the INFRA token on the Ethereum network.

Features/modules

  • GPU Lending / GPU Rental (claimed): provision/rental of GPUs.
  • AI Nodes (claimed): access to AI servers at tariffs (including PAYG).
  • AI request Endpoints (claimed): API endpoints for tasks (including image/video processing).
  • Staking (claimed): staking of $INFRA with rewards in Ethereum.

Typical scenarios

  • Scenario 1: a user rents a GPU/node → gets compute resources (claimed).
  • Scenario 2: a user sends a request to an AI endpoint → gets the processing result (claimed).
  • Scenario 3: a user stakes $INFRA → gets rewards in ETH (claimed).

Getting started (wallet/network)

  • What you need: an EVM wallet (for the token/staking) and the product documentation (see links_*).
  • Network/chain: Ethereum.
  • Fees: Ethereum fees (gas) for onchain operations; tariffs/payment for resources are claimed in $INFRA.

Architecture/tech (non‑AI)

  • Components: the network of AI nodes (offchain), the platform interfaces (offchain), the INFRA token (onchain).
  • Participant roles: users; GPU/node providers (claimed).
  • Where logic runs: request distribution/processing — offchain; token/staking — onchain.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: payment/tariffs for the use of resources (the docs mention “$INFRA needed … p/h”) and staking for ETH rewards (claimed).
  • Protocol necessity drivers: if the tariffs/economics are tied to $INFRA, the token is used as a unit of account and an incentive for participation (claimed).
  • Who pays fees: users pay gas on the Ethereum network for onchain operations.
  • Where fees go: to the Ethereum network validators (gas), the general network model.
  • Issuance/burn: fixed supply (see max total supply in the Explorer).
  • Security/incentive mechanisms: staking of $INFRA for ETH rewards (claimed in the docs); details of the onchain staking mechanics are not established per Tier‑1 sources (the infraX Staking page is marked as “Coming soon”).
  • Distribution and token issuance schedule: not established per Tier‑1 sources.
  • Treasury: not established per Tier‑1 sources.

Governance

  • Who makes decisions: —.
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: no Tier‑1 confirmation found.
  • Bug bounty: no Tier‑1 confirmation found.
  • Incidents: no Tier‑1 confirmation found.
  • Threat model: risks of the token contract/integrations, as well as risks of the centralized/offchain components of the compute platform.

Project status and timeline

  • Current status: active (in terms of the token on Ethereum; the product is described in the docs).
  • Key releases/milestones: not established per Tier‑1 sources.
  • Roadmap: see links_* Roadmap.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: not established per Tier‑1 sources.

AI component of the project

  • What is real AI here? The Tier‑1 docs describe infrastructure for GPU/AI resources and AI endpoints (image/video processing), as well as “AI Nodes”.
  • What is truly onchain? The INFRA token (ERC‑20) on the Ethereum network.
  • Why is a token needed? The docs claim tariffs/participation in the platform economy via $INFRA and staking of $INFRA for ETH rewards.
  • Red flags (based on the information found): the docs contain broad claims about “L1 blockchain processing/verification” without reference to specific onchain logic/contracts (OC_2 is left at 0).

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 1
Onchain necessity low 1
Token necessity medium 2
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 = 1.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): infrastructure for AI workloads: AI nodes and API endpoints for AI processing (image/video), claimed in the docs.
  • Evidence: Tier‑1 — https://infrax.gitbook.io/infrax-documentation
  • Why sufficient / why not (one line): the Tier‑1 document lists the AI modules and use cases.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): a public demo/application with a direct check of the AI endpoints was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://infrax.gitbook.io/infrax-documentation/the-infrax-dapp/infrax-nodes
  • Why sufficient / why not (one line): the docs describe the dApp interface/pages, but do not give a direct public link to a working demo endpoint.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not found per Tier‑1 sources.
  • Context (version/date/how measured): not established.
  • Evidence: Tier‑1 — https://infrax.gitbook.io/infrax-documentation
  • Why sufficient / why not (one line): the Tier‑1 documentation contains no reproducible AI quality/performance metrics.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): a tech specification of the AI endpoints/internal compute architecture is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://infrax.gitbook.io/infrax-documentation/how-it-works
  • Why sufficient / why not (one line): the docs describe the process at a high level, but without a detailed architecture/versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: INFRA token: 0xe9eccde9d26fcbb5e93f536cfc4510a7f46274f8
  • Evidence: Tier‑1 — https://etherscan.io/token/0xe9eccde9d26fcbb5e93f536cfc4510a7f46274f8
  • Why sufficient / why not (one line): the token address and network are confirmed by the Explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established per Tier‑1 sources (other than the token; onchain processing “leveraging the power of the L1 blockchain” is claimed, but without specific contracts/addresses).
  • Evidence: Tier‑1 — https://infrax.gitbook.io/infrax-documentation/how-it-works
  • Why sufficient / why not (one line): OC_2 requires specific onchain mechanisms; Tier‑1 does not disclose them.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the compute logic and AI endpoints can be implemented offchain; onchain criticality is not proven.
  • Evidence: Tier‑1 — https://infrax.gitbook.io/infrax-documentation/how-it-works
  • Why sufficient / why not (one line): there is no Tier‑1 proof of inoperability without the blockchain.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, INFRA (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xe9eccde9d26fcbb5e93f536cfc4510a7f46274f8
  • Why sufficient / why not (one line): the token is observable in the Explorer.
  • 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): the docs claim tariffs/payment for the use of GPUs/nodes in $INFRA (for example, “$INFRA needed … p/h”).
  • Evidence: Tier‑1 — https://infrax.gitbook.io/infrax-documentation/the-infrax-dapp/infrax-nodes
  • Why sufficient / why not (one line): the Tier‑1 page explicitly speaks of $INFRA as the unit of tariff/account.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): the docs claim staking of $INFRA with rewards in Ethereum (an incentive for participation).
  • Evidence: Tier‑1 — https://infrax.gitbook.io/infrax-documentation
  • Why sufficient / why not (one line): the Tier‑1 Welcome page lists “Staking for ETH Rewards”.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the use of the token in governance is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://infrax.gitbook.io/infrax-documentation
  • Why sufficient / why not (one line): the docs contain no explicit description of governance via 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 has not been assessed (the docs claim tariffs in $INFRA and staking).
  • Evidence: Tier‑1 — https://infrax.gitbook.io/infrax-documentation
  • Why sufficient / why not (one line): without a precise economic model/alternatives, replaceability cannot be reasonably asserted.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://etherscan.io/token/0xe9eccde9d26fcbb5e93f536cfc4510a7f46274f8 The infraX token (INFRA): contract and max total supply 1,000,000.
Tier‑1 https://infrax.gitbook.io/infrax-documentation Tier‑1 docs: list of features (GPU rental/lending, AI nodes, endpoints, staking for ETH rewards).
Tier‑1 https://infrax.gitbook.io/infrax-documentation/the-infrax-dapp/infrax-nodes Tier‑1: the interface mentions “$INFRA needed to run GPU’s p/h” (tariffs/payment in the token).

No comments to display

Back to top