Skip to main content

tokenbot / Clanker

tokenbot / Clanker (CLANKER) — 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).

Clanker — an Infra | Meme project on Base: a set of smart contracts and an SDK for deploying ERC‑20 tokens with automatic creation of liquidity pools and a creator rewards model (part of the LP fees goes to the token creator). Token: CLANKER (ERC‑20, Base; Tier‑1 docs + explorer).

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: a set of smart contracts that allows quickly issuing ERC‑20 tokens on Base and automatically creating a trading pool/LP positions.
  • Who it’s for: users and developers who want to launch tokens via clanker.world, the Farcaster bot or the SDK.
  • Why onchain/token: onchain is needed for trusted token deployment and accounting of LP fees/creator rewards; the CLANKER token as a separate utility is not disclosed in the Tier‑1 docs (there is the onchain fact of the token and its supply).

How it works (very briefly)

  1. The user does: initiates a token deployment (via clanker.world / Farcaster / the SDK / a direct contract call).
  2. The system does: deploys the ERC‑20, creates a liquidity pool (Uniswap integration) and the “initial LP” on which fees are collected.
  3. The user gets: a token, a basic market and the ability to collect creator rewards (part of the initial LP fees).
  4. Where the blockchain is: deployment of the token/pools, LP positions and fee collection — onchain (Base and other networks per the deployment list).
  5. Token role: CLANKER is the project’s separate ERC‑20 token (the onchain fact is confirmed), but the necessity of the token for the protocol’s operation is not explicitly proven in the Tier‑1 docs.

Quick links: AI thesis fit

Project passport

Field Value
Project name tokenbot / Clanker
Also known as (aliases) Clanker | CLANKER
Logo (logo) ../assets/64_tokenbot-2_logo.png
Token symbol (ticker) CLANKER
Category Infra | Meme
Primary chain (chain) Base
Type EVM
Network status mainnet
Consensus (consensus) L2 (Optimistic Rollup, Base on Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x1bc0c42215582d5a085795f4badbac3ff36d1bcb
Token model (token_type) —
Max supply 1,000,000
Issuance fixed cap
Tokenomics (tokenomics, brief) max total supply 1,000,000 (BaseScan); the token’s utility is not explicitly described in the Tier‑1 docs.
Governance —
Admins/keys —
Audit yes
Bug bounty —
Team (team) Jack Dishman; Lily Johnson; Carter Appleton; Michael (m00npapi.eth) (Tier‑1 docs)
Funding (investors/funding) —
AI component (ai_component) —
Use‑case (use_case) token deployment + creator rewards via LP fees
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 3 / token_score 0 / evidence_score 2
Last verified 2026-02-10

General project overview

Clanker is “token deployment” infrastructure: a set of smart contracts and interfaces that make launching an ERC‑20 token look like a “one‑click” operation and immediately create the trading infrastructure (liquidity/pools). The key motive per the Tier‑1 docs is creator rewards: the token creator receives a share of the fees (LP fees) from the “initial LP” on a standard deployment.

The project supports several deployment paths: by mentioning @clanker on Farcaster, via the clanker.world frontend/mini‑app, via the SDK and via direct interaction with the core contracts.

Features/modules

  • Token deployment flows: Farcaster bot / clanker.world / SDK / direct contracts (Tier‑1 docs).
  • Automatic liquidity creation: creation of the initial LP and fee collection (Tier‑1 docs).
  • Creator rewards: the accrual model and claiming via the token’s admin page on clanker.world (Tier‑1 docs).
  • SDK: “one‑click deployment”, metadata/social links, reward distributions, mini‑app examples (Tier‑1 docs).
  • Deployed contracts registry: a list of contracts by version and network (Tier‑1 docs).

Typical scenarios

  • Scenario 1 (token creator): deploys a token via clanker.world → receives the initial LP → collects creator rewards based on trading volume.
  • Scenario 2 (developer): integrates the Clanker SDK into their application/mini‑app → gives users a token deployment interface.
  • Scenario 3 (trader/LP): trades tokens created via Clanker → fees go partly to LPs, partly to the protocol/creator (per the rules).

Getting started (wallet/network)

  • What you need: an EVM wallet (Base) and funds for gas.
  • Network/chain: Base mainnet (see the contracts in links_* and in the Tier‑1 “Deployed Contracts”).
  • Fees: gas on Base + LP pool fees (Uniswap infrastructure); the protocol fee is described as 20% of the LP fees at the pool level (Tier‑1 docs).

Architecture/tech (non‑AI)

  • Components: core contracts (Clanker + hooks/lockers/vaults), the clanker.world frontend, the SDK, Uniswap integrations and LP positions (Tier‑1 docs).
  • Participant roles: token creators, traders/LPs, interface developers, the protocol (owner of the fee parameters).
  • Where logic runs: onchain — token deployment, creation of pools/LP positions and accrual/collection of fees; offchain — UI/SDK and integrations.
  • Dependencies: Base (L2), Uniswap infrastructure, wallets/Farcaster mini‑apps.

Token/economics (expanded, no forecasts)

  • Token utility: per the available Tier‑1 sources, the utility of CLANKER as a mandatory “protocol currency” is not confirmed (there is the onchain fact of the token).
  • Protocol necessity drivers: the protocol economy is described via LP fees and creator rewards; it operates at the level of contracts and pool fees (Tier‑1 docs).
  • Who pays fees: traders pay fees in the pools; the deployer/creator pays gas for the deployment.
  • Where fees go: part of the fees goes to LPs/the creator (creator rewards), part to the protocol (the Tier‑1 docs specify a 20% protocol fee from the LP fees).
  • Issuance/burn: max total supply of CLANKER = 1,000,000 (BaseScan).
  • Security/incentive mechanisms: incentives for the token creator via creator rewards; protocol parameters and contract addresses are recorded onchain.
  • Distribution and token issuance schedule: — (no description of vesting/allocations for the CLANKER token was found within Tier‑1).
  • Treasury: —.

Governance

  • Who makes decisions: — (there is no explicit DAO/snapshot in Tier‑1).
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: present (Clanker audits by version; Tier‑1).
  • Bug bounty: — (Tier‑1 not found).
  • Incidents: — (Tier‑1 not found).
  • Threat model: smart contract risks (deployment/pools/lockers), risks of fee settings/admin parameters in the deployers, risks of Uniswap integrations and MEV.

Project status and timeline

  • Current status: mainnet (Base) + there is contract versioning (v4.1.0/v4.0.0 and others) in the Tier‑1 deployment registry.
  • Key releases/milestones: SDK releases and the changelog in the documentation; a list of contract deployments by version (Tier‑1).
  • Roadmap: — (there is no Tier‑1 roadmap page in links_*).

Ecosystem/integrations

  • Integrations: Farcaster (bot), the clanker.world frontend/mini‑app, the SDK (clanker-sdk), Uniswap pools and LP (Tier‑1 docs).
  • Partners: —.
  • Where it’s actually used: token deployments via clanker.world + token admin pages for claiming creator rewards (Tier‑1 docs).

AI component of the project

  • What is real AI here? Per Tier‑1 sources, an AI component/AI protocol is not confirmed: this is onchain infrastructure for deploying tokens and markets.
  • What is truly onchain? token deployment/LP pools and collection of fees/creator rewards; there is a list of deployed contracts by version and network (Tier‑1 docs).
  • Why is a token needed? at a minimum, the ERC‑20 CLANKER token exists on Base; however, the Tier‑1 docs do not show that it is mandatory for the protocol’s operation (hence token necessity is low).
  • Red flags (based on the information found): possible token‑washing (the token exists, but its utility is not disclosed in Tier‑1); it is important to re‑check which contracts exactly have been audited and which version they belong to.

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 high 3
Token necessity low 0
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 AI intent/roadmap is claimed: the product is described as onchain deployment of tokens and markets.
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation
  • Why sufficient / why not (one line): the Tier‑1 description contains no AI functions/roadmap → AI_0=0.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): AI functions/models/agents are not described in Tier‑1.
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation
  • Why sufficient / why not (one line): the product is DeFi/infra contracts for token deployment → AI_1=0.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): there is a demo/quickstart for deploying tokens via the SDK/mini‑app, but it is not an AI case (hence AI_2=0).
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation/sdk/quick-start
  • Why sufficient / why not (one line): the demo relates to the token deployment infrastructure, not to AI.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation
  • Why sufficient / why not (one line): AI metrics are absent because no AI component is claimed.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): there is a technical description for the smart contracts/SDK, but not for an AI module.
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation/references/deployed-contracts
  • Why sufficient / why not (one line): there is no AI architecture → AI_4=0.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Base (8453).
  • Addresses/identifiers: the CLANKER token 0x1bc0c42215582d5a085795f4badbac3ff36d1bcb; core contracts (e.g. Clanker v4.0.0: 0xE85A59c628F7d27878ACeB4bf3b35733630083a9) and others per the deployment registry.
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation/references/deployed-contracts , https://basescan.org/token/0x1bc0c42215582d5a085795f4badbac3ff36d1bcb
  • Why sufficient / why not (one line): the Tier‑1 docs provide a list of contracts by network/version, and the explorer confirms the token.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: ERC‑20 deployment and creation of the initial LP/fee collection; claiming creator rewards (the token’s admin page).
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation , https://clanker.gitbook.io/clanker-documentation/general/creator-rewards-and-fees
  • Why sufficient / why not (one line): Tier‑1 describes an onchain model of token deployment + creator rewards on fees.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain contracts it is impossible to deploy tokens/pools in a trusted way and to distribute LP fees/creator rewards according to the protocol rules.
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation/general/creator-rewards-and-fees
  • Why sufficient / why not (one line): the product’s core value is onchain tokens/markets and onchain collection/distribution of fees.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the CLANKER token exists (ERC‑20 on Base).
  • Evidence: Tier‑1 — https://basescan.org/token/0x1bc0c42215582d5a085795f4badbac3ff36d1bcb
  • Why sufficient / why not (one line): the explorer records the name/symbol/supply 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): 0
  • Claim (one line): it is not confirmed per Tier‑1 that the protocol requires payment specifically in CLANKER (gas on Base is paid in ETH).
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation
  • Why sufficient / why not (one line): without an explicit “pay in CLANKER”, TK_1=0.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): incentives are described as creator rewards from LP fees, but this is not proof of staking/collateral specifically in CLANKER.
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation/general/creator-rewards-and-fees
  • Why sufficient / why not (one line): there is no token collateral/slashing/staking of CLANKER in Tier‑1.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): governance via CLANKER is not confirmed in Tier‑1.
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation
  • Why sufficient / why not (one line): without a snapshot/DAO/description of voting, TK_3=0.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): per the Tier‑1 description, the protocol logic (deployment/fees/creator rewards) does not depend on the separate CLANKER utility token.
  • Evidence: Tier‑1 — https://clanker.gitbook.io/clanker-documentation/general/creator-rewards-and-fees
  • Why sufficient / why not (one line): the main processes rely on onchain contracts and LP fees, not on payments in the token.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://clanker.gitbook.io/clanker-documentation that this is a token deployment protocol (contracts + deployment methods + roles).
Tier‑1 https://clanker.gitbook.io/clanker-documentation/general/creator-rewards-and-fees how creator rewards and protocol fees are structured (20% of the LP fees).
Tier‑1 https://clanker.gitbook.io/clanker-documentation/references/deployed-contracts core contract addresses by version/network (Base 8453 and others).
Tier‑1 https://clanker.gitbook.io/clanker-documentation/sdk/quick-start a reproducible quickstart/SDK (token deployment, mini‑app example).
Tier‑1 https://clanker.gitbook.io/clanker-documentation/references/audits the existence of audits by version (including the Macro PDF).
Tier‑1 https://basescan.org/token/0x1bc0c42215582d5a085795f4badbac3ff36d1bcb the onchain fact of the tokenbot (CLANKER) token, max supply 1,000,000.
Tier‑1 https://github.com/clanker-devco/clanker-sdk/security/advisories Security advisories: there are no published advisories (status).

No comments to display

Back to top