Skip to main content

TAO.BOT

TAO.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).

TAO.BOT — a frontend/application for the Bittensor ecosystem: a subnet screener, swaps (TAO ↔ subnet tokens) and network analytics; token: TAOBOT (ERC‑20).

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 “terminal” app for Bittensor: view subnet metrics and trade their tokens.
  • Who it’s for: traders/LPs in the Bittensor ecosystem and ETH users who need a fast on‑ramp to subnet tokens.
  • Why onchain/token: onchain is needed for swaps/liquidity and asset accounting; the TAOBOT token is the project’s utility/economics (including a claimed share of fees in the future).

How it works (very briefly)

  1. The user does: connects a wallet (Native TAO mode) or makes a deposit into the ETH gateway.
  2. The system does: shows the subnet screener and provides a swap interface for TAO ↔ subnet tokens; for the gateway — keeps the deposit balance.
  3. The user gets: a trade/position and access to subnet analytics (prices, volumes, emissions, liquidity, etc.).
  4. Where the blockchain is: swaps and liquidity are executed on Bittensor (Native TAO) and/or via deposit/withdrawal on Ethereum (gateway).
  5. Token role (if any): TAOBOT (ERC‑20) is the project token; the docs describe supply parameters and a “planned utility” (including a planned distribution of fees from future LSTs).

Quick links: AI thesis fit

Project passport

Field Value
Project name TAO.BOT
Also known as (aliases) tao.bot; TAOBOT
Logo (logo) ../assets/148_tao-bot_logo.svg
Token symbol (ticker) TAOBOT
Category Infra
Primary chain (chain) Bittensor
Type non-EVM
Network status mainnet
Consensus (consensus) unknown
Launch date (launch_date) —
Project status (status) active
Token (standard) ERC-20
Token contract 0x49fb8ad7578148E17c3eF0C344CE23A66ed372C4
Token model (token_type) utility (fee-mechanism)
Max supply 100,000,000 TAOBOT
Issuance fixed (not mintable/burnable per the docs)
Tokenomics (tokenomics, brief) 65% LP (lock), 20% reserve (lock+vesting), 10% team (lock), 5% marketing; 5%/5% buy/sell tax (planned removal).
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) none
Use‑case (use_case) trade + analytics for Bittensor subnets
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 2 / 1 / 2
Last verified 2026-02-11

General project overview

TAO.BOT is a user application for the Bittensor ecosystem: a “terminal” for viewing subnet metrics and trading their tokens. Essentially it is a convenient UI that combines:

  • subnet screener (a table/pages with prices, volumes, emission shares, liquidity, etc.),
  • trading interface (TAO ↔ subnet token swaps),
  • portfolio and auxiliary tools,
  • two operating modes: Native TAO (direct onchain actions on the Bittensor network) and ETH Entry Gateway (deposit/withdrawal on Ethereum + trading via the gateway balance).

The project’s value is reducing friction for Ethereum users who want access to Bittensor subnet markets, and more convenient analytics for ecosystem participants.

Features/modules

  • Explore (Screener): a table of subnets with key KPIs (prices, volumes, emissions, MCAP, etc.) and search.
  • Subnet pages: detailed pages of a specific subnet (KPIs, charts, pools/liquidity, validator context).
  • Trade: swaps (Native TAO onchain) and swaps/execution via the gateway balance (ETH Entry Gateway).
  • Liquidity (Native TAO): liquidity management for supported pools (concentrated‑liquidity style).
  • Portfolio: balances and action history (swaps, gateway deposits/withdrawals, LP activities).
  • Bridge (gateway): deposit/withdrawal of ETH/USDC/USDT for access to trading without a native TAO wallet.

Typical scenarios

  • Scenario 1 (ETH user): deposits ETH/USDC/USDT into the gateway → buys TAO or a subnet token → withdraws back to Ethereum when needed.
  • Scenario 2 (Native TAO): connects a native TAO wallet → makes an onchain swap TAO ↔ subnet token → (optionally) adds liquidity to a pool.
  • Scenario 3 (analyst/subnet operator): views subnet KPIs/dynamics and liquidity → compares subnets by emission/volume/market cap.

Getting started (wallet/network)

  • What you need: open the app and connect a wallet (Native TAO) or an Ethereum wallet for the gateway.
  • Network/chain: Bittensor (Native TAO) and/or Ethereum mainnet (gateway deposit/withdrawal, TAOBOT token).
  • Fees: in Native TAO — Bittensor network fees; in the gateway — Ethereum gas for deposit/withdrawal; the docs state that the TAO.BOT trading fee = 0 (not excluding network fees).

Architecture/tech (non‑AI)

  • Components: web client (UI), gateway backend components (deposit/withdrawal and a “hosted balance” for ETH users), integrations with the Bittensor and Ethereum networks.
  • Participant roles: users/traders, LPs; Bittensor validators/infrastructure; liquidity providers/pools; operator(s) of the gateway infrastructure.
  • Where logic runs: onchain swaps/liquidity — on the Bittensor network (Native TAO); deposit/withdrawal — onchain on Ethereum; part of the routing/accounting of the gateway balance — offchain (per the gateway description in the docs).
  • Dependencies: Ethereum mainnet (deposits/withdrawals), the Bittensor network (trading), external charts (TradingView) and explorers (Etherscan) for address verification.

Token/economics (expanded, no forecasts)

  • Token utility: the docs describe a “planned utility”, including the intention to share protocol fees from future LSTs (the parameters are promised closer to the LST launch).
  • Who pays fees: per the docs there is a current transfer tax of 5%/5% (buy/sell) on the TAOBOT token; network fees are paid on the respective networks (Bittensor/Ethereum).
  • Where fees go: the tax is used for project development/support (per the docs); the tax is planned to be removed once protocol revenue from LSTs is up and running.
  • Issuance/burn: the supply is fixed, 100,000,000 TAOBOT, with no mint/burn (per the docs).
  • Distribution and token issuance schedule: the docs specify allocations and lock/vesting (LP lock; reserve lock+vesting; team lock; marketing unlock/lock events).

Governance

  • Who makes decisions: not established (no Tier‑1 description of governance was found; probably the team/product operator).
  • How protocol parameters change: — (no Tier‑1 update/voting process is described).
  • Where decisions are discussed/made: — (no Tier‑1 forum/repo/discussion process found).
  • Keys/multisig: — (no Tier‑1 information on keys/multisig found).

Security and incidents

  • Audits: — (no Tier‑1 audit reports found).
  • Bug bounty: — (no Tier‑1 bug bounty found).
  • Incidents: — (no Tier‑1 postmortems/incidents found).
  • Threat model: gateway risks (custody/accounting of the “hosted balance”), smart contract/integration risks, UI/phishing risks.

Project status and timeline

  • Current status: active (public website/docs + app).
  • Key releases/milestones: — (no Tier‑1 list of releases/milestones recorded).
  • Roadmap: — (no Tier‑1 roadmap/public backlog was found).

Ecosystem/integrations

  • Integrations: Bittensor (subnet token trading) + Ethereum gateway (deposit/withdrawal) — per the docs.
  • Partners: — (no Tier‑1 confirmed list of partners found).
  • Where it’s actually used: a terminal/screener and trading UI for users of the Bittensor ecosystem (per the description in the docs).

AI component of the project

  • What is real AI here? The TAO.BOT product has no declared AI module of its own; it is a trading/analytics interface for the Bittensor ecosystem.
  • What is truly onchain? Swaps/liquidity are executed on the Bittensor network (Native TAO); the gateway deposit/withdrawal and the TAOBOT token are on Ethereum.
  • Why is a token needed? TAOBOT is a utility token with described supply parameters and a claimed future utility (including revenue share from LSTs after launch).
  • Red flags (based on the information found): AI‑washing — high risk (association with an “AI ecosystem” without AI of its own); what to double‑check: the actual LST contracts/revenue share parameters after launch.

DecAI Fit component summary

  • DecAI Fit: 0/6 — no AI reality and no AI intent (ai_score=0)
Component Level Score
AI reality low 0
Onchain necessity medium 2
Token necessity medium 1
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No explicit “roadmap intentions” to introduce AI into TAO.BOT were found in the available docs.
  • Evidence: Tier‑1 — https://docs.tao.bot/home
  • Why sufficient / why not (one line): The documentation describes the product as a trading/analytics interface, with no AI roadmap.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): No AI functionality is declared (screener/swaps/liquidity/portfolio).
  • Evidence: Tier‑1 — https://docs.tao.bot/home ; https://docs.tao.bot/using-taobot
  • Why sufficient / why not (one line): The description of the product modules contains no AI component.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): The demo concerns trading/analytics, not AI functions.
  • Evidence: Tier‑1 — https://www.tao.bot/trade/swap
  • Why sufficient / why not (one line): There is no demonstration of AI results/models.
  • 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): There are no AI metrics, since no AI component is declared.
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): There is no technical description of an AI architecture (the product is not about AI).
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): There is no subject for a technical description of an AI part.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum (TAOBOT token), Bittensor (Native TAO mode)
  • Addresses/identifiers: TAOBOT ERC‑20 0x49fb8ad7578148E17c3eF0C344CE23A66ed372C4
  • Evidence: Tier‑1 — https://docs.tao.bot/taobot-token ; https://etherscan.io/token/0x49fb8ad7578148E17c3eF0C344CE23A66ed372C4
  • Why sufficient / why not (one line): The token address and network are specified in the official documentation and confirmed by the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: Swaps/liquidity and ownership of subnet tokens on the Bittensor network (Native TAO), deposit/withdrawal of assets on Ethereum (gateway).
  • Evidence: Tier‑1 — https://docs.tao.bot/home ; https://docs.tao.bot/using-taobot
  • Why sufficient / why not (one line): The product is tied to onchain activity (trading and liquidity management).
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: without onchain, swaps/LP cannot be done, but the UI itself could have been built for a centralized exchange — the criticality of the “blockchain” specifically for TAO.BOT as a product is not proven.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Onchain is important, but “impossibility without a blockchain” is not confirmed as fundamental.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, TAOBOT (ERC‑20).
  • Evidence: Tier‑1 — https://docs.tao.bot/taobot-token
  • Why sufficient / why not (one line): The official token page.
  • 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 with the token as a mandatory mechanism is not described.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The token docs describe taxes/planned utility, but not “pay‑to‑use”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): The 5%/5% transfer tax is declared as a mechanism for funding development; an intention of revenue share from LST fees is declared.
  • Evidence: Tier‑1 — https://docs.tao.bot/taobot-token
  • Why sufficient / why not (one line): This is an economic role of the token that goes beyond “just a payment”.
  • Conflict note (if any): The revenue share parameters are described as planned.

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance via TAOBOT is not confirmed.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The available docs contain no description of a DAO/voting.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): There is no proof that the product is impossible without the token (rather tokenomics/monetization).
  • Evidence: Tier‑1 — https://docs.tao.bot/taobot-token
  • Why sufficient / why not (one line): The utility is described as planned; the basic UI/trading function does not require a token of its own.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.tao.bot/home Product description: subnet screener, trading, operating modes (Native TAO / gateway).
Tier‑1 https://docs.tao.bot/using-taobot Details of the modules (Trade/Explore/Liquidity/Portfolio) and the gateway/Native TAO logic.
Tier‑1 https://docs.tao.bot/taobot-token TAOBOT token parameters (network, contract, supply, tax, planned utility).
Tier‑1 https://etherscan.io/token/0x49fb8ad7578148E17c3eF0C344CE23A66ed372C4 Confirmation of the TAOBOT token onchain contract on Ethereum.
Tier‑2 — —
Tier‑3 — —