Skip to main content

Hyperbot

Hyperbot (BOT) — 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).

Hyperbot — a DeFi/Trading / AI/Analytics project: an AI‑powered “gateway to perp DEXs” — a single entry point for monitoring of onchain data/whales, signals and copy/grid trading. Per the official documentation, Hyperbot uses a “Web for Action, Bot for Insight” architecture: strategies on the web console, while notifications/intelligence come via Telegram bots. The BOT token is a BEP‑20 on the BNB Smart Chain 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 trading terminal/bot for perp‑DEXs: monitoring of “smart money/whales” + strategy automation (copy/grid).
  • Who it’s for: traders and communities that need fast signaling and trade copying.
  • Why onchain/token: onchain is needed for executing trades on DEXs and for verifiable address data; BOT is a utility/incentive token and (per the docs) governance/access to features.

How it works (very briefly)

  1. The user does: connects a wallet/address and chooses a mode: monitoring, copy trading, grid trading.
  2. The system does: aggregates onchain data/leaderboards, applies the tagging system (in the docs — AI semantic analysis + behavioral metrics) and delivers signals via the bot matrix.
  3. The user gets: alerts, “smart money” filtering and automated strategy execution/copying.
  4. Where the blockchain is: trade execution happens on onchain perp‑DEXs; the BOT token is onchain (BSC).
  5. Token role: per the docs — incentives (data/strategies/referrals/LP/staking) and consumption (copy trading fees, premium, API, promos) + governance.

Quick links: AI thesis fit

Project passport

Field Value
Project name Hyperbot
Also known as (aliases) HyperBot, BOT
Logo (logo) ../assets/231_hyperbot_logo.png
Token symbol (ticker) BOT
Category AI/Analytics | DeFi/Trading
Primary chain (chain) BNB Smart Chain
Type EVM
Network status mainnet
Consensus (consensus) PoSA (BNB Smart Chain; 21 validators)
Launch date (launch_date) —
Project status (status) active
Token (standard) BEP-20
Token contract 0x59537849f2a119ec698c7Aa6C6DaAdc40C398A25
Token model (token_type) utility (governance)
Max supply 1,000,000,000 BOT (BscScan Max Total Supply)
Issuance fixed supply (per the token docs / BscScan max total supply)
Tokenomics (tokenomics, brief) dual‑cycle “Incentives‑Consumption”: rewards for contribution + spending on fees/premium/API (per the token docs)
Governance governance via the BOT token (per the token docs; mechanism details not disclosed)
Admins/keys there is a transfer controller/transfer mode role in the “similar match source code” (BscScan)
Audit yes (audit PDF in links_*)
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) AI tagging + whale/signal analytics
Use‑case (use_case) copy + grid trading + whale tracking
DecAI Fit — AI thesis fit 5/6 — high alignment with the Decentralized AI thesis
DecAI Fit component summary 2 / 2 / 3 / 3
Last verified 2026-02-11

General project overview

Hyperbot describes itself as an AI‑powered gateway to perp‑DEXs: it combines “smart money” discovery, flow/address monitoring, copy trading and grid trading. The official docs highlight a “Dual‑Layer Architecture”: a web application for deploying/managing strategies and a Telegram bot matrix for notifications and distribution of “intelligence” (alerts/trends/whales).

In the BOT token model (in the docs), two layers are claimed: incentives (for contributing data/strategies/referrals/liquidity/staking) and consumption (paying copy trading fees, premium features, API access and promo resources).

Features/modules

  • Smart Discovery / address monitoring: leaderboards, filters and address behavior tags (docs).
  • Tagging System: behavioral tags and risk identification based on onchain data over a 90‑day window (docs).
  • Copy Trading: copying top traders, risk controls and a service fee (docs).
  • Grid Trading: automation of “buy low, sell high” within a set range (docs).
  • Bot Matrix: Telegram bots for alerts and a “community alpha station” (docs).

Typical scenarios

  • Scenario 1: a user finds “Large Fund + Stable Profit” addresses → tracks alerts on them → makes trading decisions.
  • Scenario 2: a user selects a trader from the leaderboard → launches copy trading → receives results and notifications in Telegram.
  • Scenario 3: a user launches a grid strategy within a range → the bot pushes notifications on trades/profit.

Getting started (wallet/network)

  • What you need: Telegram (bot/mini app) and/or the web version; a wallet/address for working with perp‑DEXs.
  • Network/chain: BNB Smart Chain (the BOT token); trading takes place on the integrated perp‑DEXs (for example, Hyperliquid is mentioned in the docs/CMC).
  • Fees: network/DEX fees + the Hyperbot service fee (in the docs: 0.1% per transaction when trading on Hyperliquid via Hyperbot).

Architecture/tech (non‑AI)

  • Components: Web App (strategy command center) + Bot Matrix (notification/broadcast) + the onchain BOT token (docs/BscScan).
  • Participant roles: traders, data/strategy contributors, BOT holders.
  • Where logic runs: analytics/signals — offchain services; trade execution — onchain on DEXs; the token — onchain (BSC).
  • Dependencies: onchain data (transactions/positions) and integrations with perp‑DEXs.

Token/economics (expanded, no forecasts)

  • Token utility: BOT is used to pay copy trading fees, premium subscriptions, API and promo resources; also for rewards (data/strategies/referrals/LP/staking) — per the token docs.
  • Protocol necessity drivers: BOT is claimed as the value carrier and governance core; part of the functionality is tied to payment/access and incentives (per the token docs).
  • Who pays fees: users (trading fees + service fees + onchain fees).
  • Where fees go: — (not disclosed).
  • Issuance/burn: supply = 1B (token docs; BscScan max total supply).
  • Security/incentive mechanisms: staking/LP incentives, rewards for contribution; risk controls in copy trading are described in the docs as part of the risk engine.
  • Distribution and token issuance schedule: the token docs contain a distribution chart, but the numeric values were not extracted (image).
  • Treasury: —.

Governance

  • Who makes decisions: governance via BOT is claimed (details not disclosed).
  • How protocol parameters change: —.
  • Where decisions are discussed/made: docs + X/Telegram.
  • Keys/multisig: —.

Security and incidents

Project status and timeline

  • Current status: the product is available (web + Telegram bot/mini app), the token is on BSC.
  • Key releases/milestones: —.
  • Roadmap: —.

Ecosystem/integrations

  • Integrations: the CMC “About” mentions integrations with Hyperliquid and Aster; the docs — a Hyperliquid copy‑trading flow and Telegram bots.
  • Partners: —.
  • Where it’s actually used: a trading terminal and community alerts (per the docs).

AI component of the project

  • What is real AI here? The docs claim AI‑refined “actionable intelligence”, AI semantic analysis for categorizing address behavior and a tagging system with metrics/thresholds.
  • What is truly onchain? onchain address/trade data (the source of signals) + the BOT token (BscScan).
  • Why is a token needed? BOT is claimed as an incentive and consumption token (fees/premium/API) + governance.
  • Red flags (based on the information found): AI‑washing (no quality metrics for the “AI models”), token‑washing (it needs to be checked what is actually paid for in BOT vs fiat/USDT), risks of a centralized risk engine/algorithms.

DecAI Fit component summary

  • DecAI Fit: 5/6 — high alignment with the Decentralized AI thesis
Component Level Score
AI reality medium 2
Onchain necessity medium 2
Token necessity medium 3
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 = 2.
  • Conflict note (if any): none.

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): the tagging system uses AI semantic analysis and onchain metrics to classify addresses and identify risks.
  • Evidence: Tier‑1 — https://docs.hyperbot.network/get-started/discover-and-monitor/discover-smart-addresses/the-tagging-system
  • Why sufficient / why not (one line): the docs contain a description of the architecture and the tag logic.
  • Conflict note (if any): none.

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): there is a description of features, but no reproducible demo/metrics specifically for the AI part (tag/signal quality).
  • Evidence: Tier‑1 — https://docs.hyperbot.network/ ; https://docs.hyperbot.network/get-started/discover-and-monitor/discover-smart-addresses/the-tagging-system
  • Why sufficient / why not (one line): without metrics/an evaluation protocol, the demo cannot be counted.
  • Conflict note (if any): none.

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://docs.hyperbot.network/
  • Why sufficient / why not (one line): quality metrics for the AI models/signals are not published.
  • Conflict note (if any): none.

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

  • AI_4 (decision): 1
  • Claim (one line): the Dual‑Layer architecture (web + bot matrix) and the logic of the tagging system are described.
  • Evidence: Tier‑1 — https://docs.hyperbot.network/ ; https://docs.hyperbot.network/get-started/discover-and-monitor/discover-smart-addresses/the-tagging-system
  • Why sufficient / why not (one line): sufficient for understanding “what the system does”.
  • Conflict note (if any): none.

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: BNB Smart Chain
  • Addresses/identifiers: BOT: 0x59537849f2a119ec698c7Aa6C6DaAdc40C398A25
  • Evidence: Tier‑1 — https://bscscan.com/token/0x59537849f2a119ec698c7Aa6C6DaAdc40C398A25
  • Why sufficient / why not (one line): BscScan confirms the contract and max supply.
  • Conflict note (if any): none.

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

  • OC_2 (decision): 0
  • What useful logic is onchain: apart from the BOT token, protocol/strategy contracts are not confirmed by addresses in the docs (mostly products and integrations are described).
  • Evidence: Tier‑1 — https://docs.hyperbot.network/
  • Why sufficient / why not (one line): without addresses, onchain logic cannot be counted as a fact.
  • Conflict note (if any): none.

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 1
  • “Replace the blockchain” test: without onchain there is no verifiable address/trade data and strategy execution on perp‑DEXs is impossible.
  • Evidence: Tier‑1 — https://docs.hyperbot.network/ ; https://docs.hyperbot.network/get-started/copy-trading
  • Why sufficient / why not (one line): the product is built on onchain data and onchain execution.
  • Conflict note (if any): part of the analytics remains offchain.

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): the project has a token, BOT.
  • Evidence: Tier‑1 — https://bscscan.com/token/0x59537849f2a119ec698c7Aa6C6DaAdc40C398A25
  • Why sufficient / why not (one line): confirmed by the explorer.
  • Conflict note (if any): none.

TK_1..TK_4 (1/0)

TK_1 — payment for the service (1/0)

  • TK_1 (decision): 1
  • Claim (one line): BOT is used to pay copy trading fees, premium features and API.
  • Evidence: Tier‑1 — https://docs.hyperbot.network/official-links/token-usdbot
  • Why sufficient / why not (one line): the use‑cases are listed in the token docs.
  • Conflict note (if any): not confirmed by onchain billing contracts.

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

  • TK_2 (decision): 1
  • Claim (one line): rewards for contributing data/strategies/referrals + liquidity/staking incentives.
  • Evidence: Tier‑1 — https://docs.hyperbot.network/official-links/token-usdbot
  • Why sufficient / why not (one line): the incentives are explicitly listed in the token docs.
  • Conflict note (if any): staking/LP parameters are not provided.

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): BOT is claimed as the “governance core” of the ecosystem.
  • Evidence: Tier‑1 — https://docs.hyperbot.network/official-links/token-usdbot
  • Why sufficient / why not (one line): the governance role is claimed in the token docs.
  • Conflict note (if any): no links to a specific voting mechanism.

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): the token is built into the incentives+consumption model and is claimed as the governance core.
  • Evidence: Tier‑1 — https://docs.hyperbot.network/official-links/token-usdbot
  • Why sufficient / why not (one line): the design implies the use of the token in key scenarios.
  • Conflict note (if any): whether the token is actually mandatory for all users is not proven.

Evidence (table)

Tier Source What it proves
Tier‑1 https://www.hyperbot.network/ Product description and a link to the BOT contract + audit link.
Tier‑1 https://docs.hyperbot.network/ Official documentation: architecture (web + bot matrix), modules and features.
Tier‑1 https://docs.hyperbot.network/official-links/token-usdbot Utility/token model of BOT (incentives + consumption), supply=1B, use‑cases.
Tier‑1 https://docs.hyperbot.network/get-started/copy-trading Description of copy trading and the service fee (0.1% per tx for Hyperliquid via Hyperbot).
Tier‑1 https://docs.hyperbot.network/get-started/discover-and-monitor/discover-smart-addresses/the-tagging-system Tagging system: metrics/thresholds and the principles of tag generation on onchain data.
Tier‑1 https://bscscan.com/token/0x59537849f2a119ec698c7Aa6C6DaAdc40C398A25 BOT contract (BEP‑20), max total supply 1B, links to the official domain.
Tier‑1 https://github.com/HyperbotNetworkOrg Official repositories (frontend + smartcontract).
Tier‑1 https://github.com/HyperbotNetworkOrg/hyperbot-smartcontract/blob/main/Hyperbot(BOT)_audit_report.pdf Audit PDF in the project’s official repository.

No comments to display

Back to top