Skip to main content

Three Protocol

Three 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).

Three Protocol — an AI/Other | Infra project (eCommerce/payments tools + claimed AI components; Tier‑1 website), token (symbol: THREE) on the Ethereum network.

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 set of solutions for eCommerce/payments, with the website claiming the following areas: privacy transactions (ZK), escrow contracts, a marketplace/jobs portal, payment services and AI modules (for example, “Procurement Matching Neural Network AI”).
  • Who it’s for: for users/businesses that need “crypto‑commerce” tools (claimed).
  • Why onchain/token: the THREE ERC‑20 token on the Ethereum network is confirmed; whether the token is mandatory for specific product features is not established per Tier‑1 sources.

How it works (very briefly)

  1. The user does: uses one of the ecosystem’s services (for example, payments/card, a marketplace/jobs portal, or other modules; claimed).
  2. The system does: performs operations offchain and/or onchain depending on the service (details are partially not established per Tier‑1 sources).
  3. The user gets: a payment/operation/product search/matching (claimed).
  4. Where the blockchain is: the THREE ERC‑20 token on Ethereum is confirmed; the Tier‑1 website claims smart contracts (including on Solana), but service contract addresses (other than the token) are not recorded.
  5. Token role (if any): whether the token is mandatory as “payment for the service” or as a protocol incentive is not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field Value
Project name Three Protocol
Also known as (aliases) Three Protocol Token, $THREE
Logo (logo) ../assets/805_three-protocol-token_logo.png
Token symbol (ticker) THREE
Category AI/Other | 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 0xa059b81568fee88791de88232e838465826cf419
Token model (token_type) —
Max supply 100,000,000 THREE
Issuance fixed (max total supply)
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit yes (audit PDF in links_*)
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) neural network for matching
Use‑case (use_case) eCommerce/payments tools
DecAI Fit — AI thesis fit 2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

Per the Tier‑1 website, Three Protocol describes a set of solutions for eCommerce/payments, including a privacy area (ZK), escrow contracts (“Tri‑Proof”), the “Procurement Matching Neural Network AI” module, as well as services/platforms such as “Jobs3” and “3PAY” (as parts of the ecosystem).

The onchain component confirmed per Tier‑1 sources is the THREE ERC‑20 token on the Ethereum network. The Tier‑1 website also claims smart contracts and components built on Solana (for example, Tri‑Proof smart contracts), but without recording addresses/contracts in links_*/Evidence, the assessment of onchain necessity remains conservative.

Features/modules

  • ZKi3s (claimed): anonymous transactions with a ZK approach.
  • Tri‑Proof smart contracts (claimed): escrow logic to reduce fraud in transactions.
  • Procurement Matching Neural Network AI (claimed): matching of products/preferences.
  • DAIOs (claimed): the concept of “Decentralised AI Organizations” for decisions/disputes.
  • 3PAY / Jobs3 (claimed): payment services and a jobs portal.

Typical scenarios

  • Scenario 1: a user uses an ecosystem payment service/tool → receives a processed operation (claimed).
  • Scenario 2: a user searches for a product/service → receives a match/result (claimed).

Getting started (wallet/network)

  • What you need: web access to the services; an EVM wallet — for the THREE token.
  • Network/chain: Ethereum — for the token.
  • Fees: Ethereum network fees apply to operations with the token.

Architecture/tech (non‑AI)

  • Components: ecosystem web services (offchain; details are not established) + the THREE ERC‑20 token (onchain).
  • Where logic runs: product features — mostly offchain; the token — onchain (Ethereum).

Token/economics (expanded, no forecasts)

  • Token utility: not established per Tier‑1 sources (Tier‑1 required).
  • Issuance/supply: max total supply 100,000,000 THREE (Etherscan).

Governance

  • Who makes decisions: —.

Security and incidents

  • Audits: there is a link to an audit PDF (see links_*).
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: typical web service risks and ERC‑20 token risks; details require separate verification.

Project status and timeline

  • Current status: active (website).
  • Roadmap: there is a roadmap page in GitBook (see links_*).

Ecosystem/integrations

  • Integrations: — (not established per Tier‑1 sources).

AI component of the project

  • What is real AI here? the Tier‑1 website claims AI modules (Neural Network AI for matching and DAIOs as a concept).
  • What is truly onchain? the THREE ERC‑20 token on the Ethereum network is confirmed.
  • Why is a token needed? not established per Tier‑1 sources (the model of token necessity in the product is not sufficiently described).
  • Red flags (based on the information found): absence of Tier‑1 artifacts confirming the onchain logic of modules (other than the token) with addresses/contracts, and absence of measurable quality metrics for the AI component.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI is claimed as part of the product, but we do not apply the “intent‑only” flag, as there are descriptions of features (AI_1).
  • Evidence: Tier‑1 — https://www.threeprotocol.ai/
  • Why sufficient / why not (one line): There are Tier‑1 descriptions of AI modules, but without demos/metrics.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): The website claims “Procurement Matching Neural Network AI” for matching products/preferences.
  • Evidence: Tier‑1 — https://www.threeprotocol.ai/
  • Why sufficient / why not (one line): The Tier‑1 source describes the purpose of the AI module (without metrics).
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demo specifically of the AI module was found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://www.threeprotocol.ai/
  • Why sufficient / why not (one line): The website lists modules but does not provide a reproducible demo of the AI part.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://www.threeprotocol.ai/
  • Why sufficient / why not (one line): Tier‑1 quality metrics for AI matching were not found per Tier‑1 sources.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): The tech description/architecture of the AI module was not found per Tier‑1 sources.
  • Evidence: Tier‑1 — https://www.threeprotocol.ai/
  • Why sufficient / why not (one line): There are product claims, but no technical details of the model.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: THREE token: 0xa059b81568fee88791de88232e838465826cf419
  • Evidence: Tier‑1 — https://etherscan.io/token/0xa059b81568fee88791de88232e838465826cf419
  • Why sufficient / why not (one line): The token contract is confirmed by the onchain 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 ERC‑20 token).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xa059b81568fee88791de88232e838465826cf419
  • Why sufficient / why not (one line): There are no Tier‑1 addresses/description of the onchain logic of the product modules.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not established per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 argument that onchain is critical for eCommerce features.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has an ERC‑20 token, THREE.
  • Evidence: Tier‑1 — https://etherscan.io/token/0xa059b81568fee88791de88232e838465826cf419
  • Why sufficient / why not (one line): The token contract is confirmed by the onchain explorer.
  • 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): Not established per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description that the token serves as payment for the service.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Not established per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of incentives/collateral/penalties.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Not established per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no Tier‑1 description of governance mechanics 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 is not established (no Tier‑1 role of the token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Without a Tier‑1 role of the token, we do not draw a conclusion.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.threeprotocol.ai/ Description of the ecosystem and claimed AI modules (including Neural Network AI).
Tier‑1 https://three-3.gitbook.io/litepaper Official docs/litepaper (context; details on AI/onchain require deeper examination).
Tier‑1 https://etherscan.io/token/0xa059b81568fee88791de88232e838465826cf419 The THREE ERC‑20 token contract (onchain fact).
Tier‑1 https://github.com/cyberscope-io/audits/blob/main/1-three/audit.pdf Public audit report (as a claimed security artifact).
Tier‑1 https://3pay.threeprotocol.ai Public web surface of one of the ecosystem’s services (3PAY).
Tier‑1 https://jobs3.io Public web surface of Jobs3 (claimed as an ecosystem platform).
Tier‑1 — No Tier‑1 source for claim “the token is mandatory for the service to operate” was found.

No comments to display

Back to top