Skip to main content

Bubsy AI

Bubsy AI — 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).

Bubsy AI — an AI/Analytics project on the Ethereum network, token (symbol: BUBSY).

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 bot + dApp that claim AI‑assisted community moderation/analytics features.
  • Who it’s for: teams/communities and users who need a dashboard/alerts and analysis (for example, of holders/wallets).
  • Why onchain/token: the token is claimed as a “key” to access tiers (tiers) and staking/rewards; onchain records the token contract and operations.
  • What you can actually touch (Tier‑1): the web dApp bubsy.ai (see links_*).

How it works (very briefly)

  1. The user does: connects a wallet to the dApp and/or uses the bot.
  2. The system does: displays analytics/monitoring (claimed: of holders/wallets) and provides tiered access to features.
  3. The user gets: a dashboard/alerts and analysis results (details of the AI part/methodology are not verified in this card).
  4. Where the blockchain is: the BUBSY ERC‑20 token and related transactions; token ownership is used as an access condition.
  5. Token role: access to features (tiers) and claimed staking/rewards.

Quick links: AI thesis fit

Project passport

Field Value
Project name Bubsy AI
Also known as (aliases) Bubsy, BUBSY
Logo (logo) ../assets/826_bubsy-ai_logo.png
Token symbol (ticker) BUBSY
Category AI/Analytics
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 0xd699b83e43415b774b6ed4ce9999680f049af2ab
Token model (token_type) utility (tiers + staking + rewards)
Max supply 70,000,000 BUBSY
Issuance fixed
Tokenomics (tokenomics, brief) Access tiers (tiers) for features and staking rewards are claimed; the documentation also describes the distribution structure: 85% liquidity / 5% partnerships / 5% team (locked until 2025) / 5% airdrops (burned).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI-assisted analysis/community moderation
Use‑case (use_case) holder/wallet analytics + alerts
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 2 / onchain_score 1 / token_score 2 / evidence_score 3
Last verified 2026-02-11

General project overview

Per the Tier‑1 documentation, Bubsy is an ecosystem consisting of a bot and a dApp that claims to help moderate, analyze and understand the community “with the help of Artificial Intelligence”. The Tier‑1 website mentions holder/wallet analytics features, tiered access to features via the token and a separate staking/rewards section.

Features/modules

  • DApp: an interface for features and settings.
  • Bot: claimed as part of the ecosystem.
  • Holder analytics (claimed): analysis of top holders/holding structure.
  • Wallet tracking (claimed): wallet tracking and alerts (claimed: Telegram).
  • Tiers + staking/rewards (claimed): access to features and staking/rewards.

Typical scenarios

  • Scenario 1: a user opens the dApp and runs an analysis → receives a conclusion/dashboard (claimed).
  • Scenario 2: a user enables wallet tracking → receives alerts (claimed).

Getting started (wallet/network)

  • What you need: an EVM wallet (to connect to the dApp).
  • Network/chain: Ethereum (token).
  • Fees: Ethereum network fees for transactions.

Architecture/tech (non‑AI)

  • Components: web dApp + bot + offchain analytics/AI processing (details not verified) + token contract.
  • Participant roles: dApp/bot users; token holders (tiers).
  • Where logic runs: AI/analytics — offchain; token accounting and ownership — onchain (Ethereum).
  • Dependencies: — (not verified).

Token/economics (expanded, no forecasts)

  • Token utility (Tier‑1): the Tier‑1 website claims that features are available in tiers using the BUBSY token.
  • Incentive mechanisms (Tier‑1): the Tier‑1 documentation describes a Rewards/Staking DApp with lock options (15 days / 3 months / 1 year) and reward payouts in ETH.
  • Issuance: max total supply 70,000,000 BUBSY (Tier‑1, explorer).

Governance

  • Who makes decisions: — (not established per Tier‑1 sources).
  • How protocol parameters change: —.
  • Where decisions are discussed/made: —.
  • Keys/multisig: —.

Security and incidents

  • Audits: not found per Tier‑1 sources.
  • Bug bounty: not found per Tier‑1 sources.
  • Incidents: not found per Tier‑1 sources.
  • Threat model: —.

Project status and timeline

  • Current status: active (there is a dApp and documentation).
  • Key releases/milestones: — (not verified).
  • Roadmap (Tier‑1): https://docs.bubsy.ai/overview/roadmap

Ecosystem/integrations

  • Integrations: not verified per Tier‑1 sources.
  • Partners: not verified per Tier‑1 sources.
  • Where it’s actually used: not verified per Tier‑1 sources.

AI component of the project

  • What is real AI here? The Tier‑1 documentation claims the use of AI for community moderation/analysis.
  • What is truly onchain? The BUBSY ERC‑20 token on Ethereum (Tier‑1, explorer).
  • Why is a token needed? The Tier‑1 website claims tiers (access to features) and staking/rewards.
  • Red flags (based on the information found): there are no Tier‑1 AI quality metrics (AI_3=0) and no tech description of the AI part (AI_4=0) per the available Tier‑1 sources.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): AI intent is not singled out separately, because there is a direct Tier‑1 description of AI use (AI_1).
  • Evidence: Tier‑1 — https://docs.bubsy.ai/
  • Why sufficient / why not (one line): we use AI_1 as the basis instead of intent.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the Tier‑1 docs claim: the bot + dApp help moderate/analyze the community with the help of Artificial Intelligence.
  • Evidence: Tier‑1 — https://docs.bubsy.ai/
  • Why sufficient / why not (one line): The Tier‑1 documentation directly states the role of AI.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): there is a public dApp (connect wallet) as a surface for using the features.
  • Evidence: Tier‑1 — https://bubsy.ai/
  • Why sufficient / why not (one line): we record the presence of a public dApp as a demo surface.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: no Tier‑1 quality metrics/benchmarks for the AI part were found.
  • Context (version/date/how measured): —
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there are no published metrics per the SSOT definition.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): the tech description/architecture/versions of the AI part (model/version/parameters) were not found per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no repository/technical documentation for the AI model in links_*.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: 0xd699b83e43415b774b6ed4ce9999680f049af2ab
  • Evidence: Tier‑1 — https://etherscan.io/token/0xd699b83e43415b774b6ed4ce9999680f049af2ab
  • Why sufficient / why not (one line): the onchain fact of the token contract is confirmed by the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: not established per Tier‑1 sources (other than the token).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): other contracts/protocol logic are not verified.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: no Tier‑1 justification of onchain criticality was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): “criticality” is not proven.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, BUBSY (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xd699b83e43415b774b6ed4ce9999680f049af2ab
  • Why sufficient / why not (one line): the onchain fact of the token is established per the explorer.
  • 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): tiers of access to features “using the $BUBSY token” are claimed.
  • Evidence: Tier‑1 — https://bubsy.ai/
  • Why sufficient / why not (one line): The Tier‑1 website directly specifies the token as a condition for access to features/tiers.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): claimed: “Stake the $BUBSY token and earn rewards”.
  • Evidence: Tier‑1 — https://bubsy.ai/
  • Why sufficient / why not (one line): The Tier‑1 website directly mentions staking and rewards.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): the use of the token in governance is not established per Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 description of governance mechanics.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the replaceability of the token is not established.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): there is no Tier‑1 analysis of “replacing the token”.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.bubsy.ai/ Tier‑1: Bubsy is described as a bot + dApp for AI‑assisted community moderation/analytics.
Tier‑1 https://bubsy.ai/ Tier‑1: holder analytics, tiers (access via the token), staking/rewards and Multi‑Sig Vault are claimed.
Tier‑1 https://etherscan.io/token/0xd699b83e43415b774b6ed4ce9999680f049af2ab Onchain fact: the Bubsy AI (BUBSY) ERC‑20 token, max total supply 70,000,000.
Tier‑1 https://docs.bubsy.ai/bubsy-rewards/staking-dapp Rewards/Staking DApp: staking options with lock periods (15d / 3m / 1y) and reward payouts in ETH.
Tier‑1 https://docs.bubsy.ai/bubsy-token/bubsy-tokenomics Tokenomics: total supply 70M, distribution (liquidity/partnerships/team/airdrops) and contract address.
Tier‑1 https://docs.bubsy.ai/my-bubsy-dapp/bubsythebot BubsyTheBot: the purpose of the bot and the flow “purchasing a key in the dApp → activating the bot in Telegram”.
Tier‑1 https://docs.bubsy.ai/my-bubsy-dapp/pricing MyBubsy DApp: an access subscription (prices in ETH) for using Bubsy functionality.

No comments to display

Back to top