Skip to main content

Roobee

Roobee (ROOBEE) — 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).

Roobee is described in the available Tier‑1 sources as an ecosystem/community around the ROOBEE token and a set of DeFi scenarios, including Roobee DAO (on BNB Chain via a separate token, bROOBEE).

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: the ROOBEE token and multichain infrastructure for use in DeFi and for voting/staking in Roobee DAO.
  • Who it’s for: token holders and participants in DeFi/DAO activities.
  • Why onchain/token: onchain is needed for token ownership/transfers and DAO mechanics; in the Tier‑1 documentation available in this card, a verifiable AI module is not confirmed, so ai_score=0.

How it works (very briefly)

  1. The user does: holds ROOBEE and/or participates in DeFi applications.
  2. The system does: provides multichain access to ROOBEE (bridge transfer of part of the supply) and a separate DAO mechanic on BNB Chain via bROOBEE.
  3. The user gets: participation in voting/staking and use of the token in DeFi.
  4. Where the blockchain is: Ethereum (ROOBEE ERC‑20) and BNB Chain (including bROOBEE) + other networks (per the docs).
  5. Token role: ROOBEE — the main token; bROOBEE — the token for DAO voting/staking on BNB Chain.

Quick links: AI thesis fit

Project passport

Field Value
Project name Roobee
Also known as (aliases) ROOBEE; Roobee DAO
Logo (logo) ../assets/296_roobee_logo.svg
Token symbol (ticker) ROOBEE
Category DeFi | DAO tooling
Primary chain (chain) Ethereum
Type EVM
Network status mainnet
Consensus (consensus) PoS (Ethereum)
Launch date (launch_date) —
Project status (status) active (docs + token)
Token (standard) ERC-20
Token contract ROOBEE (Ethereum): 0xa31b1767e09f842ecfd4bc471fe44f830e3891aa
Token model (token_type) utility (governance)
Max supply 5,400,000,000 ROOBEE (Etherscan Max Total Supply)
Issuance fixed max total supply (per Etherscan)
Tokenomics (tokenomics, brief) part of ROOBEE was locked in the Ethereum contract and transferred to BNB/Polygon/Avalanche/Optimism/Arbitrum (per the docs)
Governance Roobee DAO (per the docs)
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) unknown
Use‑case (use_case) multichain token + DAO voting/staking
DecAI Fit — AI thesis fit 0/6 — no AI reality and no AI intent (ai_score=0)
DecAI Fit component summary 0 / 2 / 2 / 2
Last verified 2026-02-11

General project overview

In “Key information” (GitBook), ROOBEE is described as the project’s main token, which is used in the community and in “various DeFi apps”, as well as a means of participating in the project’s development via Roobee DAO voting. The same source lists the token’s smart contract addresses by network and separately states that bROOBEE is used on Roobee DAO (BNB Chain) for voting and staking (with a mention of APR).

AI component of the project

  • What is real AI here? The Tier‑1 documentation available in this card (Key information) contains no description of an AI module (model/tasks/demo/metrics). Therefore ai_score=0.
  • What is truly onchain? ROOBEE ERC‑20 on Ethereum, as well as DAO voting/staking via bROOBEE on BNB Chain.
  • Why is a token needed? It is used for DeFi scenarios and governance/staking in the DAO.

DecAI Fit component summary

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

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): No Tier‑1 declaration of AI intent/roadmap was found.
  • Evidence: Tier‑1 — https://roobee.io/docs/whitepaper_en.pdf
  • Why sufficient / why not (one line): The available sources describe the token/DAO, without an AI plan.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 0
  • Claim (one line): No Tier‑1 description of AI features/models in the product was found.
  • Evidence: Tier‑1 — https://roobee.io/docs/whitepaper_en.pdf
  • Why sufficient / why not (one line): The documents contain no AI module as a product component.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 0
  • Claim (one line): No Tier‑1 demos/examples of the AI component in operation were found (the AI component is not described).
  • Evidence: Tier‑1 — https://roobee.io/docs/whitepaper_en.pdf
  • Why sufficient / why not (one line): The presence of a token/DAO is not an AI demo.
  • Conflict note (if any): —

AI_3 — metrics/quality (1/0)

  • AI_3 (decision): 0
  • Metrics: —.
  • Context (version/date/how measured): —.
  • Evidence: Tier‑1 — https://roobee.io/docs/whitepaper_en.pdf
  • Why sufficient / why not (one line): AI quality metrics are absent (the AI part is not claimed).
  • Conflict note (if any): —

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

  • AI_4 (decision): 0
  • Claim (one line): No technical description of the AI architecture/model versions was found in Tier‑1.
  • Evidence: Tier‑1 — https://roobee.io/docs/whitepaper_en.pdf
  • Why sufficient / why not (one line): The documents focus on the token/DAO, without an AI architecture.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: ROOBEE (ERC‑20) — 0xa31b1767e09f842ecfd4bc471fe44f830e3891aa
  • Evidence: Tier‑1 — https://etherscan.io/token/0xa31b1767e09f842ecfd4bc471fe44f830e3891aa
  • Why sufficient / why not (one line): The token address and parameters are verifiable via the explorer.
  • Conflict note (if any): —

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

  • OC_2 (decision): 1
  • What useful logic is onchain: DAO mechanics (voting/staking) via bROOBEE on BNB Chain (per the documentation).
  • Evidence: Tier‑1 — https://roobee.io/docs/whitepaper_en.pdf
  • Why sufficient / why not (one line): Tier‑1 describes DAO scenarios beyond the basic ERC‑20.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: per Tier‑1, it is not substantiated that without the blockchain a key property of the product breaks down.
  • Evidence: Tier‑1 — https://roobee.io/docs/whitepaper_en.pdf
  • Why sufficient / why not (one line): There are onchain components (token/DAO), but “criticality” is not formalized.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The project has a token, ROOBEE (ERC‑20).
  • Evidence: Tier‑1 — https://etherscan.io/token/0xa31b1767e09f842ecfd4bc471fe44f830e3891aa
  • Why sufficient / why not (one line): The token is confirmed onchain.
  • 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 services/access with the ROOBEE token is not confirmed per Tier‑1.
  • Evidence: Tier‑1 — https://roobee.io/docs/whitepaper_en.pdf
  • Why sufficient / why not (one line): The documentation describes DeFi/DAO scenarios, without an explicit paywall scheme “pay ROOBEE → get access”.
  • Conflict note (if any): —

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

  • TK_2 (decision): 1
  • Claim (one line): The documentation describes staking/rewards mechanics in the context of Roobee DAO (bROOBEE).
  • Evidence: Tier‑1 — https://roobee.io/docs/whitepaper_en.pdf
  • Why sufficient / why not (one line): Staking/rewards are participation incentives.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 1
  • Claim (one line): Governance/voting via Roobee DAO is described in the Tier‑1 documentation.
  • Evidence: Tier‑1 — https://roobee.io/docs/whitepaper_en.pdf
  • Why sufficient / why not (one line): DAO voting is mentioned.
  • 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 established per Tier‑1.
  • Evidence: Tier‑1 — https://roobee.io/docs/whitepaper_en.pdf
  • Why sufficient / why not (one line): A conclusion on replaceability requires a separate comparison with alternatives.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://roobee.io/docs/whitepaper_en.pdf Multichain addresses of the token and the description of bROOBEE for voting/staking in Roobee DAO.
Tier‑1 https://etherscan.io/token/0xa31b1767e09f842ecfd4bc471fe44f830e3891aa The ROOBEE contract and max total supply 5.4B.