Ooki Protocol
Ooki Protocol — 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).
Ooki Protocol — a DeFi project on the Ethereum network, token (symbol: OOKI).
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 DeFi project (per the metadata/documentation in links_*).
- Who it’s for: DeFi users.
- Why onchain/token: the OOKI token (ERC‑20) exists on Ethereum; the Tier‑1 docs describe DAO governance with voting via OOKI (through staking/voting weight).
How it works (very briefly)
- The user does: uses the protocol/application (details — in the project documentation).
- The system does: performs DeFi operations on smart contracts (confirmation per Tier‑1 is required).
- The user gets: the result of the operation (a loan/trading/returns — depending on the product; not detailed in this card per Tier‑1 sources).
- Where the blockchain is: the OOKI ERC‑20 token on Ethereum; the rest of the onchain part requires confirmation per Tier‑1.
- Token role (if any): OOKI (ERC‑20); per the Tier‑1 docs, the token is used for governance (voting through staking/weight).
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Ooki Protocol |
| Also known as (aliases) | OOKI |
| Logo (logo) | ../assets/740_ooki-protocol_logo.svg |
| Token symbol (ticker) | OOKI |
| Category | DeFi |
| Primary chain (chain) | Ethereum |
| Type | EVM |
| Network status | mainnet |
| Consensus (consensus) | PoS (Ethereum) |
| Launch date (launch_date) | — |
| Project status (status) | active |
| Token (standard) | ERC-20 |
| Token contract | 0x0De05F6447ab4D22c8827449EE4bA2D5C288379B |
| Token model (token_type) | utility (governance) |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | DAO (onchain governance) |
| Admins/keys | — |
| Audit | yes |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | — |
| Use‑case (use_case) | DeFi protocol |
| DecAI Fit — AI thesis fit | 0/6 — no AI reality and no AI intent (ai_score=0) |
| DecAI Fit component summary | ai_score 0 / onchain_score 1 / token_score 1 / evidence_score 2 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://ooki.cc |
| Docs | https://ooki.gitbook.io/ |
| GitHub | https://github.com/OokiTrade |
| Releases / Changelog | https://github.com/OokiTrade/contractsV2/commits |
| Whitepaper | — |
| Roadmap | — |
| Security advisories | https://github.com/OokiTrade/contractsV2/security |
| Explorer | https://etherscan.io/token/0x0De05F6447ab4D22c8827449EE4bA2D5C288379B |
| X | https://twitter.com/ookitrade |
| Discord | https://www.discord.gg/erBFNhjvyr |
| Telegram | https://t.me/OokiAnnouncements |
| Medium | — |
| Audit report(s) | https://code4rena.com/reports/2022-02-ooki |
| Bug bounty | — |
| CoinGecko (profile, reference) | https://www.coingecko.com/en/coins/ooki |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/ooki-protocol/ |
General project overview
Ooki Protocol is recorded conservatively within this card: the website/documentation/repositories and the OOKI token on Ethereum are available via Tier‑1 links. No Tier‑1 confirmation of an AI component was found; therefore, per SSOT, ai_score = 0 and DecAI Fit = 0/6.
Features/modules
- DeFi features of the protocol: see the official documentation in links_* (details are not detailed in this card per Tier‑1 sources).
Typical scenarios
- Scenario 1: a user studies the documentation → uses the protocol/application → gets the result of the operation (not detailed in this card per Tier‑1).
- Scenario 2: a user interacts with the OOKI token → transactions are observable in the Ethereum explorer.
Getting started (wallet/network)
- What you need: a wallet for EVM networks and access to the documentation/application (if available).
- Network/chain: Ethereum (for the token).
- Fees: Ethereum network fees for token/contract transactions.
Architecture/tech (non‑AI)
- Components: the OOKI token (ERC‑20) and the protocol smart contracts (see the official documentation for details).
- Participant roles: protocol users and token holders.
- Where logic runs: the token and contracts — onchain (Ethereum); protocol details — in the documentation.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not detailed in this card per Tier‑1 (a Tier‑1 description of the mechanics is needed).
- Who pays fees: the transaction sender (Ethereum gas).
- Issuance/burn: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
Security and incidents
- Audits: there is a link to a report/audit (see links_*).
- Bug bounty: —.
- Incidents: —.
- Threat model: DeFi contract risks; details are not detailed in this card per Tier‑1.
Project status and timeline
- Current status: mainnet (the token on Ethereum).
- Key releases/milestones: see commits in links_* (Releases/Changelog).
- Roadmap: —.
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? an AI component is not established per Tier‑1 sources.
- What is truly onchain? the OOKI token (ERC‑20) on Ethereum; the rest of the onchain logic requires confirmation per Tier‑1 documentation.
- Why is a token needed? the role of the token as a mandatory mechanism of the product is not detailed in this card per Tier‑1.
- Red flags (based on the information found): AI labels in third‑party sources without Tier‑1 confirmation; the absence of an explicit connection between AI and the product.
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 | low | 1 |
| Token necessity | low | 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 Tier‑1 claim/roadmap about AI was found.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): Without a Tier‑1 declaration of AI intentions, we set 0 (conservatively).
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 0
- Claim (one line): What exactly the AI component does is not established per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 description of an AI feature.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): No demo of the AI part was found per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There is no Tier‑1 confirmation of an AI feature, so a demo is not applicable.
- 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 is no Tier‑1 confirmation of the AI part and, accordingly, metrics.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): No tech description of the AI part was found per Tier‑1.
- Evidence: Tier‑1 — —
- Why sufficient / why not (one line): There are no grounds for 1.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: token contract 0x0De05F6447ab4D22c8827449EE4bA2D5C288379B
- Evidence: Tier‑1 — https://etherscan.io/token/0x0De05F6447ab4D22c8827449EE4bA2D5C288379B
- Why sufficient / why not (one line): The existence of the token and an observable contract in the explorer confirms an onchain artifact.
- Conflict note (if any): —
OC_2 — onchain beyond just a token (1/0)
- OC_2 (decision): 0
- What useful logic is onchain: Tier‑1 confirmation of onchain logic of the protocol (other than the token) is not provided in this card.
- Evidence: Tier‑1 — https://ooki.gitbook.io/
- Why sufficient / why not (one line): 1 requires addresses/a description of specific contracts and their role.
- 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 this card per Tier‑1 sources.
- Evidence: Tier‑1 — https://ooki.gitbook.io/
- Why sufficient / why not (one line): There is no Tier‑1 justification of onchain criticality.
- Conflict note (if any): —
Token necessity
TK_0 — no token (1/0)
- TK_0 (decision): 0
- Claim (one line): The project has a token, OOKI (ERC‑20).
- Evidence: Tier‑1 — https://etherscan.io/token/0x0De05F6447ab4D22c8827449EE4bA2D5C288379B
- Why sufficient / why not (one line): The token and its contract are observable in the Tier‑1 explorer.
- 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): The use of the token as a mandatory payment for the service is not established per Tier‑1.
- Evidence: Tier‑1 — https://ooki.gitbook.io/
- Why sufficient / why not (one line): 1 requires an explicit payment mechanism via the token.
- Conflict note (if any): —
TK_2 — incentives/collateral/penalties (1/0)
- TK_2 (decision): 0
- Claim (one line): Mechanisms of incentives/collateral/penalties with the token are not established per Tier‑1.
- Evidence: Tier‑1 — https://ooki.gitbook.io/
- Why sufficient / why not (one line): Specific rules/contracts/documentation are needed.
- Conflict note (if any): —
TK_3 — governance (1/0)
- TK_3 (decision): 1
- Claim (one line): The Tier‑1 documentation describes DAO governance with voting via OOKI and voting power requirements (through staking).
- Evidence: Tier‑1 — https://ooki.gitbook.io/ooki/governance/dao-governance
- Why sufficient / why not (one line): This is a direct Tier‑1 description of the governance mechanics and the role of the token in voting.
- Conflict note (if any): —
TK_4 — token is replaceable (1/0)
- TK_4 (decision): 0
- Claim (one line): The replaceability of the token without loss of meaning is not established per Tier‑1.
- Evidence: Tier‑1 — https://ooki.gitbook.io/
- Why sufficient / why not (one line): There is insufficient data on the role of the token in the product.
- Conflict note (if any): —
Evidence (table)
| Tier | Source | What it proves |
|---|---|---|
| Tier‑1 | — | No Tier‑1 source for claim “the project has an AI component” was found. |
| Tier‑1 | https://etherscan.io/token/0x0De05F6447ab4D22c8827449EE4bA2D5C288379B | The existence of the OOKI ERC‑20 token on Ethereum (contract/network). |
| Tier‑1 | https://ooki.gitbook.io/ | Official project documentation (context and claimed functionality). |
| Tier‑1 | https://ooki.gitbook.io/ooki/governance/dao-governance | A description of DAO governance (snapshot + onchain ratification) and voting via OOKI (voting power/staking). |
| Tier‑1 | https://code4rena.com/reports/2022-02-ooki | Public report/audit (Tier‑1 link in links_*). |
| Tier‑2 | https://www.coingecko.com/en/coins/ooki | Token profile on an aggregator (context; not proof). |
| Tier‑3 | https://coinmarketcap.com/currencies/ooki-protocol/ | Token profile on an aggregator (context; not proof). |
No comments to display
No comments to display