Skip to main content

Bubblemaps

Bubblemaps — 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).

Bubblemaps — an Analytics | InfoFi onchain analytics platform (visual maps of holders/clusters, “Intel Desk”), token (symbol: BMT) on Solana (SPL) and BNB Chain (BEP‑20, LayerZero OFT).

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 visual analytics platform for investigations: it shows top token holders, connections between addresses and clusters, and helps “trace” the movement of funds; a separate Intel Desk module collects cases and the work of researchers.
  • Who it’s for: traders, funds, analysts, project teams and “onchain sleuths”.
  • Why onchain/token: onchain is the data source for analytics and investigations; the BMT token is used for the Intel Desk mechanics (deposit/voting/bounties) and for access to advanced features (including AI interpretation of clusters).
  • What you can actually touch (Tier‑1): the application and Intel Desk (see links_* → App / Demo and links_* → Intel Desk (app)).

How it works (very briefly)

  1. The user does: opens the application, searches for a token/contract and studies the “bubble map”.
  2. The system does: builds a map of top holders (per the docs — 250 in the basic mode), displays connections/clusters based on onchain transfers, and provides filters and time modes (Time Travel, etc.).
  3. The user gets: a visual picture of the distribution/clusters and suspicious patterns for investigation/trading.
  4. Where the blockchain is: data — directly from blockchains (on‑chain transfers/holders); Intel Desk uses deposit/withdraw and voting via BMT.
  5. Token role (if any): BMT is needed for Intel Desk (deposit into the voting pool, voting, bounties) and for access to premium features (including AI models for interpreting clusters and deeper analytics).

Quick links: AI thesis fit

Project passport

Field Value
Project name Bubblemaps
Also known as (aliases) Bubblemaps V2; Intel Desk; $BMT
Logo (logo) ../assets/124_bubblemaps_logo.png
Token symbol (ticker) BMT
Category Analytics | InfoFi
Primary chain (chain) Solana
Type EVM
Network status mainnet
Consensus (consensus) PoS (Solana)
Launch date (launch_date) —
Project status (status) active
Token (standard) BEP-20
Token contract Solana: FQgtfugBdpFN7PZ6NdPrZpVLDBrPGxXesi4gVu3vErhY; BNB: 0x7d814b9ed370ec0a502edc3267393bf62d891b62
Token model (token_type) utility (governance (Intel Desk) + access (premium features))
Max supply 1,000,000,000 BMT (wiki)
Issuance fixed; omnichain issuance via burn/mint when bridging (OFT)
Tokenomics (tokenomics, brief) Circulating supply at TGE: 25.6%; vesting of up to 4 years (wiki)
Governance Intel Desk governance mechanics: voting and case prioritization via BMT
Admins/keys —
Audit yes (LayerZero token audit: Ottersec, Pashov; Migration/locking audit: Code4rena Zenith — per the wiki)
Bug bounty —
Team (team) —
Funding (investors/funding) The wiki notes an equity round (2023) and a token round (2024); the website — “Backed by …” (without a full list in a single document)
AI component (ai_component) AI interpretation of clusters/cases (summaries)
Use‑case (use_case) on-chain investigations (clusters/funds/insights)
DecAI Fit — AI thesis fit 4/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 2 / 1 / 3
Last verified 2026-02-11

General project overview

Bubblemaps is a product for onchain analytics and investigations that turns “raw” blockchain data (holders, transfers, address connections) into visual maps and structured insights. At the level of user experience it is an analytics application, not a blockchain protocol: you search for a token/address and get a map of holders and the connections between them.

A separate component is Intel Desk, described as a “collaborative investigation layer”: investigation cases are formed around events (a hack, insider trading, manipulation), and the community participates via BMT in choosing priorities, voting and the bounty mechanics.

Features/modules

  • Bubblemaps V2: bubble maps of holders and clusters, transfer filters, time modes (for example, “Time Travel”).
  • Intel Desk: investigation cases + contributor rankings, a voting/multiplier mechanism.
  • Premium (via BMT): extended analytics (for example, top‑1000 holders), cross‑chain analytics, and “AI models to interpret clusters” (per the wiki).
  • Integrations: iframe and API (as stated on the website) + embedding into external analytics platforms (the wiki gives examples).

Typical scenarios

  • Scenario 1 (token check): enters a ticker/contract → looks at top holders and clusters → looks for insider patterns (clustered holders, suspicious transfers).
  • Scenario 2 (public investigation): opens an Intel Desk case → reads the chain of findings → tracks which addresses/flows are linked to the event.
  • Scenario 3 (participation with the token): deposits BMT into the voting pool → votes for cases and/or launches bounties → gets access to extended materials/features (under the Intel Desk rules).

Getting started (wallet/network)

  • What you need: the application is enough for viewing maps; for Intel Desk and premium features — a wallet and BMT tokens.
  • Network/chain: the analytics is multichain; the BMT token is SPL (Solana) and BEP‑20 (BNB Chain) under the OFT model; Intel Desk starts on Solana (wiki).
  • Fees: onchain fees arise on BMT deposits/withdrawals and when moving the token between networks.

Architecture/tech (non‑AI)

  • Components: web client (Bubblemaps V2, Intel Desk) + offchain collection/processing of onchain data + onchain contracts/programs for BMT and its cross‑chain transfer (LayerZero OFT).
  • Participant roles: user‑researchers; “contributors/mappers”; BMT holders (voters/bounties).
  • Where logic runs: analytics/visualization — offchain; deposit/withdraw/voting (Intel Desk) and token transfer — onchain.
  • Dependencies: LayerZero (OFT), Solana/BNB Chain infrastructure, sources of onchain data/indexing.

Token/economics (expanded, no forecasts)

  • Token utility: BMT “powers Bubblemaps V2 and the Intel Desk” and grants access to advanced features, and is also used in the Intel Desk mechanics (vote/rank/earn; bounties; access to AI summaries/analytics).
  • Protocol necessity drivers: basic analytics may be available without the token, but Intel Desk and the premium layer are explicitly tied to BMT.
  • Who pays fees: users (Solana/BNB gas) on BMT operations.
  • Where fees go: the Tier‑1 sources contain no full scheme of fee distribution; bounties/rewards to participants are described.
  • Issuance/burn: the OFT transfer is described as a burn on the source chain and a mint on the destination chain via LayerZero.
  • Security/incentive mechanisms: incentives for proposers/voters/contributors; a penalty for quick withdrawal in Intel Desk (per the formula).
  • Distribution and token issuance schedule: the allocation and vesting table is given in the wiki tokenomics; “fully unlocked 4 years after listing”.
  • Treasury: not identified as a separate onchain treasury module within this card.

Governance

  • Who makes decisions: BMT holders choose case priorities via Intel Desk and (in general) the directions of investigations/resources.
  • How protocol parameters change: the Intel Desk governance mechanics are described (votes → multiplier → impact on rewards/visibility); the onchain parameters of the contracts/programs are not examined in detail.
  • Where decisions are discussed/made: Intel Desk + public channels (X/Discord/Telegram).
  • Keys/multisig: the Tier‑1 sources contain no brief summary of admin keys.

Security and incidents

  • Audits: the wiki lists “Token Audit (LayerZero): Ottersec, Pashov” and “Migration and Locking Audit: Code4rena Zenith”.
  • Bug bounty: not listed.
  • Incidents: not found in Tier‑1 sources.
  • Threat model: risks — misinterpretation of clusters (including possible erroneous matches), data limitations (exchange hot wallets/supernodes), and the security of the cross-chain OFT mechanics.

Project status and timeline

  • Current status: Bubblemaps V2 and Intel Desk are available as web applications; BMT is deployed on Solana and BNB Chain.
  • Key releases/milestones: updates are published in the wiki and blog; specific versions/release notes — on the website/blog.
  • Roadmap: no separate roadmap page is listed in the links.

Ecosystem/integrations

  • Integrations: iframe embedding, API (website); multichain support (wiki); LayerZero OFT for BMT.
  • Partners: the website/wiki list “backed by” and examples of integrations/mentions (DEXScreener, CoinGecko, Etherscan, etc.), but without a single list of contractual partners.
  • Where it’s actually used: investigation cases in Intel Desk (public UI) and token maps in Bubblemaps V2.

AI component of the project

  • What is real AI here? The Tier‑1 sources claim AI features: AI models for interpreting clusters and AI summaries of Intel Desk cases.
  • What is truly onchain? Investigation data — from blockchains; BMT and the deposit/withdraw/vote operations in Intel Desk — onchain.
  • Why is a token needed? BMT is used for Intel Desk voting/bounties/incentives and for access to premium features (including AI interpretation of clusters).
  • Red flags (based on the information found):
    • AI‑washing: “AI models” are claimed, but without a technical description/metrics (which models exactly, how quality is evaluated).
    • Onchain‑washing: the analytics is mostly offchain; onchain — in the token/Intel Desk.
    • Token‑washing: the base product is free, while the token is for premium/incentives; it is important to check how truly mandatory BMT is for the key value.
    • What to double‑check: the Intel Desk addresses and contracts (programs/contracts), as well as the specific AI mechanics (models/limitations).

DecAI Fit component summary

  • DecAI Fit: 4/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity medium 2
Token necessity low 1
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 features are claimed as existing (AI models/AI summaries), not only as plans.
  • Evidence: Tier‑1 — https://wiki.bubblemaps.io/bubblemaps-v2/premium , https://wiki.bubblemaps.io/intel-desk/powered-by-usdbmt
  • Why sufficient / why not (one line): AI_0=1 only when there is no AI_1..AI_4; here there is a Tier‑1 description of AI features.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): AI is used to interpret clusters/connections and for brief case summaries.
  • Evidence: Tier‑1 — https://wiki.bubblemaps.io/bubblemaps-v2/premium , https://wiki.bubblemaps.io/intel-desk/powered-by-usdbmt
  • Why sufficient / why not (one line): The Tier‑1 pages directly mention AI models/AI summaries as product features.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): The public Bubblemaps V2 and Intel Desk applications, where maps/cases are available (and an AI layer is claimed in premium/summary).
  • Evidence: Tier‑1 — https://v2.bubblemaps.io/ , https://intel.bubblemaps.io
  • Why sufficient / why not (one line): The existence of public UI entry points is sufficient for the demo criterion.
  • 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): The Tier‑1 sources contain no quantitative quality metrics for the AI interpretation/summaries.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): The technical description of the AI models/architecture is not disclosed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Mentioning AI features without specifications/architecture is insufficient for AI_4.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Solana + BNB Chain
  • Addresses/identifiers: Solana SPL BMT: FQgtfugBdpFN7PZ6NdPrZpVLDBrPGxXesi4gVu3vErhY; BNB BEP‑20 OFT BMT: 0x7d814b9ed370ec0a502edc3267393bf62d891b62
  • Evidence: Tier‑1 — https://wiki.bubblemaps.io/bmt/summary , https://wiki.bubblemaps.io/bmt/cross-chain
  • Why sufficient / why not (one line): The Tier‑1 wiki lists the networks and contract addresses.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: Intel Desk manages the deposit/withdraw of BMT in the voting pool and the participation/fee logic (anti‑spam).
  • Evidence: Tier‑1 — https://wiki.bubblemaps.io/intel-desk/deposit-and-withdraw , https://wiki.bubblemaps.io/intel-desk/powered-by-usdbmt
  • Why sufficient / why not (one line): Onchain operational logic around voting/deposits is described, not only the existence of the token.
  • Conflict note (if any): the addresses of the specific Intel Desk programs/contracts are not given in brief form.

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: the core analytics (maps/visualization) is theoretically possible as a centralized service as well; onchain is critical rather for the Intel Desk mechanics and the token, but is not proven critical for the entire platform.
  • Evidence: Tier‑1 — https://wiki.bubblemaps.io/
  • Why sufficient / why not (one line): There is no Tier‑1 statement that the product “breaks without onchain” as a protocol layer.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, BMT (SPL + BEP‑20 OFT).
  • Evidence: Tier‑1 — https://wiki.bubblemaps.io/bmt/summary
  • Why sufficient / why not (one line): The wiki explicitly lists the ticker, networks and token addresses.
  • 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 in BMT as a “mandatory payment for the service” is not claimed; the token is used for participation/bounties and access.
  • Evidence: Tier‑1 — https://wiki.bubblemaps.io/bmt/tokenomics , https://wiki.bubblemaps.io/intel-desk/powered-by-usdbmt
  • Why sufficient / why not (one line): Governance/access/incentives are described, not payment for the basic service.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): BMT is used for Intel Desk incentives (reward proposers/voters/contributors) and for bounties; there is a penalty for quick withdrawal (anti‑gaming).
  • Evidence: Tier‑1 — https://wiki.bubblemaps.io/bmt/tokenomics , https://wiki.bubblemaps.io/intel-desk/deposit-and-withdraw
  • Why sufficient / why not (one line): Tier‑1 describes the incentives and the withdrawal fee formula.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): BMT grants governance rights via Intel Desk: voting determines case priorities/the multiplier.
  • Evidence: Tier‑1 — https://wiki.bubblemaps.io/ , https://wiki.bubblemaps.io/intel-desk/how-does-it-work
  • Why sufficient / why not (one line): Tier‑1 describes the “vote → multiplier → impact” governance mechanics.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 1
  • Claim (one line): Intel Desk access/incentives/voting can be implemented without a token (subscription/points/account roles), while the analytics part of Bubblemaps V2 remains.
  • Evidence: Tier‑1 — https://wiki.bubblemaps.io/bubblemaps-v2/premium , https://wiki.bubblemaps.io/intel-desk/powered-by-usdbmt
  • Why sufficient / why not (one line): The token utility is an add‑on layer; the criticality of the token for the “operability” of the platform is not proven.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://bubblemaps.io/ What the product does: onchain intelligence layer, Bubblemaps V2 and Intel Desk.
Tier‑1 https://wiki.bubblemaps.io/ Description of Bubblemaps as a visual onchain intelligence engine; the role of BMT (utility token) and governance via Intel Desk.
Tier‑1 https://wiki.bubblemaps.io/bubblemaps-v2/premium Premium features for BMT holders, including AI models for cluster interpretation.
Tier‑1 https://wiki.bubblemaps.io/intel-desk/powered-by-usdbmt BMT mechanics in Intel Desk (vote/rank/earn, bounties, AI case summaries).
Tier‑1 https://wiki.bubblemaps.io/intel-desk/deposit-and-withdraw Deposit/withdraw in the voting pool and the withdrawal fee formula (anti‑gaming).
Tier‑1 https://wiki.bubblemaps.io/bmt/cross-chain The cross‑chain model of BMT via LayerZero OFT (burn/mint; networks/addresses).
Tier‑1 https://wiki.bubblemaps.io/bmt/tokenomics Max supply 1B, allocations/vesting, utility and a mention of audits.
Tier‑1 https://bscscan.com/token/0x7d814b9eD370Ec0a502EdC3267393bF62d891B62 The BNB version of BMT in the explorer.
Tier‑1 https://v2.bubblemaps.io/ Demo UI of Bubblemaps V2.
Tier‑1 https://intel.bubblemaps.io Demo UI of Intel Desk.
Tier‑2 — —
Tier‑3 — —

No comments to display

Back to top