Skip to main content

Envoy A.I

Envoy A.I — 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).

Envoy A.I — an AI/Other project on the Ethereum network, token (symbol: ENVOY).

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: the ENVOY ERC‑20 token on the Ethereum network.
  • Who it’s for: — (not confirmed by Tier‑1 sources).
  • Why onchain/token: onchain records the issuance/transfers of the token; the usefulness of the token/product is not confirmed by Tier‑1 sources.

How it works (very briefly)

  1. The user does: holds/transfers the ENVOY token (ERC‑20).
  2. The system does: executes the standard ERC‑20 logic of the contract on the Ethereum network.
  3. The user gets: onchain accounting of balances/transfers of the token.
  4. Where the blockchain is: the token contract and its events/transactions.
  5. Token role: not confirmed by Tier‑1 sources (see Evidence).

Quick links: AI thesis fit

Project passport

Field Value
Project name Envoy A.I
Also known as (aliases) Envoy AI, ENVOY
Logo (logo) ../assets/822_envoy-ai_logo.svg
Token symbol (ticker) ENVOY
Category AI/Other
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 0xcFf252a3299bE44Fa73402966F30a0159308B2Ad
Token model (token_type) —
Max supply 1,000,000,000 ENVOY
Issuance —
Tokenomics (tokenomics, brief) —
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) —
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary ai_score 0 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

Per the Tier‑1 onchain source, the ENVOY ERC‑20 token exists on the Ethereum network. The purpose of the product and the role of “AI” in the system are not confirmed by Tier‑1 sources.

Features/modules

  • — (not confirmed by Tier‑1 sources).

Typical scenarios

  • Scenario 1: a token holder transfers ENVOY → onchain records the transfer.

Getting started (wallet/network)

  • What you need: an EVM wallet.
  • Network/chain: Ethereum.
  • Fees: Ethereum network fees for transactions.

Architecture/tech (non‑AI)

  • Components: an ERC‑20 token contract.
  • Participant roles: token holders, dApp users (if they exist; not confirmed by Tier‑1 sources).
  • Where logic runs: onchain (Ethereum) for the token contract; the offchain part of the product is not established.
  • Dependencies: —.

Token/economics (expanded, no forecasts)

  • Token utility: not confirmed by Tier‑1 sources.
  • Issuance/burn: max total supply 1,000,000,000 ENVOY (Tier‑1, explorer).

Governance

  • Who makes decisions: — (not established).

Security and incidents

  • Audits: no Tier‑1 confirmation found.
  • Bug bounty: no Tier‑1 confirmation found.
  • Incidents: no Tier‑1 confirmation found.

Project status and timeline

  • Current status: not confirmed by Tier‑1 sources.

Ecosystem/integrations

  • Integrations: not confirmed by Tier‑1 sources.

AI component of the project

  • What is real AI here? No Tier‑1 confirmation of the AI component/product features was found.
  • What is truly onchain? There is an ENVOY token contract on the Ethereum network (Tier‑1, explorer).
  • Why is a token needed? Not confirmed by Tier‑1 sources.
  • Red flags (based on the information found): AI‑washing risk due to the absence of a verified Tier‑1 description of the product/AI features.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality low 0
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 partially present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): A Tier‑1 declaration of AI intentions is not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): without extracted Tier‑1 text, we conservatively set 0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): what exactly the AI does (if anything) is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): A Tier‑1 description of AI features is not confirmed by Tier‑1 sources.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): demos/examples of operation are not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no extracted Tier‑1 source with a demo/guide.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: not confirmed by Tier‑1 sources.
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there are no Tier‑1 metrics/benchmarks.
  • 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 part are not confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no extracted Tier‑1 description.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0xcFf252a3299bE44Fa73402966F30a0159308B2Ad
  • Evidence: Tier‑1 — https://etherscan.io/token/0xcFf252a3299bE44Fa73402966F30a0159308B2Ad
  • Why sufficient / why not (one line): the onchain fact of the token contract and network is recorded 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 confirmed by Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): the existence of useful onchain logic other than the token is not verified.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: not applicable/not established per Tier‑1.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 justification of onchain criticality.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, ENVOY (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xcFf252a3299bE44Fa73402966F30a0159308B2Ad
  • Why sufficient / why not (one line): the onchain fact of the token is established per the 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): it is not established that the token is used to pay for the service.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): A Tier‑1 description of the token utility is not confirmed by Tier‑1 sources.
  • Conflict note (if any): —

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

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

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the use of the token in governance is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 description.
  • 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 Tier‑1 justification.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://etherscan.io/token/0xcFf252a3299bE44Fa73402966F30a0159308B2Ad Onchain fact: the Envoy A.I (ENVOY) ERC‑20 token and the contract address on the Ethereum network; max total supply 1,000,000,000 ENVOY.
Tier‑1 — No Tier‑1 source for claim “what exactly the product/AI component does” was found.

No comments to display

Back to top