Skip to main content

CLAWNCH

CLAWNCH — 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).

CLAWNCH — an agent‑native token launchpad on Base (via Clanker / Uniswap v4): per Tier‑1 sources, agents can launch tokens “for free” and receive a share of trading fees; the $CLAWNCH token is described as a coordination layer for the agent economy.

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: token launch infrastructure on Base aimed at autonomous AI agents (token launch + fee accounting).
  • Who it’s for: AI agents and their operators/creators; developers integrating via API/SDK/MCP.
  • Why onchain/token: onchain is needed for token deployment and trading fee accrual; $CLAWNCH is claimed as a “coordination mechanism” (agent↔agent payments, coordination, commitment signal, collateral).

How it works (very briefly)

  1. The user (agent) does: publishes a !clawnch post on Moltbook / Moltx / 4claw with token parameters (name/symbol/wallet/description/image).
  2. The system does: validates the post and deploys the token on Base (via Clanker), records the launch and parameters.
  3. The user gets: a deployed token + the right to a share of trading fees (claimed: 80% to the agent, 20% to the platform).
  4. Where the blockchain is: Base (EVM, chain id 8453); the $CLAWNCH contract and auxiliary contracts are listed in the technical docs.
  5. Token role (if any): $CLAWNCH is described as a shared asset for coordination and economic alignment of agents’ interests.

Quick links: AI thesis fit

Project passport

Field Value
Project name CLAWNCH
Also known as (aliases) —
Logo (logo) ../assets/905_clawnch_logo.png
Token symbol (ticker) CLAWNCH
Category AI/Agents | Infra | DeFi
Primary chain (chain) Base
Type EVM
Network status mainnet
Consensus (consensus) PoS (Base; Ethereum L2)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0xa1F72459dfA10BAD200Ac160eCd78C6b77a747be
Token model (token_type) utility (coordination + payments + collateral)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) In Tier‑1 sources, $CLAWNCH is described as a coordination layer; a trading fee split of 80% to the agent / 20% to the platform is claimed for token launches.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) agent economy tooling
Use‑case (use_case) agent-native token launches on Base + launch fee economics
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 1 / onchain_score 3 / token_score 2 / evidence_score 2
Last verified 2026-02-11

General project overview

Per Tier‑1 sources, Clawnch is agent‑native token launch infrastructure on Base via Clanker/Uniswap v4: a launch is initiated by a post on supported agent social platforms (Moltbook / Moltx / 4claw), after which the system validates the parameters and deploys the token. The documentation also describes API/SDK/MCP tools, the fee distribution model, and a set of contracts/addresses.

AI component of the project

  • What is real AI here? in Tier‑1 sources, the product explicitly targets autonomous AI agents (agents‑only launchpad), but an AI model/inference as a protocol component is not described.
  • What is truly onchain? token deployment and fee accrual on the Base network; the $CLAWNCH contract and auxiliary contracts are listed in the technical docs.
  • Why is a token needed? $CLAWNCH is described as a coordination layer: a single asset for agent↔agent payments/coordination/commitment signals and collateral scenarios (Tier‑1, claimed).
  • Red flags (based on the information found): some wording is “visionary” in nature (“coordination layer”, “signal commitment”); without onchain artifacts/public parameters, this should not automatically raise implementation-dependent flags.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 1
  • Claim (one line): The project is positioned as an agent‑native platform (“agents launch tokens”, “agent economy”) in Tier‑1 documentation.
  • Evidence: Tier‑1 — https://clawn.ch/skill ; https://clawn.ch/docs.md
  • Why sufficient / why not (one line): Tier‑1 sources directly record AI orientation as the product’s intent/purpose.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): It is not established that the protocol has its own AI component (model/inference) as part of the product.
  • Evidence: Tier‑1 — https://clawn.ch/skill ; https://clawn.ch/docs.md
  • Why sufficient / why not (one line): Tier‑1 describes the “agents‑only” purpose and infrastructure, but does not record an AI model/metrics as a component.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): A demo specifically of AI functionality (in the sense of the product’s AI component) is not recorded.
  • Evidence: Tier‑1 — https://clawn.ch/skill
  • Why sufficient / why not (one line): The presence of a website/guides ≠ a demonstration of the product’s AI in operation.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://clawn.ch/docs ; Tier‑2 — https://www.coingecko.com/en/coins/clawnch (aggregator, for reference).
  • Evidence: Tier‑1 — https://clawn.ch/skill
  • Why sufficient / why not (one line): Quality metrics are not recorded per Tier‑1.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A technical description specifically of the AI part (model/versions/architecture) is not recorded.
  • Evidence: Tier‑1 — https://clawn.ch/docs.md
  • Why sufficient / why not (one line): Tier‑1 technical docs describe API/SDK/contracts, but not AI architecture.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Base
  • Addresses/identifiers: $CLAWNCH token contract 0xa1F72459dfA10BAD200Ac160eCd78C6b77a747be (Base)
  • Evidence: Tier‑1 — https://basescan.org/token/0xa1f72459dfa10bad200ac160ecd78c6b77a747be ; https://clawn.ch/docs.md
  • Why sufficient / why not (one line): The token contract address is confirmed by the explorer and listed in Tier‑1 technical docs.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: token deployment on Base, trading fee accrual and distribution (contracts and fee flows are described).
  • Evidence: Tier‑1 — https://clawn.ch/skill ; https://clawn.ch/docs.md
  • Why sufficient / why not (one line): Tier‑1 describes the onchain flow of launches and fees as part of the product, not “just a token”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without the blockchain, token launches and trustless fee accrual/payout cannot be implemented.
  • Evidence: Tier‑1 — https://clawn.ch/skill
  • Why sufficient / why not (one line): The main function of the product is onchain deployment and onchain fees.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, $CLAWNCH, on the Base network.
  • Evidence: Tier‑1 — https://basescan.org/token/0xa1f72459dfa10bad200ac160ecd78c6b77a747be ; https://clawn.ch/skill
  • Why sufficient / why not (one line): The Explorer page and Tier‑1 docs confirm the existence of the 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): $CLAWNCH is described as a shared asset for agent↔agent payments/settlement (bounties, services, tips).
  • Evidence: Tier‑1 — https://clawn.ch/skill
  • Why sufficient / why not (one line): Tier‑1 documentation explicitly describes the token’s payment use case (as a claimed role).
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): Tier‑1 technical docs describe “stake/commitment” and “burn‑to‑earn” mechanics (burn $CLAWNCH for an allocation at launch).
  • Evidence: Tier‑1 — https://clawn.ch/docs.md ; https://clawn.ch/docs
  • Why sufficient / why not (one line): Tier‑1 describes crypto‑economic mechanics involving $CLAWNCH (although some of them may be limited to specific scenarios).
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): The use of the token for governance is not established per Tier‑1.
  • Evidence: Tier‑1 — https://clawn.ch/skill
  • Why sufficient / why not (one line): A Tier‑1 description of the governance process is required.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): The token is described as the central mechanism for ecosystem coordination; its replacement “without loss of meaning” is not asserted per Tier‑1.
  • Evidence: Tier‑1 — https://clawn.ch/skill
  • Why sufficient / why not (one line): The Tier‑1 source positions the token as a coordination mechanism; there is no explicit proof of replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://clawn.ch/ Product positioning as an agent‑native token launchpad; publication of the $CLAWNCH token address.
Tier‑1 https://clawn.ch/skill Token launch documentation (post formats, rate limits) and a description of $CLAWNCH as a coordination layer (utility claims).
Tier‑1 https://clawn.ch/docs.md Technical documentation: stack/architecture, onchain contracts/addresses, API/SDK/MCP, fee flows.
Tier‑1 https://basescan.org/token/0xa1f72459dfa10bad200ac160ecd78c6b77a747be Onchain fact: the $CLAWNCH token contract on the Base network.
Tier‑2 https://coinmarketcap.com/currencies/clawnch/ Aggregator profile (context).
Tier‑2 https://www.coingecko.com/en/coins/clawnch Aggregator profile (context).

No comments to display

Back to top