Skip to main content

Project template

[Project Name] — a [category] project on [chain], token [ticker].

TL;DR (for readers who are not into AI)

  • What it is: a [protocol/app/network/marketplace] for [plain-purpose].
  • Who it’s for: [primary users: traders/users/developers/businesses].
  • Why onchain/token: [one sentence without AI terms: payments/access/incentives/security/accounting].

How it works (very briefly)

  1. The user does: [action].
  2. The system does: [what happens inside].
  3. The user gets: [result/benefit].
  4. Where the blockchain is: [what is onchain exactly: settlement/accounting/guarantees/ownership].
  5. Token role (if any): [why the token is needed; if none — “no token”].

Quick links: AI thesis fit

Project passport (short facts)

Field Value
Project name [ ]
Also known as (aliases) (synonyms/ticker/spellings) [ ]
Logo (logo) (link/file) [ ]
Ticker (or — if no token) [ ]
Category (1–3: DeFi / DEX / NFT / AI / Infra / GameFi / RWA / Meme / Other) [ ]
Website [ ]
Documentation [ ]
Repository [ ]
Whitepaper [ ]
Primary chain (chain) [ ]
Type (EVM / non‑EVM / Appchain) [ ]
Network status (mainnet / testnet / beta) [ ]
Consensus (consensus) (PoS/PoW/…) [ ]
Launch date (launch_date) (YYYY or date) [ ]
Project status (status) (active / in development / closed) [ ]
Explorer [ ]
Token (standard) (native / ERC‑20 / SPL / CW20 / none) [ ]
Token contract (address or —) [ ]
Token type (token_type) (utility / governance / revenue-share / …) [ ]
Max supply (max supply) [ ]
Circulating supply (circulating supply) [ ]
Issuance (fixed / inflationary / burn / unknown) [ ]
Tokenomics (tokenomics, brief) (1–2 facts) [ ]
Governance (DAO / multisig / company / unknown) [ ]
Audit (yes/no/unknown + link) [ ]
Bug bounty (yes/no/unknown + link) [ ]
Team (team) (brief/unknown) [ ]
Investors (investors) (brief/unknown) [ ]
AI component (ai_component) (3–10 words) [ ]
Use-case (use_case) (3–10 words) [ ]
w6index — AI thesis fit (AI thesis fit) (X/6 + level) [ ]
Last verified (YYYY‑MM‑DD) [ ]
Disclaimer not financial advice
Type Link
Website [ ]
Docs [ ]
GitHub [ ]
Whitepaper [ ]
Explorer [ ]
X [ ]
Discord [ ]
Telegram [ ]
Medium [ ]
CoinGecko [ ]
CoinMarketCap [ ]

General project overview

[In detail and in plain language (without repeating the TL;DR above): what the project is, what problem it solves, who it is for, and what form it takes (protocol/app/network).]

Features/modules

  • [Key product modules/components (as a list).]
  • [What matters most / what is unique for users.]

Typical use cases

  • Use case 1: [who does what → what outcome]
  • Use case 2: [who does what → what outcome]
  • Use case 3: [optional]

Getting started (wallet/network/steps)

  • What you need: [wallet/account/minimum requirements]
  • Network/chain: [which network, where to switch]
  • Steps: 1) [ ] 2) [ ] 3) [ ]
  • Fees: [which fees apply and where they occur]

Architecture/tech (non‑AI)

  • Components: [contracts/nodes/clients/indexers/backend, etc.]
  • Participant roles: [users/validators/providers/operators…]
  • Where logic runs: [L1/L2/appchain/offchain + what runs where]
  • Dependencies: [oracles/DA/bridges/RPC providers/storage, etc.]

Token/economics (expanded)

  • Token utility: [what people pay for / what they get]
  • Demand drivers: [why the token is needed in the system]
  • Who pays fees: [users/providers/third parties]
  • Where fees go: [validators/providers/treasury/burn]
  • Issuance/burn: [model + links/parameters]
  • Staking/slashing: [yes/no, terms, risks]
  • Distribution/vesting/unlocks: [who gets what / schedule / links]
  • Treasury: [who controls it / how it’s spent / links]

Governance

  • Who makes decisions: [DAO/team/foundation/multisig]
  • How protocol parameters change: [process/voting/upgrades]
  • Where decisions are discussed/made: [forum/repo/snapshot/links]
  • Keys/multisig: [signers/threshold/links]

Security and incidents

  • Audits: [who/when/links] (if many — put a table below)
  • Bug bounty: [yes/no, link]
  • Incidents: [hacks/outages/hard forks/postmortems]
  • Threat model: [main risks and security assumptions]

Project status and timeline

  • Current status: [mainnet/testnet/beta/…]
  • Key releases/milestones: [dates/versions]
  • Roadmap: [what’s being built now + link]

Ecosystem/integrations

  • Integrations: [DEX/CEX/wallets/bridges/tools]
  • Partners: [if there are confirmed ones]
  • Where it’s actually used: [integration examples/use cases + links]

Risks (clear and specific)

  • Technical risks: [ ]
  • Economic risks: [ ]
  • Governance risks: [ ]
  • Regulatory risks: [ ]
  • Centralization risks: [ ]

AI part of the project

  • What is real AI here? [1–2 sentences]
  • What is truly onchain? [1–2 sentences]
  • Why the token is needed? [1–2 sentences]

w6index component summary

Component Level Score
AI reality [low/medium/high] [0–3]
Onchain necessity [low/medium/high] [0–3]
Token necessity [no token/low/medium/high] [0–3]
Evidence [Tier‑1 present/absent] [0–3]

Important: this is an assessment of AI thesis fit and evidential support. Not financial advice.
We do not assess price/returns/timing and do not give buy/sell/hold recommendations.

Details

AI reality

AI_1 — what the AI does (1/0)

  • AI_1:AI_1 (decision): [1/0/1]unknown]
  • Fact:Claim (one line): [what the AI actually does]
Evidence: Tier‑[1/2] — [link], [link] Why sufficient / why not (one line): [why this is enough for 1, or why 0/unknown] Conflict note (if any): [ ] Basis (Tier‑1/2): [link]

AI_2 — demos/examples (1/0)

  • AI_2:AI_2 (decision): [1/0/1]unknown]
  • Fact:Claim (one line): [what demo/example exists and what it shows]
Evidence: Tier‑[1/2] — [link], [link] Why sufficient / why not (one line): [why this is enough for 1, or why 0/unknown] Conflict note (if any): [ ] Basis (Tier‑1/2): [link]

AI_3 — metrics/quality (1/0)

  • AI_3:AI_3 (decision): [1/0/1]unknown]
  • Metrics: [ ]
  • Context (version/date/how measured): [ ]
  • BasisEvidence: Tier‑[1/2] — [link], [link]
Why sufficient / why not (Tier‑1/2)one line): [link]why metrics are valid/sufficient, or why 0/unknown] Conflict note (if any): [ ]

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

  • AI_4:AI_4 (decision): [1/0/1]unknown]
  • Fact:Claim (one line): [what is documented/described]
Evidence: Tier‑[1/2] — [link], [link] Why sufficient / why not (one line): [why this is enough for 1, or why 0/unknown] Conflict note (if any): [ ] Basis (Tier‑1/2): [link]

Onchain necessity

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

  • OC_1:OC_1 (decision): [1/0/1]unknown]
  • Chain: [ ]
  • Addresses/identifiers: [ ]
  • BasisEvidence: Tier‑[1/2] — [link], [link]
Why sufficient / why not (Tier‑1/2)one line): [link]why this is enough for 1, or why 0/unknown] Conflict note (if any): [ ]

OC_2 — onchain beyond just a token (1/0)

  • OC_2:OC_2 (decision): [1/0/1]unknown]
  • What useful logic is onchain: [ ]
  • BasisEvidence: Tier‑[1/2] — [link], [link]
Why sufficient / why not (Tier‑1/2)one line): [link]why this is enough for 1, or why 0/unknown] Conflict note (if any): [ ]

OC_3 — onchain is critical (1/0)

  • OC_3:OC_3 (decision): [1/0/1]unknown]
  • “Replace the blockchain” test: what breaks without onchain: [ ]
  • BasisEvidence: Tier‑[1/2] — [link], [link]
Why sufficient / why not (Tier‑1/2)one line): [link]why the test is proven, or why 0/unknown] Conflict note (if any): [ ]

Token necessity

TK_0 — no token (1/0)

  • TK_0:TK_0 (decision): [1/0/1]unknown]
Claim (one line): [the project has no token] Evidence: Tier‑[1/2] — [link], [link] Why sufficient / why not (one line): [why this is enough, or why unknown] Conflict note (if any): [ ]

TK_1..TK_4 (1/0)

TK_1 — paying for the service (1/0)

  • TK_1 (paying for the service)decision): [1/0/1]unknown]
Claim (one line): [what users pay for with the token] Evidence: Tier‑[1/2] — basis:[link], [link] TK_2Why sufficient / why not (incentives/collateral/penalties)one line): [why this is proven, or why 0/1]unknown] Conflict note (if any): [ ]

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

    TK_2 (decision): [1/0/unknown] Claim (one line): [which incentives/collateral/penalties exist and why] Evidence: Tier‑[1/2] — [link], [link] TK_3Why sufficient / why not (governance)one line): [why this is proven, or why 0/1]unknown] Conflict note (if any): [ ]

    TK_3 — basis:governance (1/0)

      TK_3 (decision): [1/0/unknown] Claim (one line): [how the token is used for governance] Evidence: Tier‑[1/2] — [link], [link] Why sufficient / why not (one line): [why this is proven, or why 0/unknown] Conflict note (if any): [ ]

      TK_4 (— token is replaceable)replaceable (1/0)

        TK_4 (decision): [1/0/1]unknown] Claim (one line): [why the token can/cannot be replaced] Evidence: Tier‑[1/2] — basis:[link], [link] Why sufficient / why not (one line): [why this conclusion is supported, or why unknown] Conflict note (if any): [ ]

        Evidence (table)

        Tier Source What it proves
        Tier‑1 [link] [ ]
        Tier‑2 [link] [ ]
        Tier‑3 [link] [ ]
        Back to top