Skip to main content

KiboShib

KiboShib (KIBSHI) — 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).

KiboShib — a meme token with the narrative of “the first AI‑generated memecoin”; token: KIBSHI (ERC‑20).

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 meme asset/community around the KIBSHI token.
  • Who it’s for: traders/the memecoin community.
  • Why onchain/token: the blockchain — basic issuance/transfers/DEX trading; no separate useful onchain logic beyond the token is claimed.

How it works (very briefly)

  1. The user does: buys/holds/transfers the KIBSHI token or participates in community activities.
  2. The system does: the token contract processes transfers; liquidity/trading takes place on DEXes/exchanges.
  3. The user gets: exposure to the meme narrative and participation in the community.
  4. Where the blockchain is: issuance and accounting of token ownership — onchain (Ethereum).
  5. Token role (if any): the token is the product; utility beyond a “meme asset” is not confirmed.

Quick links: AI thesis fit

Project passport

Field Value
Project name KiboShib
Also known as (aliases) KIBSHI
Logo (logo) ../assets/153_kiboshib_logo.png
Token symbol (ticker) KIBSHI
Category Meme
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) 2022-12 (per the website, “Date of birth”)
Project status (status) active
Token (standard) ERC-20
Token contract 0x02e7f808990638e9e67e1f00313037ede2362361
Token model (token_type) —
Max supply 1,000,000,000,000 (1 trillion; per the website “1 Trillion Tokens”, better to re‑check via the explorer)
Issuance fixed (per the website: “Fixed supply forever”)
Tokenomics (tokenomics, brief) Meme token; the website claims a liquidity lock and large transfers to “Vitalik’s address” (careful onchain verification is needed).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) none (narrative only)
Use‑case (use_case) meme token
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 1 / 0 / 2
Last verified 2026-02-11

General project overview

KiboShib (KIBSHI) is a meme token that builds its narrative on the claim that the idea/naming/visual elements were allegedly “generated by AI” (the website gives ChatGPT/DALL‑E examples). In essence, the product is the token itself and the community activity around it (memes, social channels, listings, etc.).

Important: the use of AI as an “origin story” is not an AI component of the product in the DecAIHub sense (there is no proven AI module that computes/predicts/controls anything in the protocol).

Features/modules

  • KIBSHI ERC‑20 token on Ethereum.
  • Narrative/content about an “AI‑generated memecoin” (website/social media).
  • Liquidity/trading (DEXes/exchanges — per the project’s links).

Typical scenarios

  • Scenario 1: a user buys/sells KIBSHI on a DEX/CEX → gets meme exposure/liquidity.
  • Scenario 2: a community member interacts with the project’s social channels/activities → supports the narrative/content.
  • Scenario 3: a holder transfers tokens between addresses/wallets (standard ERC‑20).

Getting started (wallet/network)

  • What you need: an EVM wallet (e.g., MetaMask) and ETH for fees; access to a DEX/CEX as needed.
  • Network/chain: Ethereum mainnet.
  • Fees: Ethereum gas for ERC‑20 purchases/sales/transfers.

Architecture/tech (non‑AI)

  • Components: the ERC‑20 token contract + standard Ethereum infrastructure (RPC/explorers/DEXes).
  • Participant roles: token holders, LPs/traders, the community.
  • Where logic runs: onchain — ERC‑20 transfers; everything else (website/social media) — offchain.
  • Dependencies: Ethereum mainnet, DEXes/exchanges, RPC providers, explorers.

Token/economics (expanded, no forecasts)

  • Token utility: onchain utility is not confirmed (beyond the standard function of a meme token: ownership/transfer/trading).
  • Protocol necessity drivers: not applicable (no protocol necessity of the token, beyond its existence, is confirmed).
  • Who pays fees: Ethereum users pay gas in ETH for onchain operations.
  • Where fees go: to Ethereum validators (gas), not to the project’s treasury.
  • Issuance/burn: the website claims a fixed supply; the onchain parameters are better confirmed via the explorer.
  • Security/incentive mechanisms: not claimed (no Tier‑1 staking/slashing/protocol incentives found).
  • Distribution and token issuance schedule: not established (no Tier‑1 tokenomics/vesting found).
  • Treasury: not established (no Tier‑1 treasury addresses/rules found).

Governance

  • Who makes decisions: not established (looks like a community‑driven/team format; onchain governance is not confirmed).
  • How protocol parameters change: — (no protocol parameters/update process described).
  • Where decisions are discussed/made: the project’s social media (see links_*).
  • Keys/multisig: — (no Tier‑1 information on keys/multisig found).

Security and incidents

  • Audits: — (no Tier‑1 audit reports found).
  • Bug bounty: — (no Tier‑1 bug bounty found).
  • Incidents: — (no Tier‑1 postmortems/incidents found).
  • Threat model: standard ERC‑20/DEX risks (phishing, fake contracts/links, liquidity/volatility risk).

Project status and timeline

  • Current status: active (website/social media and a token on Ethereum).
  • Key releases/milestones: — (no Tier‑1 release log/milestones found).
  • Roadmap: see links_* → Roadmap (an image).

Ecosystem/integrations

  • Integrations: not established (a Tier‑1 list of integrations/exchanges was not compiled within this card).
  • Partners: — (no Tier‑1 confirmed list of partners found).
  • Where it’s actually used: trading/community activities around the token.

AI component of the project

  • What is real AI here? There is no real AI product/module; “AI” is the origin of the idea/content (a marketing narrative).
  • What is truly onchain? Issuance and accounting of ownership of the KIBSHI token on Ethereum.
  • Why is a token needed? The token is the main object (a meme asset); no utility/protocol necessity beyond trading/transfers is confirmed.
  • Red flags (based on the information found): AI‑washing high (AI is used as a brand label without AI functionality); what to double‑check: the website’s claims about supply/locks/transactions — only via the explorer.

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 partially present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 roadmap/intent to introduce AI features was found (AI is used as an origin narrative).
  • Evidence: Tier‑1 — https://kiboshib.com
  • Why sufficient / why not (one line): On the website AI is mentioned as an “AI‑generated coin/memes”, not as a product plan with an AI module.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): No AI features in the product/protocol are described.
  • Evidence: Tier‑1 — https://kiboshib.com
  • Why sufficient / why not (one line): The mentions of AI relate to branding/content, not to a computational subsystem.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): There is no demo of an AI system in operation; there are only examples of “AI‑generated” content.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Content examples are not a demo of an AI protocol.
  • 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 absent, since an AI subsystem is not confirmed.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): A technical description of an AI model/architecture is absent.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no AI component that would require a technical description.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum (mainnet)
  • Addresses/identifiers: KIBSHI ERC‑20 0x02e7f808990638e9e67e1f00313037ede2362361
  • Evidence: Tier‑1 — https://etherscan.io/token/0x02e7f808990638e9e67e1f00313037ede2362361
  • Why sufficient / why not (one line): The explorer confirms the token contract.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: Not confirmed (beyond the standard ERC‑20 token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no description of protocol onchain logic (access/accounting/rules/DAO).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: beyond ownership/trading of the token, no product properties “only thanks to onchain” are claimed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): This is a meme token without a protocol necessity for onchain logic.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, KIBSHI (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0x02e7f808990638e9e67e1f00313037ede2362361
  • Why sufficient / why not (one line): Onchain confirmation of the token.
  • 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): Payment for services with the token is not confirmed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Utility beyond trading is not described.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/slashing are not confirmed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no protocol description of incentives.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance via the token is not confirmed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no description of a DAO/voting.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): The token is a meme asset; functionally replaceable (no confirmed protocol necessity).
  • Evidence: Tier‑1 — https://kiboshib.com
  • Why sufficient / why not (one line): Utility is not confirmed; what remains is “narrative/asset”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://kiboshib.com The project’s official narrative and the claimed parameters (supply/locks) as claims.
Tier‑1 https://etherscan.io/token/0x02e7f808990638e9e67e1f00313037ede2362361 Onchain confirmation of the KIBSHI token (contract on Ethereum).
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top