Skip to main content

Connectome

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

Connectome — an AI/Agents project on the Ethereum network, token (symbol: —).

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/SDK for creating a “Virtual Human Agent” (assistant/character) based on AI (per the project’s claim).
  • Who it’s for: developers/creators who want to create AI assistants/characters; users who interact with agents.
  • Why onchain/token: the token exists (ERC‑20); per the Tier‑1 project description, blockchain is mentioned as the basis for a distributed marketplace of algorithms and “distributed AI learning”, but the token utility and specific onchain logic (other than the token) are not described.

How it works (very briefly)

  1. The user does: uses the platform/SDK to create or configure an agent.
  2. The system does: applies AI models (per the project’s claim) for the agent’s behavior/recognition/interaction.
  3. The user gets: an AI assistant/character and the result of the interaction.
  4. Where the blockchain is: it is not established in the available Tier‑1 sources which part of the product logic is truly onchain (other than the token).
  5. Token role (if any): the token utility is not described per Tier‑1 sources.

Quick links: AI thesis fit

Project passport

Field Value
Project name Connectome
Also known as (aliases) —
Logo (logo) ../assets/713_connectome_logo.svg
Token symbol (ticker) —
Category AI/Agents
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 0x9a1bf361798ef6538ccb8137ea900c4d4b48ca3d
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) VHA assistants + SDK
Use‑case (use_case) AI agent creation + use
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 0 / evidence_score 3
Last verified 2026-02-11

General project overview

Connectome describes itself as a platform for creating a “Virtual Human Agent” (VHA) and a set of AI features (recognition/behavior/SDK) for developers and users. However, it is not established per Tier‑1 sources which specific parts of the product run onchain (other than the existence of the token on the Ethereum network).

The Tier‑1 description also mentions: a distributed marketplace of algorithms (Connectome Market) and the goal of “distributed AI learning” based on blockchain, but without anchoring to specific contract addresses/modules of onchain logic.

Features/modules

  • VHA (Virtual Human Agent): a claimed “virtual assistant/character” model.
  • SDK: a claimed ability to create/configure agents.

Typical scenarios

  • Scenario 1: a developer uses the SDK → creates/configures an AI agent.
  • Scenario 2: a user interacts with an agent → receives responses/behavior in the application.

Getting started (wallet/network)

  • What you need: access to the platform/SDK (as described on the Tier‑1 website); onboarding requirements are not described.
  • Network/chain: Ethereum (for the token).
  • Fees: Ethereum network fees (gas) for token transactions.

Architecture/tech (non‑AI)

  • Components: the ERC‑20 token contract (Ethereum); product components are described at the feature level (VHA/SDK/recognition/market), but without details of the onchain part.
  • Participant roles: users, developers, token holders.
  • Where logic runs: the AI part and product logic are described per Tier‑1 at the claim level, but without onchain anchoring; the token is onchain.
  • Dependencies: Ethereum infrastructure for the token.

Token/economics (expanded, no forecasts)

  • Token utility: not described per Tier‑1 sources.
  • Protocol necessity drivers: —.
  • Who pays fees: users of the Ethereum network for token transactions.
  • Where fees go: to Ethereum validators/stakers (at the network level).
  • Issuance/burn: —.
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: —.
  • Treasury: —.

Governance

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

Security and incidents

  • Audits: No Tier‑1 audit report(s) found.
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: not established (other than the standard risks of an EVM token).

Project status and timeline

  • Current status: not established.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: —.
  • Partners: —.
  • Where it’s actually used: —.

AI component of the project

  • What is real AI here? Per the project’s claim, it is building a “Virtual Human Agent” and uses AI models for behavior/recognition.
  • What is truly onchain? The token contract on the Ethereum network and operations with it (Tier‑1: explorer).
  • Why is a token needed? Per Tier‑1 sources, the token utility is not described.
  • Red flags (based on the information found): Tier‑1 proof of onchain logic of the product (other than the token) and of token utility is not established.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): The Tier‑1 roadmap/AI intentions are not singled out separately.
  • Evidence: Tier‑1 — https://connectome.to/
  • Why sufficient / why not (one line): There is a description of the AI part (see AI_1), but “roadmap intent without proof” is not confirmed as a separate signal.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The project claims a VHA platform and the use of AI models for recognition (face/speech) and behavior/decision‑making.
  • Evidence: Tier‑1 — https://connectome.to/
  • Why sufficient / why not (one line): The Tier‑1 website describes what exactly the AI part of the product does at the feature level.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): Demos/public examples of the agent in operation are not identified per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no explicit App/Demo in links_*.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Metrics/benchmarks were not found.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A technical description of the AI architecture/versions is not identified per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The website claims features, but there is no tech description/model versions.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ERC‑20 contract: 0x9a1bf361798ef6538ccb8137ea900c4d4b48ca3d
  • Evidence: Tier‑1 — https://etherscan.io/token/0x9a1bf361798ef6538ccb8137ea900c4d4b48ca3d
  • Why sufficient / why not (one line): The onchain artifact (the token contract) is available in 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 (other than the token contract).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no confirmed onchain logic of the product beyond the token.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established that the product breaks down without onchain.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no justification of onchain criticality per Tier‑1/2.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token (ERC‑20) on the Ethereum network.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x9a1bf361798ef6538ccb8137ea900c4d4b48ca3d
  • Why sufficient / why not (one line): The token contract is available onchain.
  • 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): It is not established that the token is used to pay for the service.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No description of the token utility was found in the available sources.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/penalties using the token are not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of the incentive mechanics.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): It is not established that the token is used for governance.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of governance mechanics with 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 established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no data to justify replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://connectome.to/ The claimed functionality of the VHA platform and the use of AI models (a description of what the AI does).
Tier‑1 https://etherscan.io/token/0x9a1bf361798ef6538ccb8137ea900c4d4b48ca3d The ERC‑20 token contract and the Ethereum network (onchain fact).
Tier‑2 https://coinmarketcap.com/currencies/connectome/ Token profile (for reference; not proof of technology).
Tier‑3 https://medium.com/connectome-blog Publications/updates (claims require Tier‑1 confirmation).

No comments to display

Back to top