Arbius
Arbius — 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).
Arbius — an AI/Inference | Infra project on the Ethereum network, token (symbol: AIUS).
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 decentralized protocol/marketplace for AI inference and model hosting.
- Who it’s for: developers and product teams that integrate inference; model creators; executors (solvers/miners) with GPUs.
- Why onchain/token: the token is used to pay for requests and to distribute incentives to network participants.
- What you can actually touch (Tier‑1): the Arbius playground (see
App / Demoin links_*).
How it works (very briefly)
- The user does: sends an inference/generation request via an interface or an integration.
- The system does: selects an executor (solver) and publishes/processes the task according to the protocol rules.
- The user gets: the result (for example, an image/text) and confirmation of execution/payment.
- Where the blockchain is: onchain records the token/payments and the related protocol states (at the level accessible via the Explorer).
- Token role: AIUS is used for payments and incentives (including rewards for useful work).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Arbius |
| Also known as (aliases) | AIUS |
| Logo (logo) | ../assets/571_arbius_logo.svg |
| Token symbol (ticker) | AIUS |
| Category | AI/Inference | 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 | 0x8AFE4055Ebc86Bd2AFB3940c0095C9aca511d852 |
| Token model (token_type) | utility (payments + staking + governance) |
| Max supply | 1,000,000 AIUS (max total supply) |
| Issuance | fixed |
| Tokenomics (tokenomics, brief) | Fixed supply; AIUS is used to pay for requests and for network incentives (including rewards for useful work). |
| Governance | DAO |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | decentralized AI inference/hosting marketplace |
| Use‑case (use_case) | AI inference marketplace + decentralized compute |
| DecAI Fit — AI thesis fit | 5/6 — high alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 2 / onchain_score 1 / token_score 3 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://arbius.ai |
| Docs | https://docs.arbius.ai/ |
| GitHub | https://github.com/semperai/arbius |
| Releases / Changelog | https://github.com/semperai/arbius/commits/master/ |
| Whitepaper | https://arbius.ai/paper.pdf |
| Roadmap | https://arbius.ai/roadmap |
| Security advisories | https://github.com/semperai/arbius/security |
| Explorer | https://etherscan.io/token/0x8AFE4055Ebc86Bd2AFB3940c0095C9aca511d852 |
| App / Demo | https://arbius.ai/playground |
| X | https://twitter.com/arbius_ai |
| Discord | https://discord.com/invite/eXxXMRCMzZ |
| Telegram | https://t.me/arbius_ai |
| Medium | https://medium.com/@arbius_ai |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/arbius |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/arbius/ |
General project overview
Arbius positions itself as a decentralized network/protocol for machine learning and AI inference: users send requests (for example, generation), and executors (solvers/miners) perform the work on GPUs and receive rewards. The Tier‑1 documentation describes the main protocol entities (tasks/solutions/contestations), as well as scenarios for integration and participation in the network.
Features/modules
- AI marketplace / hosting: hosting and using models via the project’s protocol/interfaces.
- Tasks / solutions / contestations: the mechanism for posting tasks, publishing solutions and contesting them (as the basic “skeleton” of verifiability).
- Incentives: incentives for executors (miners/solvers) via the AIUS token and the protocol rules (claimed in Tier‑1).
Typical scenarios
- Scenario 1: a user runs a request in the playground → receives the result and pays for execution according to the protocol rules.
- Scenario 2: an operator connects a solver/miner → performs network tasks and receives rewards (per the project documentation).
- Scenario 3: a developer/model creator registers a model → the model becomes available for use via the protocol.
Getting started (wallet/network)
- What you need: an EVM wallet and ETH for gas; the AIUS token — for payments/participation (see links_*).
- Network/chain: Ethereum (the AIUS token and onchain facts are observable via the Explorer).
- Fees: Ethereum fees (gas) + protocol payments/fees in AIUS (details — in the project documentation).
Architecture/tech (non‑AI)
- Components: onchain token contracts and protocol entities (see the Explorer and the documentation); offchain executors (solvers/miners) with GPUs; interfaces/integrations (see Docs).
- Participant roles: users; model creators/owners; solvers/miners; validators (the role is described in the docs).
- Where logic runs: computation/inference — offchain at the executors; accounting/payments and part of the state — onchain.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: AIUS is used to pay for requests (for example, generations) and for rewards to network participants.
- Protocol necessity drivers: the token is used as an instrument of incentives and of payment for the executors’ work (per the project’s Tier‑1 description).
- Who pays fees: users who initiate requests.
- Where fees go: gas — to Ethereum validators; the task fee under the protocol can be claimed by the executor/solver (claimSolution) after model fees are withheld (see Tier‑1 docs).
- Issuance/burn: fixed supply; max total supply 1,000,000 AIUS (see the Explorer).
- Security/incentive mechanisms: PoUW/rewards and the related mechanics are described in the documentation; the details of the parameters require separate verification.
- Distribution and token issuance schedule: —.
- Treasury: —.
Governance
- Who makes decisions: DAO (claimed: holders vote onchain).
- How protocol parameters change: via the governance process (see Docs).
- Where decisions are discussed/made: the documentation and GitHub (see links_*).
- Keys/multisig: —.
Security and incidents
- Audits: not found per Tier‑1 sources.
- Bug bounty: not found per Tier‑1 sources.
- Incidents: —.
- Threat model: risks of incentive misalignment, disputes over the quality of results and trust in offchain executors; the assessment requires the protocol parameters and the contestation/validation practices (see docs).
Project status and timeline
- Current status: mainnet (the token/network are observable via the Explorer).
- Key releases/milestones: not established per Tier‑1 sources (see commits in links_* as a trace of development).
- Roadmap: see links_*.
Ecosystem/integrations
- Integrations: ecosystem interfaces/products are listed on the Website (for example, Amica, Marketplace).
- Partners: not established per Tier‑1 sources.
- Where it’s actually used: usage examples/an integration guide are available in the official documentation (see links_*).
AI component of the project
- What is real AI here? The protocol positions itself as a decentralized network for AI/ML tasks (including inference/generations) with executors on GPUs.
- What is truly onchain? Onchain, the token and the related protocol artifacts accessible via the Explorer are observable; computation is performed offchain.
- Why is a token needed? AIUS is used to pay for requests and for incentives/rewards to network participants.
- Red flags (based on the information found): absence of Tier‑1 quality metrics for the model/inference (AI_3=0); most of the “quality/security” requires verification of the protocol parameters and the contestation/validation practices.
DecAI Fit component summary
- DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | medium | 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): In Tier‑1 sources, AI is described as a working product/protocol, not only as a “plan/intent”.
- Evidence: Tier‑1 — https://arbius.ai ; https://docs.arbius.ai/
- Why sufficient / why not (one line): AI_0 is used only for the intent signal in the absence of proof of AI functionality; here there is already a description of what exactly the AI part does (see AI_1/AI_2).
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): Arbius positions itself as a decentralized network/protocol for AI/ML tasks (including inference/generations) with requests executed by executors on GPUs.
- Evidence: Tier‑1 — https://arbius.ai ; https://docs.arbius.ai/
- Why sufficient / why not (one line): Tier‑1 describes the purpose (decentralized AI hosting/marketplace) and the basic “request → execution → result” principle.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 1
- Claim (one line): There is a public Arbius playground that allows sending a request (for example, generation) and receiving a result.
- Evidence: Tier‑1 — https://arbius.ai/playground ; https://docs.arbius.ai/
- Why sufficient / why not (one line): The existence of a public entry point and the mention of “try Arbius / playground” in the official documentation is sufficient for AI_2=1.
- 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.arbius.ai/
- Why sufficient / why not (one line): Per Tier‑1 sources, no Tier‑1 benchmark/quality metrics for the model/inference tied to a version/context were found.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): Per Tier‑1 sources, no single Tier‑1 tech description of the architecture/model versions was found (in a format sufficient for AI_4=1).
- Evidence: Tier‑1 — https://docs.arbius.ai/ ; https://arbius.ai/paper.pdf
- Why sufficient / why not (one line): There is documentation and a whitepaper, but without a dedicated “architecture/model versions” section for verifiable recording; we conservatively set 0.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: the AIUS token (ERC‑20) — 0x8AFE4055Ebc86Bd2AFB3940c0095C9aca511d852
- Evidence: Tier‑1 — https://etherscan.io/token/0x8AFE4055Ebc86Bd2AFB3940c0095C9aca511d852
- Why sufficient / why not (one line): The existence of an onchain token contract and an observable onchain page in the Explorer is sufficient for OC_1=1.
- 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 and onchain observability via the Explorer).
- Evidence: Tier‑1 — https://docs.arbius.ai/ ; https://etherscan.io/token/0x8AFE4055Ebc86Bd2AFB3940c0095C9aca511d852
- Why sufficient / why not (one line): OC_2=1 requires Tier‑1 recording of specific useful onchain logic of the protocol (not just the token); per Tier‑1 sources this is not confirmed.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: per Tier‑1 sources, it is not established that a key property of the product breaks down without the blockchain (in a format sufficient for OC_3=1).
- Evidence: Tier‑1 — https://docs.arbius.ai/
- Why sufficient / why not (one line): Explicit Tier‑1 argumentation “why onchain is critical” is needed; with insufficient data we set 0.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, AIUS (ERC‑20).
- Evidence: Tier‑1 — https://etherscan.io/token/0x8AFE4055Ebc86Bd2AFB3940c0095C9aca511d852
- Why sufficient / why not (one line): The onchain token page in the Explorer confirms the existence of the token and the symbol.
- 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): AIUS is used to pay for AI requests/generations in the Arbius ecosystem.
- Evidence: Tier‑1 — https://arbius.ai ; https://docs.arbius.ai/
- Why sufficient / why not (one line): Tier‑1 describes the purpose of the token as a means of payment for AI generations/requests.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): Executors (solvers/miners) receive rewards/awards for solving tasks (task rewards) and can be penalized (slashing) for incorrect solutions (Tier‑1).
- Evidence: Tier‑1 — https://docs.arbius.ai/tokenomics ; https://docs.arbius.ai/solutions
- Why sufficient / why not (one line): Tier‑1 tokenomics/solutions describe task rewards/claiming fee and the risk of slashing for incorrect solutions.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): AIUS is used for governance: holders vote (Snapshot), including delegation and voting parameters (Tier‑1).
- Evidence: Tier‑1 — https://docs.arbius.ai/governance ; https://docs.arbius.ai/tokenomics
- Why sufficient / why not (one line): Tier‑1 governance/tokenomics directly describe the use of AIUS for voting and for managing the treasury/upgrades.
- 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 subscription/stablecoin) is not established per Tier‑1 sources.
- Evidence: Tier‑1 — https://docs.arbius.ai/
- Why sufficient / why not (one line): TK_4=1 requires proof of replaceability without loss of the protocol’s meaning; in its absence — we set 0.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://arbius.ai | Positioning: decentralized AI hosting/marketplace; the role of AIUS (payments/incentives) — at the level of the project’s claims. |
| Tier‑1 | https://docs.arbius.ai/ | Official documentation (protocol entities, integration guides). |
| Tier‑1 | https://docs.arbius.ai/tokenomics | Tokenomics: payments for generations, governance, task rewards/slashing, treasury allocation (Tier‑1). |
| Tier‑1 | https://docs.arbius.ai/solutions | Solutions: submit/claim solution (receiving fees/rewards; mention of contestation/slashing) (Tier‑1). |
| Tier‑1 | https://docs.arbius.ai/governance | Governance: Snapshot voting, delegation and voting parameters (Tier‑1). |
| Tier‑1 | https://arbius.ai/playground | Public playground for sending requests/receiving results (AI_2). |
| Tier‑1 | https://etherscan.io/token/0x8AFE4055Ebc86Bd2AFB3940c0095C9aca511d852 | Onchain fact: the AIUS token, contract and max total supply. |
| Tier‑1 | https://arbius.ai/paper.pdf | Whitepaper (high‑level description of the protocol). |
| Tier‑1 | https://github.com/semperai/arbius | Public repository of the project (development artifact). |
| Tier‑2 | https://www.coingecko.com/en/coins/arbius | Token profile (context/navigation). |
| Tier‑2 | https://coinmarketcap.com/currencies/arbius/ | Token profile (context/navigation). |
| Tier‑3 | — | — |
No comments to display
No comments to display