Ojamu
Ojamu — 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).
Ojamu — an AI/Other | Infra project on the Ethereum network, token (symbol: OJA).
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 project that describes itself as an AI & Blockchain‑powered platform for brand intelligence/marketing in Web3.
- Who it’s for: brands/marketing teams and Web3 projects that need data/insights/recommendations.
- Why onchain/token: the confirmed onchain artifact is the OJA ERC‑20 token on Ethereum; the criticality of onchain for the product is not established per Tier‑1.
How it works (very briefly)
- The user does: uses the Ojamu platform/tools (per the description on the website).
- The system does: analyzes data and delivers insights/recommendations claimed to be AI/ML‑powered.
- The user gets: conclusions for marketing/positioning in Web3 (details — in the project documents).
- Where the blockchain is: the confirmed onchain element is an ERC‑20 token on Ethereum.
- Token role (if any): OJA (ERC‑20); the utility of the token as a mandatory protocol mechanism is not established per Tier‑1.
Quick links: AI thesis fit
Project passport
| Field | Value |
|---|---|
| Project name | Ojamu |
| Also known as (aliases) | OJA |
| Logo (logo) | ../assets/736_ojamu_logo.jpg |
| Token symbol (ticker) | OJA |
| Category | AI/Other | Infra |
| 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 | 0x0aa7efe4945db24d95ca6e117bba65ed326e291a |
| Token model (token_type) | — |
| Max supply | — |
| Issuance | — |
| Tokenomics (tokenomics, brief) | — |
| Governance | — |
| Admins/keys | — |
| Audit | yes |
| Bug bounty | — |
| Team (team) | — |
| Funding (investors/funding) | — |
| AI component (ai_component) | AI/ML analytics + recommendations for brands |
| Use‑case (use_case) | brand intelligence/marketing in Web3 |
| DecAI Fit — AI thesis fit | 3/6 — medium alignment with the Decentralized AI thesis |
| DecAI Fit component summary | ai_score 1 / onchain_score 1 / token_score 0 / evidence_score 3 |
| Last verified | 2026-02-11 |
Links (links_*)
| Type | Link |
|---|---|
| Website | https://www.ojamu.com/ |
| Docs | https://docsend.com/view/nghf9ca642wn38g7 |
| GitHub | https://github.com/Ojamu-Technologies/Oja-Token |
| Releases / Changelog | https://github.com/Ojamu-Technologies/Oja-Token/commits |
| Whitepaper | https://docsend.com/view/nghf9ca642wn38g7 |
| Roadmap | — |
| Security advisories | https://github.com/Ojamu-Technologies/Oja-Token/security |
| Explorer | https://etherscan.io/token/0x0aa7efe4945db24d95ca6e117bba65ed326e291a |
| X | https://twitter.com/OjamuGlobal |
| Discord | — |
| Telegram | https://t.me/OjamuChat |
| Medium | https://ojamu.medium.com/ |
| Audit report(s) | https://github.com/Ojamu-Technologies/Oja-Token/blob/main/Ojamu%20%20-%20OJA%20Token%20-%20Audit.pdf |
| Bug bounty | — |
| CoinGecko (profile, reference) | — |
| CoinMarketCap (profile, reference) | https://coinmarketcap.com/currencies/ojamu/ |
General project overview
On the Tier‑1 website, Ojamu describes “Ojamu Intelligence Platform” as AI & Blockchain‑powered solutions for brands in Web3 (insights, recommendations, data analysis). Within this card, we record verifiable elements: the Tier‑1 website/whitepaper and the existence of the OJA ERC‑20 token on Ethereum.
Features/modules
- OIP (Ojamu Intelligence Platform): positioned as a platform for insights/recommendations for brands.
- Mention of “proprietary AI & ML” in the platform description (without metrics/architecture per Tier‑1).
Typical scenarios
- Scenario 1: a brand/marketer explores the platform → uses insight/analytics tools (if available).
- Scenario 2: a user interacts with the OJA token → transactions are observable in the Ethereum explorer.
Getting started (wallet/network)
- What you need: access to the project’s website/materials; a wallet for EVM networks (for operations with the token).
- Network/chain: Ethereum (for the token).
- Fees: Ethereum network fees for token transactions.
Architecture/tech (non‑AI)
- Components: an ERC‑20 token on Ethereum; the Ojamu offchain platform/services (details are not established per Tier‑1).
- Participant roles: brands/platform users and token holders.
- Where logic runs: the token — onchain; the platform/AI part — offchain (in the sense of a web platform), details are not established.
- Dependencies: —.
Token/economics (expanded, no forecasts)
- Token utility: not established per Tier‑1 (a Tier‑1 description of the mechanics is needed).
- Who pays fees: for token transactions, the sender pays fees (Ethereum gas).
- Issuance/burn: —.
Governance
- Who makes decisions: —.
- How protocol parameters change: —.
Security and incidents
- Audits: there is a link to a PDF audit of the token (see links_*).
- Bug bounty: —.
- Incidents: —.
- Threat model: typical token risks and offchain platform risks (details not established).
Project status and timeline
- Current status: mainnet (the token on Ethereum).
- Key releases/milestones: —.
- Roadmap: —.
Ecosystem/integrations
- Integrations: —.
- Partners: —.
- Where it’s actually used: —.
AI component of the project
- What is real AI here? per the Tier‑1 website, AI/ML tools for analytics and recommendations in Web3 marketing are claimed.
- What is truly onchain? the confirmed onchain artifact is the OJA ERC‑20 token on Ethereum.
- Why is a token needed? the role of the token as a mandatory mechanism of the product is not established per Tier‑1.
- Red flags (based on the information found): claims about “proprietary AI/ML” without quality metrics; absence of a public tech description/versions.
DecAI Fit component summary
- DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
| Component | Level | Score |
|---|---|---|
| AI reality | low | 1 |
| Onchain necessity | low | 1 |
| Token necessity | low | 0 |
| 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 is claimed as an operational part of the product (AI & Blockchain‑powered platform).
- Evidence: Tier‑1 — https://www.ojamu.com/
- Why sufficient / why not (one line): This item about “intentions” does not add a signal when AI is already claimed as part of the product.
- Conflict note (if any): —
AI_1 — what the AI does (1/0)
- AI_1 (decision): 1
- Claim (one line): Per the Tier‑1 website, AI/ML is used to analyze data and deliver recommendations/insights to brands.
- Evidence: Tier‑1 — https://www.ojamu.com/
- Why sufficient / why not (one line): The Tier‑1 source describes the purpose of the AI part, but without metrics/architecture.
- Conflict note (if any): —
AI_2 — demos/examples (1/0)
- AI_2 (decision): 0
- Claim (one line): A public reproducible demo of the AI part is not recorded per Tier‑1.
- Evidence: Tier‑1 — https://www.ojamu.com/
- Why sufficient / why not (one line): A verifiable “what you can touch” scenario is needed.
- Conflict note (if any): —
AI_3 — metrics/quality (1/0)
- AI_3 (decision): 0
- Metrics: —
- Context (version/date/how measured): —
- Evidence: Tier‑1 — https://www.ojamu.com/
- Why sufficient / why not (one line): No quantitative quality metrics for the AI part were found in the available Tier‑1 sources.
- Conflict note (if any): —
AI_4 — tech description/architecture/versions (1/0)
- AI_4 (decision): 0
- Claim (one line): The tech description/architecture of the AI part is not established per Tier‑1.
- Evidence: Tier‑1 — https://docsend.com/view/nghf9ca642wn38g7
- Why sufficient / why not (one line): 1 requires architecture/versions/details; these are not recorded per Tier‑1 sources.
- Conflict note (if any): —
Onchain necessity
OC_1 — contracts/addresses/chain (1/0)
- OC_1 (decision): 1
- Chain: Ethereum
- Addresses/identifiers: token contract 0x0aa7efe4945db24d95ca6e117bba65ed326e291a
- Evidence: Tier‑1 — https://etherscan.io/token/0x0aa7efe4945db24d95ca6e117bba65ed326e291a
- 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 product, other than the token, is not established.
- Evidence: Tier‑1 — https://www.ojamu.com/
- Why sufficient / why not (one line): 1 requires addresses/descriptions of protocol/logic contracts, not just a token.
- Conflict note (if any): —
OC_3 — onchain is critical (1/0)
- OC_3 (decision): 0
- “Replace the blockchain” test: it is not established that a key property of the product breaks down without onchain.
- Evidence: Tier‑1 — https://www.ojamu.com/
- 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, OJA (ERC‑20).
- Evidence: Tier‑1 — https://etherscan.io/token/0x0aa7efe4945db24d95ca6e117bba65ed326e291a
- 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://www.ojamu.com/
- Why sufficient / why not (one line): 1 requires an explicit Tier‑1 mechanism for payment/access 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://www.ojamu.com/
- Why sufficient / why not (one line): Specific rules/contracts/documentation are needed.
- 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://www.ojamu.com/
- Why sufficient / why not (one line): 1 requires an explicit governance process/documentation.
- 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://www.ojamu.com/
- 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 | https://www.ojamu.com/ | AI/ML positioning and platform description (brand intelligence/insights). |
| Tier‑1 | https://docsend.com/view/nghf9ca642wn38g7 | Project whitepaper/document (context and claims). |
| Tier‑1 | https://etherscan.io/token/0x0aa7efe4945db24d95ca6e117bba65ed326e291a | The existence of the OJA ERC‑20 token on Ethereum (contract/network). |
| Tier‑1 | https://github.com/Ojamu-Technologies/Oja-Token/blob/main/Ojamu%20%20-%20OJA%20Token%20-%20Audit.pdf | Public token audit (PDF in the official repository). |
| Tier‑3 | https://coinmarketcap.com/currencies/ojamu/ | Token profile on an aggregator (context; not proof). |
No comments to display
No comments to display