oooo
oooo (oooo) — 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).
oooo — an omnichain interoperability protocol (focused on the Bitcoin ecosystem per the docs); the documentation claims an AI Omninet layer for “intelligent” cross‑chain operations; token: oooo.
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 protocol/service for cross‑chain intents and omnichain interactions (bridge/messages between networks).
- Who it’s for: users and dApps that need cross‑chain operations; integrators and developers.
- Why onchain/token: onchain is needed for the “endpoints” smart contracts and the execution of operations between networks; the token is claimed for governance, staking/revenue share and fee discounts.
How it works (very briefly)
- The user does: specifies a cross‑chain operation (transfer/liq/yield, etc.) via the interface/an intent.
- The system does: validates/encrypts the message on the source network, passes it via the “Omni‑Bus”, verifies it via the “Verifier Network”, and delivers it to the target network.
- The user gets: the executed cross‑chain operation.
- Where the blockchain is: “endpoints” as smart contracts on the networks; onchain state/events of operations.
- Token role (if any): governance, staking & revenue sharing, fee discounts, access to “premium” features (per the tokenomics).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | oooo |
| Also known as (aliases) | oooo Protocol, oooo money, AI Omninet |
| Logo (logo) | — |
| Token symbol (ticker) | oooo |
| Category | AI/Agents | Interop/Bridge |
| Primary chain (chain) | BNB Smart Chain |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoSA (BNB Smart Chain; 21 validators) |
| Launch date (launch_date) | 2024 (roadmap: launch in Q1 2024) |
| Project status (status) | active (website/docs available) |
| Token (standard) | BEP-20 |
| Token contract | 0xf0a28bddac9d3045c95bf57df033e80685d881c0 |
| Token model (token_type) | utility (governance + staking + revshare + fee discounts) |
| Max supply | 1,000,000,000 oooo (BscScan / docs tokenomics) |
| Issuance | fixed total supply (per the tokenomics) |
| Tokenomics (tokenomics, brief) | distribution: community/ecosystem, airdrops, investors, team, liquidity, treasury, marketing (docs) |
| Governance | governance via the token is claimed (mechanics/snapshot/contracts — not confirmed in the links of this card) |
| Admins/keys | — |
| Audit | there is a report in the audit GitHub repository (see links) |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | investors are allocated a share in the tokenomics (round details — not in the links of this card) |
| AI component (ai_component) | AI assistant for cross-chain intents |
| Use‑case (use_case) | cross-chain interoperability + intents |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | 1 / 2 / 2 / 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://oooo.money/ |
| Docs | https://docs.oooo.money/ |
| GitHub | https://github.com/oooo-protocol |
| Releases / Changelog | — |
| Whitepaper | https://oooo.money/whitepaper |
| Roadmap | https://oooo.money/ |
| Security advisories | — |
| Explorer | https://bscscan.com/token/0xf0a28bddac9d3045c95bf57df033e80685d881c0 |
| X | https://twitter.com/oooo_money |
| Discord | — |
| Telegram | — |
| Medium | — |
| Audit report(s) | https://github.com/oooo-protocol/oooo-protocol-audit/blob/main/ScaleBit_Audit_Report_for_bridge.oooo.money.pdf |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/oooo |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/oooo/ |
General project overview
oooo describes itself as a modular omnichain interoperability protocol oriented toward the Bitcoin ecosystem. The documentation describes components for delivering messages between networks (endpoints, verifier network, omni‑bus) and a separate AI Omninet layer, which is positioned as an “intelligent assistant” for executing cross‑chain intents and optimizing routes.
Features/modules
- message delivery between chains (endpoints + verification + bus).
- modular architecture (verifier network, omni‑bus, event listener).
- AI Omninet (claim): understanding user intents and optimizing routes/liquidity.
Typical scenarios
- Scenario 1: a user initiates a cross‑chain operation → the message passes validation/encryption → delivery and execution on the target chain.
- Scenario 2: a user specifies an “intent” in the form of a command → AI Omninet (claim) chooses the optimal path by liquidity/security.
Getting started (wallet/network)
- What you need: an EVM wallet; interaction via the project’s interfaces.
- Network/chain: an omnichain protocol; the token — on BNB Smart Chain (contract in the explorer).
- Fees: network fees for transactions.
Architecture/tech (non‑AI)
Per the docs:
- Endpoints: smart contracts on the networks through which dApps initiate and receive messages.
- Security Checker + Encryptor/Decryptor: verification/encryption of messages on the source/target side.
- Decentralized Omni‑Bus: message transport.
- Modular Verifier Network: modular verification of correctness/integrity.
Token/economics (expanded, no forecasts)
Per the tokenomics:
- Governance: token holders can propose and vote on parameters/integrations/the treasury (claim).
- Staking & revenue sharing: staking for a share of the protocol revenue (claim).
- Fee discounts / premium access / incentive boost: discounts, access, boosted rewards (claim).
- Distribution: investors 12.7%, airdrops 21.3%, team 15%, liquidity 10%, ecosystem 23%, treasury 17%, marketing 1%.
Governance
- Who makes decisions: governance via the token is claimed, but the specific contracts/voting process are not recorded in the links of this card.
Security and incidents
- Audits: an audit report on the bridge is published on GitHub (a PDF in the audit repository).
- Bug bounty: —.
Project status and timeline
- Current status: the website/docs are available; the modular architecture and AI Omninet are described (docs).
AI component of the project
- What is real AI here? In the docs, AI Omninet is claimed as an “intelligent assistant” for understanding intents and optimizing cross‑chain operations (routes, liquidity, strategies) — this is a description of functionality at the level of intents/behavior.
- What is truly onchain? Message delivery between networks via endpoint contracts and the protocol infrastructure; the existence of the token and its contract on the network.
- Why is a token needed? The tokenomics claim governance, staking/revenue sharing, fee discounts, access to premium features.
- Red flags (based on the information found): AI‑washing risk — there are no demos/metrics/model/versions in Tier‑1; the onchain part is described architecturally, but without a list of endpoint/bridge contract addresses in the docs; double‑check the addresses of the protocol’s working contracts, apart from the token.
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 | medium | 2 |
| Evidence | Tier‑1 present | 3 |
Details
AI reality
AI_0 — AI intent (Tier‑1 roadmap) (1/0)
- AI_0 (decision): 0
- Claim (one line): AI Omninet is described as a protocol layer, but this is not a separate roadmap declaration “we plan AI” without a description of how it works.
- Evidence: Tier‑1 — https://docs.oooo.money/what-is-oooo/introducing-ai-omninet/ai-omninet-the-intelligent-assistant
- Why sufficient / why not (one line): AI is described as a component of the product, so we do not apply the “intent flag”; we assess per AI_1.
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): AI Omninet “understands intentions” (intents) and automatically executes cross‑chain operations and route optimization (claim).
- Evidence: Tier‑1 — https://docs.oooo.money/what-is-oooo/introducing-ai-omninet/ai-omninet-the-intelligent-assistant
- Why sufficient / why not (one line): the Tier‑1 docs describe the functions of the AI layer (although without implementation details).
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): no verifiable demos/examples of “input → output” for AI Omninet were found in the Tier‑1 documentation.
- Evidence: Tier‑1 — https://docs.oooo.money/what-is-oooo/introducing-ai-omninet/ai-omninet-the-intelligent-assistant
- Why sufficient / why not (one line): there is a description, but no demonstration artifacts.
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: —
- Why sufficient / why not (one line): there are no benchmarks/quality metrics for the AI decisions.
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): Tier‑1 contains only a high‑level “architecture breakdown” without information on models/versions/algorithms sufficient for a technical check.
- Evidence: Tier‑1 — https://docs.oooo.money/what-is-oooo/introducing-ai-omninet/the-architecture-of-ai-omninet
- Why sufficient / why not (one line): the architecture is described conceptually, without technical details of the AI implementation.
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: BNB Smart Chain (per the token)
- Addresses/identifiers: oooo token: 0xf0a28bddac9d3045c95bf57df033e80685d881c0
- Evidence: Tier‑1 — https://bscscan.com/token/0xf0a28bddac9d3045c95bf57df033e80685d881c0
- Why sufficient / why not (one line): the onchain fact of the token and max supply is verifiable via the explorer.
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 1
- Claim (one line): in the docs, endpoints are described as smart contracts for message delivery and dApp interaction.
- Evidence: Tier‑1 — https://docs.oooo.money/what-is-oooo/modular-architecture ; https://docs.oooo.money/what-is-oooo/message-delivery-with-oooo
- Why sufficient / why not (one line): Tier‑1 asserts the existence of onchain protocol components beyond the token.
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- Claim (one line): the sources contain no strict argument that without a blockchain the product “breaks down” (a centralized router/bridge can be built).
- Evidence: Tier‑1 — https://docs.oooo.money/what-is-oooo/message-delivery-with-oooo
- Why sufficient / why not (one line): the criticality of onchain is not justified via the “replace the blockchain” test.
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Evidence: Tier‑1 — https://bscscan.com/token/0xf0a28bddac9d3045c95bf57df033e80685d881c0
TK_1 — payment for the service (1/0)
- TK_1 (decision): 0
- Claim (one line): the tokenomics do not state that protocol fees are paid specifically in the oooo token.
- Evidence: Tier‑1 — https://docs.oooo.money/tokenomics
- Why sufficient / why not (one line): fee discounts are described, but not “payment for the service with the token”.
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 1
- Claim (one line): staking the token provides a share of “real revenue” and a rewards boost (claim).
- Evidence: Tier‑1 — https://docs.oooo.money/tokenomics
- Why sufficient / why not (one line): the utility explicitly includes staking & revenue sharing.
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): governance is claimed as a utility: proposals and votes on protocol decisions (claim).
- Evidence: Tier‑1 — https://docs.oooo.money/tokenomics
- Why sufficient / why not (one line): the tokenomics directly describe the governance role of the token.
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): in the tokenomics, the token is positioned as the “heart of the protocol” (governance/staking/access); the sources do not assert replaceability without loss of meaning.
- Evidence: Tier‑1 — https://docs.oooo.money/tokenomics
- Why sufficient / why not (one line): a functional role of the token within the economic model is claimed.
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | https://docs.oooo.money/ | Official documentation of the protocol. |
| Tier‑1 | https://docs.oooo.money/what-is-oooo/modular-architecture | The existence of onchain endpoints and modular protocol components (claim). |
| Tier‑1 | https://docs.oooo.money/what-is-oooo/message-delivery-with-oooo | The message delivery process (architectural description). |
| Tier‑1 | https://docs.oooo.money/what-is-oooo/introducing-ai-omninet/ai-omninet-the-intelligent-assistant | Description of AI Omninet functions (claim). |
| Tier‑1 | https://docs.oooo.money/what-is-oooo/introducing-ai-omninet/the-architecture-of-ai-omninet | High‑level architecture of AI Omninet. |
| Tier‑1 | https://docs.oooo.money/tokenomics | Total supply, distribution, token utility (claim). |
| Tier‑1 | https://bscscan.com/token/0xf0a28bddac9d3045c95bf57df033e80685d881c0 | Token contract and max total supply on the network. |
| Tier‑1 | https://github.com/oooo-protocol | Official repositories of the project. |
| Tier‑1 | https://github.com/oooo-protocol/oooo-protocol-audit/blob/main/ScaleBit_Audit_Report_for_bridge.oooo.money.pdf | Public audit document (PDF). |
No comments to display
No comments to display