Skip to main content

ArcBlock

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

ArcBlock — an AI/Agents | Infra project on Ethereum, token (symbol: ABT).

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/set of products for building applications (including via “blocklets”), as well as ArcBlock/AIGNE AI tools for developing and working with AI agents.
  • Who it’s for: developers and teams (platform/SDK/plugins), users of the products (for example, DID Wallet), engineers/content teams using ArcBlock’s AI tools.
  • Why onchain/token: the onchain fact (Tier‑1) is confirmed for the ABT token (ERC‑20 on Ethereum); the necessity of ABT for the operation of the AI tools is not explicitly shown in Tier‑1 sources.
  • What you can actually touch (Tier‑1): the AIGNE website https://www.aigne.io/en and open‑source toolkits for AI engineering: https://github.com/ArcBlock/idd, https://github.com/ArcBlock/agent-skills.

How it works (very briefly)

  1. The user does: chooses an ArcBlock product (for example, the AIGNE AI tools or the dev toolkits) and uses it in their workflow.
  2. The system does: provides “agentic”/LLM tools and plugins (AIGNE/IDD/agent‑skills) for creating/maintaining applications and content.
  3. The user gets: ready‑made AI tools (no‑code/low‑code and plugins) and/or ecosystem applications (for example, DID Wallet).
  4. Where the blockchain is: ABT is an ERC‑20 token on Ethereum; other onchain logic of the platform/products was not recorded in the Tier‑1 sources of this file.
  5. Token role: ABT exists as an onchain asset, but a mandatory role in ArcBlock’s AI products (payment/stake/access) is not confirmed in Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name ArcBlock
Also known as (aliases) ABT; AIGNE
Logo (logo) ../assets/83_arcblock_logo.png
Token symbol (ticker) ABT
Category AI/Agents | Infra
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2018-01-12
Project status (status) active
Token (standard) ERC-20
Token contract 0xb98d4c97425d9908e66e53a6fdf673acca0be986
Token model (token_type) —
Max supply 186 000 000
Issuance capped (Max Total Supply)
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit yes
Bug bounty yes
Team (team) ArcBlock
Funding (investors/funding) —
AI component (ai_component) AI-native dev toolkits (AIGNE/IDD)
Use‑case (use_case) AI agents + LLM app tooling
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 0 / evidence_score 3
Last verified 2026-02-11

General project overview

ArcBlock is an ecosystem of products and tools for application development and for working with digital identity (for example, DID Wallet), as well as a separate line of AI tools under the AIGNE brand.

In the available Tier‑1 sources, AIGNE is described as a no‑code Generative AI Apps Engine and a platform with “LLM adapters” (connecting different LLMs) and a “Studio” direction. Additionally, ArcBlock publishes open‑source tools for “AI‑native engineering” and an intent‑driven workflow (IDD), and a set of plugins/skills for AI‑assisted development.

Features/modules

  • AIGNE (no-code engine): a platform for building generative AI applications and pluggable LLM adapters.
  • AI-native engineering toolkits: IDD (Intent Driven Development) and Agent Skills (plugins/skills) for AI‑assisted engineering.
  • Ecosystem products: for example, DID Wallet (a standalone ArcBlock product).

Typical scenarios

  • Scenario 1 (engineer): connects the IDD toolkit → formulates an intent → runs an agentic TDD team according to the workflow.
  • Scenario 2 (engineer/team): installs “agent skills” and uses the plugins for content creation/development.
  • Scenario 3 (user): uses the ecosystem products (for example, DID Wallet).

Getting started (wallet/network)

  • What you need: depends on the product: for the GitHub toolkits — a developer environment; for the ABT token — an EVM wallet; for DID Wallet — the application/a device.
  • Network/chain: ABT — ERC‑20 on Ethereum.
  • Fees: Ethereum network fees for onchain operations with ABT.

Architecture/tech (non‑AI)

  • Components: a set of web/desktop/mobile products (for example, DID Wallet) and dev toolkits/repositories (IDD, agent‑skills).
  • Participant roles: users of the products; developers/content teams; holders of the ABT token.
  • Where logic runs: the AI part — offchain (platform/tools); the onchain part — ABT as an ERC‑20 token (Ethereum).
  • Dependencies: Ethereum infrastructure (RPC/wallets/explorers), the GitHub ecosystem for the open‑source tools, LLM providers (mentioned via adapters on AIGNE).

Token/economics (expanded, no forecasts)

  • Token utility: per Tier‑1, no description of “why ABT is needed specifically for the AIGNE/IDD products” is recorded → —.
  • Issuance/supply: Etherscan shows a max total supply of 186,000,000 ABT.
  • Who pays fees: users of the Ethereum network — for transactions with ABT (gas).

Governance

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

Security and incidents

  • Audits: an audit report is published (link in links_*).
  • Bug bounty: there is a bounty program issues repository (link in links_*).
  • Incidents: — (no public postmortems were found per Tier‑1).
  • Threat model: risks of the token smart contract (if used in the products), supply/admin key risks (if any), risks of the AI tools (output quality, prompt injections, leaks of LLM provider keys).

Project status and timeline

  • Current status: the ABT token is active on Ethereum; ArcBlock maintains an active blog and publishes AI tooling updates.
  • Key milestones: deployment of the ABT contract (2018‑01‑12); publications on AI‑native engineering (2025–2026).
  • Roadmap: — (not listed in links_*).

Ecosystem/integrations

  • Integrations: the GitHub ecosystem (open‑source toolkits), Ethereum (ABT token).
  • Partners: —.
  • Where it’s actually used: AIGNE as a product website/engine, IDD and Agent Skills as repositories with instructions.

AI component of the project

  • What is real AI here? AIGNE is positioned as a no‑code generative AI engine and a set of LLM adapters; ArcBlock publishes AI‑oriented dev toolkits (IDD, agent skills) for working with AI‑assisted development.
  • What is truly onchain? ABT is an ERC‑20 token on Ethereum (the address/deployment date and max supply are confirmed by the explorer).
  • Why is a token needed? Per Tier‑1, no evidence was found that ABT is mandatory for AIGNE/IDD/agent‑skills as a payment/stake/access mechanism.
  • Red flags (based on the information found): the AI part is predominantly offchain and tied to external LLM providers; the link between the ABT token’s utility and the AI products is not disclosed.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): the AI components are presented as already existing products/repositories, not only intent.
  • Evidence: Tier‑1 — https://www.aigne.io/en
  • Why sufficient / why not (one line): this is a description of a working product, not a roadmap promise.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AIGNE is an engine for generative AI applications and adapters to LLMs; IDD/agent‑skills are tools for AI‑assisted engineering.
  • Evidence: Tier‑1 — https://www.aigne.io/en ; https://github.com/ArcBlock/agent-skills
  • Why sufficient / why not (one line): AIGNE describes a no‑code engine and LLM adapters; agent‑skills describes plugins and a workflow for AI‑native engineering.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there are reproducible artifacts in the form of open‑source toolkits with installation/launch commands (IDD and agent skills).
  • Evidence: Tier‑1 — https://github.com/ArcBlock/idd ; https://github.com/ArcBlock/agent-skills
  • Why sufficient / why not (one line): the README contains concrete installation commands and a workflow.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — — (no public benchmarks/quality metrics of the AI agents/engine were found per Tier‑1)
  • Why sufficient / why not (one line): without quantitative metrics, AI_3 is not counted.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): the principles and structure of the toolkits are described (IDD lifecycle; plugin/skill architecture).
  • Evidence: Tier‑1 — https://github.com/ArcBlock/idd ; https://github.com/ArcBlock/agent-skills
  • Why sufficient / why not (one line): the README has the lifecycle structure and a diagram/commands.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ABT token 0xb98d4c97425d9908e66e53a6fdf673acca0be986 (deploy tx 2018‑01‑12)
  • Evidence: Tier‑1 — https://etherscan.io/token/0xb98d4c97425d9908e66e53a6fdf673acca0be986 ; https://etherscan.io/tx/0xbb63fc381e511565e984d844043046c58a536ad14a4e1f50f8d3d309f7a0e2bc
  • Why sufficient / why not (one line): the explorer confirms the contract and the creation timestamp.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: apart from the ABT token, no Tier‑1 confirmation of specific onchain logic of the protocol/products is recorded per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without addresses/contracts/a description of the onchain mechanics, we set 0.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: per the available Tier‑1 sources, the AI tooling can work without a blockchain; onchain criticality is not proven.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no confirmation that the key logic of the AI products is tied to 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, ABT (ERC‑20 on Ethereum).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xb98d4c97425d9908e66e53a6fdf673acca0be986
  • Why sufficient / why not (one line): the explorer confirms the existence of the token.
  • 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): ABT is used as the mandatory payment currency for ArcBlock’s AI services/products.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): this is not explicitly confirmed in the available Tier‑1 sources.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): ABT is needed as a stake/collateral/penalty for protocol security.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): not confirmed in the available Tier‑1 sources.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): ABT provides voting/governance of the protocol.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): governance mechanics are not confirmed in the available Tier‑1 sources.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): the ABT token is not shown as technically mandatory for ArcBlock’s AI tooling (AIGNE/IDD/skills).
  • Evidence: Tier‑1 — https://www.aigne.io/en ; https://github.com/ArcBlock/idd
  • Why sufficient / why not (one line): the AI products and toolkits are described without being tied to mandatory token payment.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.aigne.io/en The existence of the AIGNE product AI platform (no-code generative AI apps engine, LLM adapters).
Tier‑1 https://github.com/ArcBlock/idd A reproducible AI engineering toolkit (installation/commands/workflow) — demo/guide (AI_2).
Tier‑1 https://github.com/ArcBlock/agent-skills A set of plugins/skills for an AI‑native engineering workflow (description and quick start).
Tier‑1 https://etherscan.io/token/0xb98d4c97425d9908e66e53a6fdf673acca0be986 The onchain fact of the ABT token: ERC‑20, max total supply 186,000,000.
Tier‑1 https://etherscan.io/tx/0xbb63fc381e511565e984d844043046c58a536ad14a4e1f50f8d3d309f7a0e2bc Creation date of the ABT contract (2018‑01‑12).
Tier‑1 https://github.com/ArcBlock/bounty-program-issues A public bounty/issues repository (the existence of a bug bounty process).
Tier‑1 https://www.arcblock.io/content/blog The official ArcBlock blog (release/changelog feed).
Tier‑2 https://arcblock.io/whitepaper The whitepaper is available at the link, but the PDF was not extracted within the current check (used as navigation).

No comments to display

Back to top