Skip to main content

clawd.atg.eth

clawd.atg.eth — 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).

clawd.atg.eth — a project/token linked to the onchain game “ClawdFomo3D” (king‑of‑the‑hill) per the Tier‑1 description in the GitHub repository; an AI component as part of the product is not established.

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: an onchain game in the “last buyer wins” format (purchasing “keys” with a timer).
  • Who it’s for: users who participate in the onchain game and interact with the contract/token.
  • Why onchain/token: onchain is needed for transparent round state and enforcement of the rules; the $CLAWD token is used to purchase “keys” and for distribution/burn under the game rules.

How it works (very briefly)

  1. The user does: purchases “keys” with $CLAWD tokens.
  2. The system does: each purchase resets the round timer; when the round ends, the last buyer receives part of the “pot” under the distribution rules.
  3. The user gets: either winnings at the end of the round, or dividends (if provided for by the rules), or nothing (if not the last buyer).
  4. Where the blockchain is: the $CLAWD token is deployed on Base; the game is described as onchain contracts/functions (purchases/timer/dividends).
  5. Token role (if any): the $CLAWD token is a means of payment for “keys” and part of the mechanics (burn/dividends/dev fee) described in the Tier‑1 README.

Quick links: AI thesis fit

Project passport

Field Value
Project name clawd.atg.eth
Also known as (aliases) CLAWD, ClawdFomo3D
Logo (logo) ../assets/907_clawd-atg-eth_logo.png
Token symbol (ticker) CLAWD
Category Gaming | Meme
Primary chain (chain) Base
Type EVM
Network status mainnet
Consensus (consensus) PoS (Base; Ethereum L2)
Launch date (launch_date) —
Project status (status) in development
Token (standard) ERC-20
Token contract 0x9f86db9fc6f7c9408e8fda3ff8ce4e78ac7a6b07
Token model (token_type) —
Max supply —
Issuance —
Tokenomics (tokenomics, brief) The README describes the rules for distributing the “pot” (portions go to the winner/burn/dividends/dev fee) and the key price formula.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) on-chain game (king-of-the-hill)
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 1 / evidence_score 2
Last verified 2026-02-11

General project overview

Per the Tier‑1 README in the repository, the project describes the game “ClawdFomo3D” in the king‑of‑the‑hill genre: players purchase “keys” with the $CLAWD token; each purchase resets the timer, and when it ends, the last buyer receives part of the “pot” under the distribution rules (including burn and dividends).

An important status clarification: the Tier‑1 README states that the game/contracts are “NOT YET DEPLOYED” (the stage of collecting feedback on the contracts). This reduces confidence in the actual availability of the product.

AI component of the project

  • What is real AI here? It is not established that the product has an AI component; the Tier‑1 README contains the claim “built by an AI agent”, but this does not prove AI functionality for the user.
  • What is truly onchain? the $CLAWD token is deployed on Base; the game logic is claimed as onchain contracts/functions.
  • Why is a token needed? the $CLAWD token is used to purchase “keys” and for the described economic rules (burn/dividends/dev fee).
  • Red flags (based on the information found): “AI” may be present only in the development narrative; without Tier‑1 artifacts about the AI feature, AI flags cannot be raised.

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 1
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): Tier‑1 intentions regarding AI as part of the product are not established.
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): Without a Tier‑1 source, intent cannot be confirmed.
  • 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 product has an AI component (model/inference) for the user.
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): Tier‑1 artifacts (docs/code/demo) describing the AI feature are required.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): A demo of AI functionality is not recorded per Tier‑1.
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): Without a Tier‑1 link to a demo, AI_2 remains 0.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • 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 of the AI part (if it exists) is not recorded per Tier‑1.
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): Tier‑1 docs/repo with an architecture or description are required.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Base
  • Addresses/identifiers: the $CLAWD token (ERC‑20): 0x9f86db9fc6f7c9408e8fda3ff8ce4e78ac7a6b07
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): The Tier‑1 README records the network and the token contract address.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: —
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): Deployed game contract addresses beyond the token are not recorded per Tier‑1.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: —
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): Onchain criticality requires formal justification and sources.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, $CLAWD.
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): The Tier‑1 README describes the token and the contract address.
  • 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): “Keys” are purchased with the $CLAWD token.
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): The Tier‑1 README describes payment with the token.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): The README describes burn and distribution of the “pot” (including dividends to key holders and the dev fee).
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): This describes incentives/value distribution mechanics involving the token.
  • 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://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): “1” requires a described governance process.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): The token appears replaceable: the game mechanics could work with another asset.
  • Evidence: Tier‑1 — https://github.com/clawdbotatg/clawdfomo3d
  • Why sufficient / why not (one line): There is no argument in Tier‑1 that this specific token is critical and irreplaceable.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://github.com/clawdbotatg/clawdfomo3d Description of the game mechanics (keys + timer), distribution of the “pot” and the $CLAWD token address on Base.
Tier‑1 https://basescan.org/token/0x9f86db9fc6f7c9408e8fda3ff8ce4e78ac7a6b07 The token’s onchain page in the explorer (Tier‑1).
Tier‑1 — No Tier‑1 sources confirming the product’s AI component were found.
Tier‑2 https://coinmarketcap.com/currencies/clawd-atg-eth/ Aggregator profile (context).
Tier‑2 https://www.coingecko.com/en/coins/clawd-atg-eth Aggregator profile (context).

No comments to display

Back to top