Bottos
Bottos — 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).
Bottos — a project that, per Tier‑1 sources, describes itself as a public blockchain and “blockchain service layer / decentralized app platform”; token (symbol: BTO).
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 blockchain platform/service layer for dApps and a “data sharing network protocol” for the AI ecosystem (per the descriptions of the project’s repositories).
- Who it’s for: for dApp developers and users (per the meaning of the description).
- Why onchain/token: the blockchain is the foundation of the product; the ERC‑20 token BTO is confirmed (contract on Ethereum). The role of the token in the protocol/product is not confirmed by Tier‑1 (see Evidence).
How it works (very briefly)
- The user/developer does: deploys/uses a dApp based on the network (integration/SDK details are not confirmed by Tier‑1 in this card).
- The system does: executes public blockchain logic and provides a service layer for applications (per the repository descriptions).
- The user gets: access to dApp functionality.
- Where the blockchain is: the core of the product (network/explorer/code).
- Token role: not confirmed by Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Bottos |
| Also known as (aliases) | — |
| Logo (logo) | ../assets/685_bottos_logo.svg |
| Token symbol (ticker) | BTO |
| Category | Infra |
| Primary chain (chain) | Bottos |
| Type | Appchain |
| Network status | mainnet |
| Consensus (consensus) | — |
| Launch date (launch_date) | — |
| Project status (status) | — |
| Token (standard) | ERC-20 |
| Token contract | 0x36905fc93280f52362a1cbab151f25dc46742fb5 |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | Not confirmed by Tier‑1. |
| Governance | — |
| Admins/keys | — |
| Audit | — |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | — |
| Use‑case (use_case) | blockchain service layer for dApps |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 1 / 2 / 0 / 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.bottos.org/ |
| Docs | https://github.com/bottos-project/magiccube/blob/master/BottosWhitepaper_EN.pdf |
| GitHub | https://github.com/Bottos-project |
| Releases / Changelog | https://github.com/bottos-project/bottos/releases |
| Whitepaper | https://github.com/bottos-project/magiccube/blob/master/BottosWhitepaper_EN.pdf |
| Roadmap | — |
| Security advisories | https://github.com/bottos-project/magiccube/security |
| Explorer | http://explorer.chainbottos.com/#/home |
| X | https://twitter.com/ai_bottos |
| Discord | — |
| Telegram | https://t.me/bottosofficial |
| Medium | https://medium.com/bottos |
| Audit report(s) | — |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/bottos |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/bottos/ |
General project overview
Per Tier‑1 sources (GitHub), the project describes itself as a public blockchain and a service layer for dApps, as well as a protocol/platform for data sharing in the AI ecosystem (DataMarket/ModelMarket in the repository’s wording). However, the role of the BTO token in the protocol/product is not confirmed per the available Tier‑1 sources.
A separate source risk: the domain bottos.org, listed in the repository as “official website / develop doc”, serves irrelevant content at the time of the check. We therefore rely on Tier‑1 artifacts from GitHub and onchain facts about the token.
Features/modules
magiccube— “Bottos Blockchain Service Layer, Decentralized App Platform” (per the repository description).bottos— “public blockchain” (per the repository description).BlockExplorer— the network explorer (per the repository description).
Typical scenarios
- Scenario 1: a developer deploys/uses a dApp → the network executes transactions/logic → a user interacts with the dApp (details are not confirmed by Tier‑1 in this card).
Getting started (wallet/network)
- What you need: source code/instructions from the official repositories (Tier‑1).
- Network/chain: Bottos (per the explorer link).
- Fees: fees/the payment model on the Bottos network are not confirmed by Tier‑1 in this card; standard Ethereum network fees apply to the ERC‑20 token.
Architecture/tech (non‑AI)
- Components: blockchain code, an SDK/client for data sharing, an explorer (per GitHub).
- Participant roles: network participants (details are not established).
- Where logic runs: onchain on its own network; details are not confirmed by Tier‑1 in this card.
- Dependencies: not confirmed by Tier‑1.
Token/economics (expanded, no forecasts)
- Token utility: not confirmed by Tier‑1.
- Protocol necessity drivers: not confirmed by Tier‑1.
- Who pays fees: Ethereum network fees are paid by senders of BTO token transactions; fees/payments on the Bottos network are not confirmed by Tier‑1 in this card.
- Where fees go: to the Ethereum network validators (standard gas logic) for operations with the ERC‑20 token.
- Issuance/burn: not confirmed by Tier‑1.
- Security/incentive mechanisms: not confirmed by Tier‑1.
- Distribution and token issuance schedule: not confirmed by Tier‑1.
- Treasury: not confirmed by Tier‑1.
Governance
- Who makes decisions: not confirmed by Tier‑1.
- How protocol parameters change: not confirmed by Tier‑1.
- Where decisions are discussed/made: not confirmed by Tier‑1.
- Keys/multisig: not confirmed by Tier‑1.
Security and incidents
- Audits: not confirmed by Tier‑1.
- Bug bounty: not confirmed by Tier‑1.
- Incidents: not confirmed by Tier‑1.
- Threat model: not confirmed by Tier‑1.
Project status and timeline
- Current status: not confirmed by Tier‑1.
- Key releases/milestones: not confirmed by Tier‑1.
- Roadmap: No Tier‑1 roadmap found.
Ecosystem/integrations
- Integrations: not confirmed by Tier‑1.
- Partners: not confirmed by Tier‑1.
- Where it’s actually used: not confirmed by Tier‑1.
AI component of the project
- What is real AI here? Tier‑1 sources describe intent: “infrastructure for AI development” and services/data/model markets for the AI ecosystem; no Tier‑1 confirmation of a working AI component (model/metrics/demo) was found.
- What is truly onchain? Its own network with an explorer and public repositories of the blockchain/platform (per GitHub).
- Why is a token needed? Not confirmed by Tier‑1 (there is no Tier‑1 description of the role of the token in the protocol/product).
- Red flags (based on the information found): the absence of Tier‑1 tokenomics/governance parameters; double‑check the existence/role of the token and whether the network is still current.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | medium | 2 |
| Token necessity | low | 0 |
| Evidence | Tier‑1 present | 2 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 1
- Claim (one line): In Tier‑1 sources, the project claims intent: “infrastructure for AI development” and elements of an AI ecosystem (data/model sharing).
- Evidence: Tier‑1 — https://raw.githubusercontent.com/bottos-project/bottos/master/README.md ; https://raw.githubusercontent.com/bottos-project/magiccube/master/README.md
- Why sufficient / why not (one line): this is a Tier‑1 declaration of intent/applicability to AI, without proof of a working AI component (AI_1..AI_4 remain 0).
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): No Tier‑1 confirmation of an AI component was found.
- Evidence: Tier‑1 — https://github.com/Bottos-project
- Why sufficient / why not (one line): AI functionality is not established.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No demo of an AI component was found (an AI component is not established).
- Evidence: Tier‑1 — https://github.com/Bottos-project
- Why sufficient / why not (one line): there is no subject of AI verification.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: not found (an AI component is not established).
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://github.com/Bottos-project
- Why sufficient / why not (one line): AI metrics are absent.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): No Tier‑1 tech description of an AI component was found (the AI component is not established).
- Evidence: Tier‑1 — https://github.com/bottos-project/magiccube/blob/master/BottosWhitepaper_EN.pdf
- Why sufficient / why not (one line): there is no tech description of the AI component.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Bottos
- Addresses/identifiers: the network explorer (per the link) + public blockchain repositories.
- Evidence: Tier‑1 — http://explorer.chainbottos.com/#/home ; Tier‑1 — https://github.com/bottos-project/bottos
- Why sufficient / why not (one line): there is an explorer and source code for the public blockchain.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- What useful logic is onchain: the product is its own network/platform for dApps (per the repository descriptions).
- Evidence: Tier‑1 — https://github.com/bottos-project/magiccube ; Tier‑1 — https://github.com/bottos-project/bottos
- Why sufficient / why not (one line): Tier‑1 repository descriptions point to a blockchain platform that is not limited to a token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: onchain criticality is not justified in Tier‑1.
- Evidence: Tier‑1 — https://github.com/bottos-project/magiccube/blob/master/BottosWhitepaper_EN.pdf
- Why sufficient / why not (one line): there is no operational justification of OC_3.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has an ERC‑20 token, BTO (contract on Ethereum).
- Evidence: Tier‑1 — https://etherscan.io/address/0x36905fc93280f52362a1cbab151f25dc46742fb5
- Why sufficient / why not (one line): the onchain artifact confirms the existence of the token.
- 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): No Tier‑1 confirmation of payment for a specific service with the token was found.
- Evidence: Tier‑1 — https://github.com/bottos-project/bottos ; https://github.com/bottos-project/magiccube
- Why sufficient / why not (one line): insufficient data.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Tier‑1 mechanics of incentives/collateral/penalties via the token in the protocol are not confirmed.
- Evidence: Tier‑1 — https://github.com/bottos-project/bottos ; https://github.com/bottos-project/magiccube
- Why sufficient / why not (one line): insufficient data.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 0
- Claim (one line): No Tier‑1 confirmation of the governance role of the token was found.
- Evidence: Tier‑1 — https://github.com/bottos-project/bottos ; https://github.com/bottos-project/magiccube
- Why sufficient / why not (one line): insufficient data.
- 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 confirmed by Tier‑1.
- Evidence: Tier‑1 — https://github.com/bottos-project/bottos ; https://github.com/bottos-project/magiccube
- Why sufficient / why not (one line): there is no argumentation.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://github.com/bottos-project/magiccube | Repository description: “Blockchain Service Layer, Decentralized App Platform”. |
| Tier‑1 | https://github.com/bottos-project/bottos | Repository description: “public blockchain”. |
| Tier‑1 | http://explorer.chainbottos.com/#/home | The existence of a network explorer. |
| Tier‑1 | https://github.com/bottos-project/magiccube/blob/master/BottosWhitepaper_EN.pdf | Whitepaper (Tier‑1 document). |
| Tier‑1 | https://raw.githubusercontent.com/bottos-project/bottos/master/README.md | AI‑intent: “infrastructure for AI development … decentralized AI ecosystem”. |
| Tier‑1 | https://raw.githubusercontent.com/bottos-project/magiccube/master/README.md | Description of the protocol as a data sharing network for the AI ecosystem (DataMarket/ModelMarket goals). |
| Tier‑1 | https://etherscan.io/address/0x36905fc93280f52362a1cbab151f25dc46742fb5 | Onchain artifact: ERC‑20 token BTO (contract on Ethereum). |
| Tier‑1 | https://www.bottos.org/ | At the time of the check, the domain serves irrelevant content (a conflict with the “official website” claim in the repository). |
| Tier‑1 | — | No Tier‑1 source for claim “role of the token in the protocol (TK_1..TK_3)” was found. |
No comments to display
No comments to display