Trace Network

Trace Network (TRACE) — 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).

Trace Network — a Metaverse project on Ethereum, token (symbol: TRACE).

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 TRACE token on the Ethereum network, associated with the Trace Network project (per the onchain token page).
Who it’s for: users/community and participants of the ecosystem (details require Tier‑1 sources).
Why onchain/token: onchain records the token and transactions; the necessity of the token is not established per Tier‑1.

How it works (very briefly)

The user does: performs operations with the TRACE token or interacts with the project’s products (not established per Tier‑1).
The system does: executes ERC‑20 transfers and related onchain operations.
The user gets: confirmed transactions on Ethereum.
Where the blockchain is: the token and transactions — onchain; the project’s product features — outside the current sample.
Token role (if any): not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	Trace Network
Also known as (aliases)	TRACE
Logo (logo)	—
Token symbol (ticker)	TRACE
Category	Metaverse
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	0x9F7fC686CfD64aA5Ae15b351d03071e91533094b
Token model (token_type)	—
Max supply	100 000 000 TRACE
Issuance	fixed (max supply)
Tokenomics (tokenomics, brief)	Max total supply is given on the token page (Etherscan).
Governance	—
Admins/keys	—
Audit	—
Bug bounty	—
Team (team)	—
Funding (investors/funding)	—
AI component (ai_component)	—
Use‑case (use_case)	metaverse token
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 1
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://trace.network/
Docs	—
GitHub	—
Releases / Changelog	—
Whitepaper	https://trace.network/whitepaper
Roadmap	—
Security advisories	—
Explorer	https://etherscan.io/token/0x9F7fC686CfD64aA5Ae15b351d03071e91533094b
X	https://twitter.com/trace_network
Discord	—
Telegram	https://t.me/tracenetwork
Medium	https://medium.com/trace-network
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	—
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/trace-network-labs/

General project overview

Per Tier‑1 (the onchain token page), TRACE is an ERC‑20 token with a max total supply of 100 000 000. The main website trace.network opens with a domain‑for‑sale page, and the whitepaper PDF linked from the token page is unavailable per the available sources, so the product description is filled in conservatively.

Features/modules

TRACE ERC‑20 token: an onchain asset on Ethereum.
Ecosystem/products: not established per Tier‑1.

Typical scenarios

Scenario 1: a user interacts with the TRACE token → gets onchain transactions.

Getting started (wallet/network)

What you need: an EVM wallet for the ERC‑20 token.
Network/chain: Ethereum.
Fees: Ethereum fees for operations with the token.

Architecture/tech (non‑AI)

Components: the TRACE token (ERC‑20), the project’s links (website/social media/whitepaper — subject to availability).
Participant roles: token holders; users of the ecosystem’s products (not established per Tier‑1).
Where logic runs: onchain — the token and transactions; the product logic — outside the current sample.
Dependencies: Ethereum RPC for onchain operations; web infrastructure for the website/documents.

Token/economics (expanded, no forecasts)

Token utility: not established per Tier‑1.
Who pays fees: users pay Ethereum fees for operations with the token.
Issuance: fixed (max supply 100 000 000 TRACE; per the token page).
Security/incentive mechanisms: not established per Tier‑1.

Governance

Who makes decisions: not established per Tier‑1.
How protocol parameters change: —.

Security and incidents

Audits: —.
Bug bounty: —.
Incidents: —.
Threat model: risks of the token smart contract and risks of access to third‑party websites/documents.

Project status and timeline

Current status: mainnet (the token on Ethereum).
Key releases/milestones: —.
Roadmap: — (not established).

Ecosystem/integrations

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

AI component of the project

What is real AI here? No mentions/proof of an AI component were found per Tier‑1.
What is truly onchain? The TRACE ERC‑20 token.
Why is a token needed? Not established per Tier‑1.
Red flags (based on the information found): incomplete availability of Tier‑1 materials (whitepaper/website) in the current check.

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 present	1

Details

AI reality

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

AI_0 (decision): 0
Claim (one line): No Tier‑1 mention of AI intentions was found.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): Without a Tier‑1 source, AI_0 remains 0.
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 0
Claim (one line): AI features are not established per Tier‑1.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no Tier‑1 description of an AI component.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): No Tier‑1 demo surface for AI was found.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no Tier‑1 demo.
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): AI quality metrics are not identified.
Conflict note (if any): —

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

AI_4 (decision): 0
Claim (one line): No tech description of an AI component was found per Tier‑1.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There are no Tier‑1 technical artifacts about AI.
Conflict note (if any): —

Onchain necessity

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

OC_1 (decision): 1
Chain: Ethereum
Addresses/identifiers: TRACE contract: 0x9F7fC686CfD64aA5Ae15b351d03071e91533094b
Evidence: Tier‑1 — https://etherscan.io/token/0x9F7fC686CfD64aA5Ae15b351d03071e91533094b
Why sufficient / why not (one line): The token contract is observable 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 per Tier‑1 (other than the token).
Evidence: Tier‑1 — https://etherscan.io/token/0x9F7fC686CfD64aA5Ae15b351d03071e91533094b
Why sufficient / why not (one line): The token page confirms the token but does not describe protocol onchain logic.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

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

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): The project has a token, TRACE (ERC‑20).
Evidence: Tier‑1 — https://etherscan.io/token/0x9F7fC686CfD64aA5Ae15b351d03071e91533094b
Why sufficient / why not (one line): The token contract is observable in 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): Mandatory payment for the service with the token is not established per Tier‑1.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no available Tier‑1 source with a description of the token utility.
Conflict note (if any): —

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

TK_2 (decision): 0
Claim (one line): Token incentives are not established per Tier‑1.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no available Tier‑1 source.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): Governance use of the token is not established per Tier‑1.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no available Tier‑1 source.
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 per Tier‑1.
Evidence: Tier‑1 — —
Why sufficient / why not (one line): There is no available Tier‑1 source.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://etherscan.io/token/0x9F7fC686CfD64aA5Ae15b351d03071e91533094b	Onchain fact: the TRACE ERC‑20 token, max total supply 100 000 000.
Tier‑1	—	No Tier‑1 source for claim “the project’s AI component” was found.
Tier‑1	—	No Tier‑1 source for claim “why the TRACE token is needed (utility)” was found.