Skip to main content

Bad Idea AI

Bad Idea AI (BAD) — 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).

Bad Idea AI — an AI/Assistants / Meme project: a “decentralized experiment” based on the ERC‑20 token BAD and a set of AI tools, including the Telegram bot S.A.R.A.H. (described on the website and in GitHub). The BAD token is confirmed onchain on the Ethereum network.

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 experiment “AI + DAO + token” with an AI assistant/bot in Telegram (S.A.R.A.H.).
  • Who it’s for: the community/token holders and users of the bot.
  • Why onchain/token: onchain is needed for the BAD token as the base asset of the ecosystem; a specific irreplaceable protocol utility of the token is not confirmed in the extracted Tier‑1.
  • What you can actually touch (Tier‑1): the S.A.R.A.H. Telegram bot (official link from the project website).

How it works (very briefly)

  1. The user does: interacts with the BAD token and/or talks to the S.A.R.A.H. Telegram bot (website).
  2. The system does: provides the bot’s answers/modes/integrations (described in GitHub) and supports the “ecosystem” narrative of AI+DAO (whitepaper/pitchdeck).
  3. The user gets: the onchain asset BAD and access to the bot/communications (website/GitHub).
  4. Where the blockchain is: the BAD token exists as an ERC‑20 on Ethereum (Etherscan).
  5. Token role (if any): in the extracted Tier‑1 the token is described as “powering the ecosystem”/an experiment; no onchain mechanics of access/payment/staking were extracted.

Quick links: AI thesis fit

Project passport

Field Value
Project name Bad Idea AI
Also known as (aliases) BAD IDEA AI, BAD, $BAD, S.A.R.A.H., SARAH
Logo (logo) —
Token symbol (ticker) BAD
Category AI/Assistants | Meme
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x32b86b99441480a7e5bd3a26c124ec2373e3f015
Token model (token_type) utility (ecosystem token, claim)
Max supply CONFLICT: 829,489,818,339,147.999999981060321473 (Etherscan “Max Total Supply”) / 831,041,059,897,327.3110117 (GitHub “Initial Supply”)
Issuance burnable (ERC‑20 burnable; Etherscan source)
Tokenomics (tokenomics, brief) experimental meme token; distribution/vesting parameters not extracted (Tier‑1)
Governance — (in the extracted Tier‑1 there is no description of a real DAO process)
Admins/keys —
Audit — (links_* contains a link to Certik as an external service)
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) Telegram bot S.A.R.A.H.
Use‑case (use_case) AI assistant for token community
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 3 / 1 / 0 / 3
Last verified 2026-02-11

General project overview

Bad Idea AI is an experiment that combines the BAD meme token (ERC‑20) and “AI‑driven tools” around a community. The website highlights the Telegram bot S.A.R.A.H. (“Talk to S.A.R.A.H.”), which promises to help navigate the topic of crypto/blockchain. In the whitepaper/pitchdeck the project describes the “AI + DAO” idea and an experimental approach without a fixed roadmap.

Features/modules

  • BAD token (ERC‑20): the onchain asset of the ecosystem (Etherscan).
  • S.A.R.A.H. Telegram bot: a “conversational assistant” with modes and multilingual support (website + GitHub).
  • Knowledgebase/integrations: the GitHub README claims a “decentralized knowledgebase” and cross‑platform integrations (GitHub).
  • Project documents: whitepaper + pitchdeck (website/GitBook).

Typical scenarios

  • Scenario 1: a user interacts with BAD → tracks the token in the explorer (Etherscan).
  • Scenario 2: a user opens S.A.R.A.H. in Telegram → gets answers/hints (website).
  • Scenario 3: a developer/participant looks at GitHub → uses/develops the bot (GitHub).

Getting started (wallet/network)

  • What you need: an EVM wallet for operations with BAD; Telegram to talk to the bot.
  • Network/chain: Ethereum mainnet.
  • Fees: gas on Ethereum for onchain transactions with the token; the bot works offchain.

Architecture/tech (non‑AI)

  • Components: the ERC‑20 token BAD (onchain) + the Telegram bot (offchain) + website/documents (Tier‑1).
  • Participant roles: token holders; bot users; those supporting the project/repository.
  • Where logic runs: onchain — the token; offchain — the bot/knowledgebase/integrations.
  • Dependencies: Ethereum; Telegram; the bot hosting infrastructure.

Token/economics (expanded, no forecasts)

  • Token utility: — (in the extracted Tier‑1 there is no description of a mandatory utility: payment/access/collateral).
  • Protocol necessity drivers: —.
  • Who pays fees: users pay gas on Ethereum for onchain transactions with the token.
  • Where fees go: to Ethereum validators (network fees).
  • Issuance/burn: the contract is ERC‑20 burnable (Etherscan source code); supply values conflict between Etherscan and the GitHub README (see the passport).
  • Security/incentive mechanisms: —.
  • Distribution and token issuance schedule: — (in the extracted Tier‑1 there is no distribution/vesting table).
  • Treasury: —.

Governance

  • Who makes decisions: — (the whitepaper uses the term DAO, but the specific process/venues were not extracted).
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: — (the website has a link to Certik, but it is an external resource; in the extracted Tier‑1 there is no published audit report as a primary artifact of the project).
  • Bug bounty: —.
  • Incidents: —.
  • Threat model: centralized dependence on the offchain bot/infrastructure; there are no confirmed onchain mechanics of DAO/access; at the same time, the AI part is not accompanied by metrics and an architectural description in Tier-1.

Project status and timeline

  • Current status: the website is active; the BAD token exists; the S.A.R.A.H. bot is available in Telegram.
  • Key releases/milestones: release notes and a changelog for SARAH are published in GitHub (GitHub).
  • Roadmap: — (the pitchdeck emphasizes the absence of a fixed roadmap; see GitBook).

Ecosystem/integrations

  • Integrations: Telegram (the bot); GitHub (code/documentation).
  • Partners: —.
  • Where it’s actually used: the Telegram bot as a product; the token is traded on DEXes/listings (the list in GitHub docs/LISTINGS.md is for reference).

AI component of the project

  • What is real AI here? the S.A.R.A.H. Telegram bot (described on the website and in GitHub as a conversational assistant with modes/multilingual support).
  • What is truly onchain? the ERC‑20 token BAD on Ethereum is confirmed (Etherscan).
  • Why is a token needed? in the extracted Tier‑1 the token is described as “powering the ecosystem”, but a specific irreplaceable utility (payment/access/collateral) is not confirmed.
  • Red flags (based on the information found): token‑washing (no proven utility); onchain‑washing (no onchain logic besides the token); AI‑washing (no metrics/architecture of the bot’s model in Tier‑1).

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): There are signs of AI reality per Tier‑1 (see AI_1..AI_4), so the AI_0 flag (intent‑only) does not apply.
  • Evidence: Tier‑1 — see Evidence/links in AI_1..AI_4.
  • Why sufficient / why not (one line): AI_0=1 is admissible only when AI_1..AI_4=0; here ai_score without AI_0 = 3.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): S.A.R.A.H. is a conversational assistant in Telegram (persona modes, multi‑language, knowledgebase — per GitHub).
  • Evidence: Tier‑1 — https://www.badidea.ai/ ; https://github.com/MrLightspeed/Bad-Idea-AI
  • Why sufficient / why not (one line): a specific function of the AI component is described.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): the website has a direct entry point to the Telegram bot (Open in Telegram).
  • Evidence: Tier‑1 — https://www.badidea.ai/ ; https://badidea.ai/about
  • Why sufficient / why not (one line): the existence of a public “entry point” serves as a demo of access, although the quality of answers is not measured.
  • 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/MrLightspeed/Bad-Idea-AI
  • Why sufficient / why not (one line): in the extracted Tier‑1 there are no metrics of the bot’s quality/accuracy/latency.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): GitHub publishes technical descriptions/release notes for SARAH (README + changelog).
  • Evidence: Tier‑1 — https://github.com/MrLightspeed/Bad-Idea-AI ; https://github.com/MrLightspeed/Bad-Idea-AI/blob/main/docs/CHANGELOG.md
  • Why sufficient / why not (one line): there are technical artifacts of the bot’s implementation.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: BAD token: 0x32b86b99441480a7e5bd3a26c124ec2373e3f015
  • Evidence: Tier‑1 — https://etherscan.io/token/0x32b86b99441480a7e5bd3a26c124ec2373e3f015 ; https://bad-idea-ai.gitbook.io/bad-idea-ai-pitchdeck/
  • Why sufficient / why not (one line): the token address is confirmed by the explorer and duplicated in the docs.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: in the extracted Tier‑1 only the ERC‑20 token is confirmed, without additional product logic/contracts.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x32b86b99441480a7e5bd3a26c124ec2373e3f015
  • Why sufficient / why not (one line): there are no other onchain artifacts (staking/access/DAO) in the extracted Tier‑1.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: apart from the existence of the token, the remaining elements (bot/content) work offchain and do not require a blockchain.
  • Evidence: Tier‑1 — https://github.com/MrLightspeed/Bad-Idea-AI ; https://www.badidea.ai/
  • Why sufficient / why not (one line): onchain is not proven to be critical for the functions of the AI bot.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, BAD.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x32b86b99441480a7e5bd3a26c124ec2373e3f015
  • Why sufficient / why not (one line): the token is confirmed onchain.
  • 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/access with the BAD token is not confirmed in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://www.badidea.ai/ ; https://bad-idea-ai.gitbook.io/bad-idea-ai-pitchdeck/
  • Why sufficient / why not (one line): in the extracted docs/whitepaper there is no specific payment/pricing in BAD.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): staking/collateral/penalties via BAD are not confirmed in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://www.badidea.ai/ ; https://static1.squarespace.com/static/64568e2523471d05956228f1/t/64570517d89163351580ef5c/1683424539459/BAD+IDEA+AI+WHITEPAPER+v1.0.pdf
  • Why sufficient / why not (one line): in the extracted whitepaper fragments there is no explicit onchain incentive mechanic.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): a governance mechanism with BAD is not confirmed by onchain artifacts/procedures in the extracted Tier‑1.
  • Evidence: Tier‑1 — https://bad-idea-ai.gitbook.io/bad-idea-ai-pitchdeck/ ; https://static1.squarespace.com/static/64568e2523471d05956228f1/t/64570517d89163351580ef5c/1683424539459/BAD+IDEA+AI+WHITEPAPER+v1.0.pdf
  • Why sufficient / why not (one line): the word “DAO” is present, but there are no implementations/addresses/rules.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): since the extracted Tier‑1 contain no mandatory onchain mechanics, the token looks replaceable (as a “meme asset” around the bot/community).
  • Evidence: Tier‑1 — https://www.badidea.ai/ ; https://github.com/MrLightspeed/Bad-Idea-AI
  • Why sufficient / why not (one line): the absence of a proven protocol utility increases replaceability.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.badidea.ai/ Project description and the link to the S.A.R.A.H. bot, whitepaper/pitchdeck.
Tier‑1 https://badidea.ai/about The “About” page, link to the Telegram bot and the whitepaper.
Tier‑1 https://bad-idea-ai.gitbook.io/bad-idea-ai-pitchdeck/ Project description + confirmation of the token parameters (BAD, ERC‑20, address).
Tier‑1 https://static1.squarespace.com/static/64568e2523471d05956228f1/t/64570517d89163351580ef5c/1683424539459/BAD+IDEA+AI+WHITEPAPER+v1.0.pdf Whitepaper: the concept of the AI+DAO experiment.
Tier‑1 https://github.com/MrLightspeed/Bad-Idea-AI Repository of the bot/tools (description of functions, release notes).
Tier‑1 https://etherscan.io/token/0x32b86b99441480a7e5bd3a26c124ec2373e3f015 Onchain confirmation of the BAD token, supply, source code.
Tier‑2 https://skynet.certik.com/projects/bad-idea External link to the scan/audit (mentioned on the website).

No comments to display

Back to top