DeepBot (Deep Whales AI)

DeepBot (Deep Whales 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).

DeepBot (Deep Whales AI) — an AI/Other | DeFi project on the Ethereum network, token (symbol: DEEPAI).

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 set of tools for onchain trading via Telegram + a web interface (trading, alerts, monitoring).
Who it’s for: traders/Telegram users who need alerts and quick access to trades.
Why onchain/token: the onchain part is confirmed per Tier‑1 in the form of an ERC‑20 token; no Tier‑1 confirmation of the product’s onchain logic (other than the token) was found.

How it works (very briefly)

The user does: connects the bot/tools and (if needed) a wallet.
The system does: provides alerts/signals and an interface for trades.
The user gets: notifications and the ability to make trades via the DeepBot tools.
Where the blockchain is: the issuance of the DEEPAI token on the Ethereum network and its contract are confirmed onchain (see explorer).
Token role (if any): the Tier‑1 documentation describes the DEEPAI token and a “revenue share” model for eligible addresses (see Evidence).

Quick links: AI thesis fit

Project passport

Field	Value
Project name	DeepBot (Deep Whales AI)
Also known as (aliases)	Deep Whales AI, DEEPAI
Logo (logo)	—
Token symbol (ticker)	DEEPAI
Category	AI/Other \| DeFi
Primary chain (chain)	Ethereum
Type	EVM
Network status	mainnet
Consensus (consensus)	PoS (Ethereum)
Launch date (launch_date)	2024-02
Project status (status)	active
Token (standard)	ERC-20
Token contract	0x18bc66f0c15e27179dd8e2277c1c9c056df0a14d
Token model (token_type)	—
Max supply	100 000 000 DEEPAI
Issuance	fixed
Tokenomics (tokenomics, brief)	The Tier‑1 documentation specifies a 5/5 tax and an eligibility criterion for “revenue share” (min. 100 000 DEEPAI).
Governance	—
Admins/keys	—
Audit	—
Bug bounty	—
Team (team)	DeepBot team (Deep Whales AI)
Funding (investors/funding)	—
AI component (ai_component)	AI analysis for signals/alerts
Use‑case (use_case)	Telegram trading + alerts + monitoring
DecAI Fit — AI thesis fit	2/6 — low alignment with the Decentralized AI thesis
DecAI Fit component summary	ai_score 1 / onchain_score 1 / token_score 1 / evidence_score 0
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://www.deepbot.pro
Docs	https://docs.deepwhalesai.ai
GitHub	—
Releases / Changelog	—
Whitepaper	—
Roadmap	https://docs.deepwhalesai.ai/deepbot-toolkit-overview/deepbot-roadmap
Security advisories	—
Explorer	https://etherscan.io/token/0x18bc66f0c15e27179dd8e2277c1c9c056df0a14d
X	https://twitter.com/DeepBot_
Discord	—
Telegram	https://t.me/DeepBotChat
Medium	https://medium.com/deepwhalesai
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/deep-whales-ai
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/deepmind-ai/

General project overview

DeepBot describes itself as a crypto trading toolkit around Telegram and a web interface: alerts, trading tools and monitoring. Per Tier‑1 sources, this is an applied product (not an L1/L2 network and not a standalone protocol), while the onchain artifact is explicitly confirmed as the DEEPAI ERC‑20 token on the Ethereum network.

In DecAIHub terms, the key question is what is actually “AI” here. Per Tier‑1 sources, there are claims about AI analytics/alerts, but no Tier‑1 tech description (model/architecture/versions) or metrics were found to raise the AI_1..AI_4 flags.

Features/modules

Telegram tools: bots/tools for trading and alerts.
Web interface: a trading interface for working via a browser.
Signals/alerts (claimed): alerts and “AI‑driven” analysis as part of the product (without disclosure of the model/metrics).

Typical scenarios

Scenario 1: a user connects the tools → receives alerts and quick access to trades.
Scenario 2: a user configures notifications/monitoring → receives signals and notifications on events.

Getting started (wallet/network)

What you need: Telegram and the account/wallet used in the product (details — in the project’s Tier‑1 documentation).
Network/chain: Ethereum — for the DEEPAI token; the use of onchain for the product logic (other than the token) is not established per Tier‑1 sources.
Fees: Ethereum network fees for operations with the token; the product’s commissions/fees are described in the Tier‑1 documentation.

Architecture/tech (non‑AI)

Components: the product’s Telegram bots, the web interface and the project infrastructure; the onchain artifact is the DEEPAI ERC‑20 token.
Participant roles: users of the product.
Where logic runs: application logic — offchain (the product); the token — onchain (Ethereum).
Dependencies: not established per Tier‑1 sources.

Token/economics (expanded, no forecasts)

What is confirmed by Tier‑1: the project documentation records the ticker/chain/total supply and the contract address of the DEEPAI token.
Token utility (Tier‑1 claimed): a “revenue share” model is described with an eligibility criterion via token ownership (as well as a link to access to the PRO tier).
Issuance: fixed (total supply 100 000 000).
Other details (vesting/treasury/burn): not found per Tier‑1 sources.

Governance

Who makes decisions: not established (Tier‑1).
How protocol parameters change: not established (Tier‑1).

Security and incidents

Audits: no Tier‑1 confirmation found.
Bug bounty: no Tier‑1 confirmation found.
Incidents: no Tier‑1 confirmation found.
Threat model: the risks of applied trading tools depend on the implementation; not established per Tier‑1 sources.

Project status and timeline

Current status: active (based on the presence of up‑to‑date Tier‑1 documentation/product pages).
Key milestones: the Tier‑1 documentation states “launched in February 2024”.
Roadmap: see links_*.

Ecosystem/integrations

Integrations/partners: we do not record them as a fact without Tier‑1 primary sources (not established per Tier‑1).
Where it’s actually used: the product is presented as Telegram tools and a web interface (see Evidence).

AI component of the project

What is real AI here? Tier‑1 sources contain claims about AI analytics/alerts, but no tech description or metrics were found.
What is truly onchain? The DEEPAI ERC‑20 token on the Ethereum network and its contract.
Why is a token needed? The Tier‑1 documentation describes a link to “revenue share” and an eligibility criterion via token ownership; the product’s onchain logic other than the token is not established.
Red flags (based on the information found): “AI signals” without a model/metrics; onchain‑washing (onchain boils down to the token); absence of Tier‑1 proof of the product’s onchain logic other than the token.

DecAI Fit component summary

DecAI Fit: 2/6 — low alignment with the Decentralized AI thesis

Component	Level	Score
AI reality	low	1
Onchain necessity	low	1
Token necessity	low	1
Evidence	Tier‑1 present	0

Details

AI reality

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

AI_0 (decision): 1
Claim (one line): Tier‑1 sources claim “AI powered” alerts/analytics as part of the product.
Evidence: Tier‑1 — https://www.deepbot.pro/
Why sufficient / why not (one line): There is a declaration of AI applicability, but no Tier‑1 tech description/metrics to confirm the operation/quality of the AI part.
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 0
Claim (one line): What exactly the AI model/algorithm is and how it works at the system level — not established per Tier‑1.
Evidence: Tier‑1 — https://www.deepbot.pro/ ; https://docs.deepwhalesai.ai/
Why sufficient / why not (one line): The wording about AI remains high‑level; there is no description of specific models/data/outputs.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): No Tier‑1 reproducible example of the AI part (an input→output example that can be repeated) was found.
Evidence: Tier‑1 — https://docs.deepwhalesai.ai/
Why sufficient / why not (one line): There is a description of the product and links to the tools, but no demo of the AI logic as a verifiable artifact.
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: —
Context (version/date/how measured): —
Evidence: Tier‑1 — https://docs.deepwhalesai.ai/
Why sufficient / why not (one line): Metrics/benchmarks for the AI part of the product were not found in Tier‑1 sources.
Conflict note (if any): —

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

AI_4 (decision): 0
Claim (one line): A tech description of the AI part (model/architecture/versions) was not found per Tier‑1 sources.
Evidence: Tier‑1 — https://docs.deepwhalesai.ai/
Why sufficient / why not (one line): The documentation describes product sections but does not provide an AI architecture/versions.
Conflict note (if any): —

Onchain necessity

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

OC_1 (decision): 1
Chain: Ethereum
Addresses/identifiers: 0x18bc66f0c15e27179dd8e2277c1c9c056df0a14d (ERC‑20)
Evidence: Tier‑1 — https://docs.deepwhalesai.ai/token-and-revenue/token-and-revenue/deepbot-token ; https://etherscan.io/token/0x18bc66f0c15e27179dd8e2277c1c9c056df0a14d
Why sufficient / why not (one line): Tier‑1 sources provide the contract address and there is a public network 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, no confirmation of the product’s onchain logic other than the token was found).
Evidence: Tier‑1 — https://docs.deepwhalesai.ai/
Why sufficient / why not (one line): Tier‑1 describes the product as a Telegram/web platform; the onchain artifact is explicitly confirmed only for the token.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 0
“Replace the blockchain” test: It is not established that the product breaks down without the blockchain (other than the existence of the token).
Evidence: Tier‑1 — https://docs.deepwhalesai.ai/
Why sufficient / why not (one line): There is no Tier‑1 justification that the critical properties of the product require onchain.
Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

TK_0 (decision): 0
Claim (one line): The project has a token, DEEPAI (ERC‑20, Ethereum).
Evidence: Tier‑1 — https://docs.deepwhalesai.ai/token-and-revenue/token-and-revenue/deepbot-token ; https://etherscan.io/token/0x18bc66f0c15e27179dd8e2277c1c9c056df0a14d
Why sufficient / why not (one line): Tier‑1 sources record the ticker/chain/contract address.
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): Mandatory payment for the service with the DEEPAI token is not established per Tier‑1 sources.
Evidence: Tier‑1 — https://www.deepbot.pro/ ; https://docs.deepwhalesai.ai/token-and-revenue/token-and-revenue/revenue-share
Why sufficient / why not (one line): Tier‑1 describes holding the token as a condition for some functions/the distribution model, but does not record “pay-per-use” as a mandatory mechanism.
Conflict note (if any): —

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

TK_2 (decision): 1
Claim (one line): The Tier‑1 documentation describes a model of distributing part of the revenue/fees into a pool and its distribution among eligible addresses based on the token ownership criterion.
Evidence: Tier‑1 — https://docs.deepwhalesai.ai/token-and-revenue/token-and-revenue/revenue-share
Why sufficient / why not (one line): This describes an economic mechanic with a token ownership criterion, tied to the rules of the product.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): The use of the token for governance is not established per Tier‑1.
Evidence: Tier‑1 — https://docs.deepwhalesai.ai/
Why sufficient / why not (one line): No description of voting/a DAO tied to the token was found in the documentation.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 0
Claim (one line): The replaceability of the token (for example, with a subscription/stablecoins) as a proven thesis is not established per Tier‑1.
Evidence: Tier‑1 — https://docs.deepwhalesai.ai/token-and-revenue/token-and-revenue/revenue-share
Why sufficient / why not (one line): 1 requires an explicit Tier‑1 justification “possible without the token without loss of meaning”; not found per Tier‑1 sources.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://docs.deepwhalesai.ai/	Description of the product as a Telegram/web platform.
Tier‑1	https://www.deepbot.pro/	Claims about AI‑powered alerts/analytics as part of the functionality (intent).
Tier‑1	https://docs.deepwhalesai.ai/token-and-revenue/token-and-revenue/deepbot-token	Token: name/ticker/chain/total supply and contract address.
Tier‑1	https://etherscan.io/token/0x18bc66f0c15e27179dd8e2277c1c9c056df0a14d	Onchain fact: the existence of the token contract on Ethereum (a verifiable artifact).
Tier‑1	https://docs.deepwhalesai.ai/token-and-revenue/token-and-revenue/revenue-share	Description of the “revenue share” model and the eligibility criterion via token ownership (token utility).
Tier‑1	—	No Tier‑1 source for claim “there is onchain logic of the product other than the token” was found.