Skip to main content

TWIN Protocol

TWIN Protocol — 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).

TWIN Protocol — an AI/Agents | Consumer project on the Ethereum network, token (symbol: TWIN).

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 for creating “digital twins” of experts and monetizing them via a marketplace (claimed in the Tier‑1 whitepaper).
  • Who it’s for: experts/creators (who train their twins) and businesses/buyers who need access to knowledge/mentorship 24/7 (claimed).
  • Why onchain/token: the TWIN token is used within the ecosystem for transactions/platform usage and incentives (claimed in Tier‑1); the onchain artifact is confirmed as an ERC‑20 token on Ethereum.

How it works (very briefly)

  1. The user does: creates/trains their digital twin (documents, questionnaires, conversations/materials) and publishes it in the marketplace (claimed).
  2. The system does: trains and serves the twin agent, which answers/gives insights and provides access to buyers (claimed).
  3. The user gets: an AI agent (“twin”) that can be monetized via access in the marketplace.
  4. Where the blockchain is: the TWIN token on Ethereum is confirmed onchain; the Twin Vault blockchain storage is claimed in the whitepaper, but without addresses/contracts in Tier‑1.
  5. Token role (if any): the token is used for payments/ecosystem usage and as an incentive (users can earn TWIN when their skills are used) — claimed.

Quick links: AI thesis fit

Project passport

Field Value
Project name TWIN Protocol
Also known as (aliases) Twin Protocol, Twin Token, TWIN
Logo (logo) ../assets/590_twin-protocol_logo.webp
Token symbol (ticker) TWIN
Category AI/Agents | Consumer
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 0x48fd84c0dFC47F1b61eD6a86367895AaA6ad2a45
Token model (token_type) utility (payments + rewards)
Max supply 1,000,000,000 TWIN (max total supply)
Issuance fixed
Tokenomics (tokenomics, brief) Fixed supply; the token is used for transactions/ecosystem usage and can be exchanged for Twin Points (as claimed in the Tier‑1 docs).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) Twin Protocol (leadership team)
Funding (investors/funding) incubated by SingularityNET (as claimed)
AI component (ai_component) digital twins (AI agents)
Use‑case (use_case) skills marketplace + twin vault
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

TWIN Protocol, in its Tier‑1 documentation, describes a platform for creating “digital twins” of people, which are meant to preserve their knowledge/expertise and provide access to mentorship/insights 24/7. The project also describes a marketplace where such twins can be “tokenized” and made available to other users/companies.

In the context of DecAIHub, this is an applied AI product whose onchain part is explicitly confirmed via the TWIN ERC‑20 token on Ethereum. At the same time, claims about blockchain storage (“Twin Vault”) are present in the Tier‑1 text, but without a list of specific smart contracts/addresses, so the conclusions about onchain logic other than the token remain conservative.

Features/modules

  • Digital Twins: creation and training of personal twin agents from the user’s materials (claimed).
  • Twin Skills Marketplace: a marketplace for access to twin skills/expertise (claimed).
  • Twin Vault: blockchain‑based storage for data/memory/training data (claimed, without onchain addresses).
  • Twin Token + Points: the token and points as a mechanism of transactions/access within the ecosystem (claimed).

Typical scenarios

  • Scenario 1: an expert trains their twin → publishes it in the marketplace → receives rewards/a flow of tokens when it is used (claimed).
  • Scenario 2: a company buys/uses the twins of employees/experts → gets access to knowledge and saves on training/onboarding (claimed).

Getting started (wallet/network)

  • What you need: access to the project’s website/documentation; for onchain operations with the token — an EVM wallet.
  • Network/chain: Ethereum (for the TWIN token).
  • Fees: Ethereum fees (gas) for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: web platform; offchain AI components for training/serving twins; the TWIN token on Ethereum.
  • Participant roles: experts/creators of twins, users/buyers, companies/enterprise clients.
  • Where logic runs: AI logic and product scenarios — offchain; onchain, the token (ERC‑20) is explicitly confirmed.
  • Dependencies: Ethereum (token); integrations/dependencies of the AI stack are not disclosed as a Tier‑1 specification.

Token/economics (expanded, no forecasts)

  • Token utility (Tier‑1): the token is used for transactions/platform usage; users can earn tokens when their skills/twins are used (claimed).
  • Product necessity drivers: the token is described as “power usage” and as a mechanism of payments/incentives within the ecosystem (claimed).
  • Who pays fees: users/companies — the Ethereum fee (gas) for onchain operations with the token.
  • Where fees go: to Ethereum validators (gas), the general network model.
  • Issuance/burn: fixed supply; max total supply 1,000,000,000 TWIN (per the Explorer).
  • Security/incentive mechanisms: the incentive “earn TWIN when skills are accessed” (claimed); the onchain incentives mechanic (contracts/addresses) is not disclosed as a Tier‑1 fact.
  • Distribution and token issuance schedule: Tier‑1 describes the distribution categories (community rewards, team/advisors, development fund, partnerships), but without percentage figures/schedules in the available fragment.
  • Treasury: not established per Tier‑1 sources.

Governance

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

Security and incidents

  • Audits: no Tier‑1 confirmation found.
  • Bug bounty: no Tier‑1 confirmation found.
  • Incidents: no Tier‑1 confirmation found.
  • Threat model: the risks depend on the offchain AI/data storage and on the security of the token/wallets; without Tier‑1, the threat model remains general.

Project status and timeline

  • Current status: active (based on the presence of the Tier‑1 website/documentation and the token).
  • Key releases/milestones: the Tier‑1 roadmap gives a plan by phases (Foundation/Launch/Go‑to‑Market/Expansion, Q4 2023–Q3 2024).
  • Roadmap: see links_* (roadmap in the whitepaper).

Ecosystem/integrations

  • Integrations: not established per Tier‑1 sources.
  • Partners: the Tier‑1 whitepaper claims “incubated by SingularityNET”; other partners require separate recording.
  • Where it’s actually used: use cases are described as enterprise knowledge sharing and a skills marketplace (Tier‑1).

AI component of the project

  • What is real AI here? The Tier‑1 whitepaper describes the AI component as digital twins (AI agents) that are trained on a person’s materials and then interact with users.
  • What is truly onchain? The TWIN ERC‑20 token on Ethereum (the contract and max total supply are visible in the explorer).
  • Why is a token needed? Tier‑1 describes that the token “powers usage” and is used for transactions/incentives (including rewards to twin creators when used).
  • Red flags (based on the information found): absence of Tier‑1 AI quality metrics; absence of a list of specific onchain contracts of the product other than the token; no Tier‑1 description of governance/audits.

DecAI Fit component summary

  • DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
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): Tier‑1 sources describe the AI part as product functionality (digital twins), not as “intent only”.
  • Evidence: Tier‑1 — https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/introduction
  • Why sufficient / why not (one line): The intent item adds no signal when Tier‑1 already describes the AI purpose/mechanics of the product.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI is used to create digital twins that encapsulate a person’s expertise and interact with users (24/7 mentorship/insights).
  • Evidence: Tier‑1 — https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/introduction
  • Why sufficient / why not (one line): The Tier‑1 description directly explains the purpose of the AI part and the usage scenarios.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 reproducible demo example of the AI part (input→output) that can be repeated without invite‑based access/a closed setup was found.
  • Evidence: Tier‑1 — https://twinprotocol.com/ ; https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/introduction
  • Why sufficient / why not (one line): Tier‑1 sources describe the product, but do not provide a verifiable “touch surface” with a reproducible example.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/introduction
  • Why sufficient / why not (one line): No reproducible metrics of quality/accuracy of the AI part were found in the available Tier‑1 materials.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): The Tier‑1 whitepaper gives the technical context of the AI approach (neural‑symbolic techniques, OpenCog framework) and positions Twin AI technology.
  • Evidence: Tier‑1 — https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/introduction
  • Why sufficient / why not (one line): There is a tech description at the level of the approach/framework, sufficient for AI_4=1 without claims about metrics.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0x48fd84c0dFC47F1b61eD6a86367895AaA6ad2a45 (ERC‑20)
  • Evidence: Tier‑1 — https://etherscan.io/token/0x48fd84c0dFC47F1b61eD6a86367895AaA6ad2a45
  • Why sufficient / why not (one line): The Explorer confirms the token contract and max total supply.
  • 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; Twin Vault/Blockchain storage are described as a concept/POC without contract addresses).
  • Evidence: Tier‑1 — https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/introduction ; https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/roadmap
  • Why sufficient / why not (one line): OC_2 requires specific onchain mechanisms/contracts; Tier‑1 does not list them.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: it is not established per Tier‑1 sources that the product breaks down without the blockchain (other than the existence of the token).
  • Evidence: Tier‑1 — https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/introduction
  • Why sufficient / why not (one line): Tier‑1 contains statements about blockchain storage/security, but there is no proven criticality test.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, TWIN (ERC‑20, Ethereum).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x48fd84c0dFC47F1b61eD6a86367895AaA6ad2a45
  • Why sufficient / why not (one line): The Explorer confirms the onchain token.
  • 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): Tier‑1 describes that companies/buyers acquire Twin tokens to “power usage” of digital twins and access to knowledge/insights.
  • Evidence: Tier‑1 — https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/introduction
  • Why sufficient / why not (one line): Tier‑1 explicitly describes the token as a means of payment/access for using the product.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Tier‑1 describes that users can earn Twin Tokens when their skills/twins are available and used in the marketplace (an economic incentive to participate).
  • Evidence: Tier‑1 — https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/introduction
  • Why sufficient / why not (one line): The token is used as a mechanism for rewarding creators/participants of the ecosystem.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance via the token is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/introduction
  • Why sufficient / why not (one line): The available Tier‑1 sections contain no description of voting/a DAO 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 as a proven thesis is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/twin-token/about-the-twin-token
  • Why sufficient / why not (one line): 1 requires an explicit Tier‑1 justification “possible without the token without loss of meaning”; it was not found.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://etherscan.io/token/0x48fd84c0dFC47F1b61eD6a86367895AaA6ad2a45 Onchain fact: the TWIN ERC‑20 token (contract, max total supply 1,000,000,000).
Tier‑1 https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/introduction Tier‑1: description of the product (digital twins), the AI purpose and the role of the token (enterprise usage + rewards).
Tier‑1 https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/twin-token/about-the-twin-token Tier‑1: the TWIN ticker, fixed supply, token ↔ points, distribution categories (without figures).
Tier‑1 https://twinprotocol.gitbook.io/twin-protocol-ai-utility-token/white-paper/roadmap Tier‑1: roadmap (POC/alpha/AI milestones, token launch, blockchain storage POC).

No comments to display

Back to top