Skip to main content

Ÿ (Yoracle)

Ÿ (Yoracle) — 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).

Ÿ (Yoracle) (also: Yoracle AI; YAI) — an AI/Other | Infra project with the YAI token (ERC‑20; Ethereum).

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 market data service/“oracle” that, per the documentation, builds forecasting signals and analytics based on a set of “data agents” and “oracle agents”.
  • Who it’s for: users who need an analytics/signals dashboard; users of the Telegram bot/mini‑app; in the future — developers via API (claimed as “coming soon”).
  • Why onchain/token: the website claims “hold‑to‑use and subscription access”; the onchain part that can be verified is the ERC‑20 contract of the YAI token.
  • What you can actually touch (Tier‑1): the web dashboard dashboard.yoracle.ai and the Telegram mini‑app/bots listed in the official links.

How it works (very briefly)

  1. The user does: opens the dashboard or the Telegram bot/mini‑app.
  2. The system does: collects/processes data from “data agents” and forms signals/forecasting conclusions from “oracle agents” (as described in the framework).
  3. The user gets: visualizations/signals/analytics on the market.
  4. Where the blockchain is: the YAI token (ERC‑20) on Ethereum.
  5. Token role: claimed as an access mechanism (“hold‑to‑use and subscription access”).

Quick links: AI thesis fit

Project passport

Field Value
Project name Ÿ (Yoracle)
Also known as (aliases) Yoracle AI; YAI
Logo (logo) ../assets/327_yoracle-ai_logo.png
Token symbol (ticker) YAI
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 0x477a3d269266994F15E9C43A8D9C0561C4928088
Token model (token_type) utility (access)
Max supply —
Issuance —
Tokenomics (tokenomics, brief) The website claims that access to the products is tied to holding the token (“hold‑to‑use”) and a subscription model (“subscription access”); detailed parameters are not recorded in the Tier‑1 sources of this card.
Governance —
Admins/keys —
Audit —
Bug bounty —
Team (team) —
Funding (investors/funding) —
AI component (ai_component) multi-agent oracle for signals/analytics
Use‑case (use_case) market analytics + forecasting signals
DecAI Fit — AI thesis fit 3/6 — medium alignment with the Decentralized AI thesis
DecAI Fit component summary ai_score 3 / onchain_score 1 / token_score 0 / evidence_score 2
Last verified 2026-02-11

General project overview

Ÿ (Yoracle) describes itself as a “market data oracle” and a set of services around market analytics. The project’s framework describes a pipeline: data agents monitor data sources 24/7 (including onchain and offchain activity), while oracle agents form forecasting results based on the processed data and pass them to output channels (web dashboard, Telegram bot/mini‑app; API is claimed as a plan).

Features/modules

  • Web dashboard: an interface for viewing analytics/signals.
  • Telegram mini‑app / bots: additional channels for delivering results (listed in the official links).
  • Framework: a description of data agents / oracle agents and data types (market/onchain/sentiment, etc.).

Typical scenarios

  • Scenario 1: a user opens the dashboard → views aggregated data and the conclusions of models/agents.
  • Scenario 2: a user uses the Telegram channel/bot → receives signals/updates in the messenger.

Getting started (wallet/network)

  • What you need: access to the web dashboard or Telegram (depending on the scenario); when interacting with the token — an Ethereum wallet.
  • Network/chain: Ethereum (for the YAI token).
  • Fees: Ethereum network fees arise only for onchain operations with the token.

Architecture/tech (non‑AI)

  • Components: offchain services (dashboard/bots/agents) + the onchain YAI token.
  • Where logic runs: data processing/models — offchain; onchain — the token.

Token/economics (expanded, no forecasts)

  • Token role: “hold‑to‑use and subscription access” is claimed; the specific mechanics of implementing access are not confirmed by Tier‑1 artifacts/rules within this card.

Security and incidents

  • Audits/bug bounty/incidents: no Tier‑1 confirmations were found.

AI component of the project

  • What is real AI here? The framework describes a multi‑agent approach: data agents collect data, oracle agents form forecasting conclusions.
  • What is truly onchain? The ERC‑20 YAI token on Ethereum.
  • Why is a token needed? The website states that the token is tied to access to the product (hold‑to‑use / subscription).
  • Red flags (what to double‑check): no Tier‑1 confirmation of onchain logic beyond the token; some claims (for example, API “soon”) require verification of actual availability.

DecAI Fit component summary

  • DecAI Fit: 3/6 — medium alignment with the Decentralized AI thesis
Component Level Score
AI reality high 3
Onchain necessity low 1
Token necessity low 0
Evidence Tier‑1 present 2
Details

AI reality

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

  • AI_0 (decision): 0
  • Claim (one line): There is a Tier‑1 description of how the oracle works (data agents/oracle agents), not just an “AI intention”.
  • Evidence: Tier‑1 — https://docs.yoracle.ai/framework
  • Why sufficient / why not (one line): This is a description of mechanics/roles, not just intent.
  • Conflict note (if any): —

AI_1 — what the AI does (1/0)

  • AI_1 (decision): 1
  • Claim (one line): Data agents collect/process data, oracle agents form forecasting results/signals.
  • Evidence: Tier‑1 — https://docs.yoracle.ai/framework
  • Why sufficient / why not (one line): A direct description in the Tier‑1 framework.
  • Conflict note (if any): —

AI_2 — demos/examples (1/0)

  • AI_2 (decision): 1
  • Claim (one line): There is a public web dashboard and a Telegram mini‑app/bots.
  • Evidence: Tier‑1 — https://docs.yoracle.ai/links
  • Why sufficient / why not (one line): The official links page lists the access points to the product.
  • 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): No reproducible quality metrics of the models/signals were found in the Tier‑1 documentation.
  • Conflict note (if any): —

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

  • AI_4 (decision): 1
  • Claim (one line): The framework describes the agents’ roles, data types and result output channels.
  • Evidence: Tier‑1 — https://docs.yoracle.ai/framework
  • Why sufficient / why not (one line): There is a Tier‑1 description of the architecture at the level of components/data flow.
  • Conflict note (if any): —

Onchain necessity

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

  • OC_1 (decision): 1
  • Chain: Ethereum
  • Addresses/identifiers: token contract 0x477a3d269266994F15E9C43A8D9C0561C4928088
  • Evidence: Tier‑1 — https://etherscan.io/token/0x477a3d269266994F15E9C43A8D9C0561C4928088
  • Why sufficient / why not (one line): The onchain token contract is available on a public network.
  • Conflict note (if any): —

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

  • OC_2 (decision): 0
  • What useful logic is onchain: No Tier‑1 confirmation of onchain logic other than the token issuance was found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): The product is described as an offchain service; the onchain role is not disclosed as “useful logic”.
  • Conflict note (if any): —

OC_3 — onchain is critical (1/0)

  • OC_3 (decision): 0
  • “Replace the blockchain” test: No Tier‑1 grounds to consider onchain critical were found.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Conservatively: without evidence we set 0.
  • Conflict note (if any): —

Token necessity

TK_0 — no token (1/0)

  • TK_0 (decision): 0
  • Claim (one line): The YAI token exists as an ERC‑20 on Ethereum.
  • Evidence: Tier‑1 — https://etherscan.io/token/0x477a3d269266994F15E9C43A8D9C0561C4928088
  • Why sufficient / why not (one line): The onchain token contract 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 statement of “payment for the service specifically with the token” was found (rather, access via holding/subscription is described).
  • Evidence: Tier‑1 — https://www.yoracle.ai/
  • Why sufficient / why not (one line): “hold‑to‑use / subscription access” is mentioned, but not detailed as a payment.
  • Conflict note (if any): —

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

  • TK_2 (decision): 0
  • Claim (one line): Incentives/collateral/penalties via the token are not described in Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No grounds for 1.
  • Conflict note (if any): —

TK_3 — governance (1/0)

  • TK_3 (decision): 0
  • Claim (one line): Governance via the token is not described in Tier‑1 sources.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): No grounds for 1.
  • Conflict note (if any): —

TK_4 — token is replaceable (1/0)

  • TK_4 (decision): 0
  • Claim (one line): There is no Tier‑1 justification of the replaceability/irreplaceability of the token.
  • Evidence: Tier‑1 — —
  • Why sufficient / why not (one line): Conservatively: without evidence we set 0.
  • Conflict note (if any): —

Evidence (table)

Tier Source What it proves
Tier‑1 https://docs.yoracle.ai/framework Describes data agents/oracle agents and the flow of data/output channels
Tier‑1 https://docs.yoracle.ai/links Lists the public access points (dashboard, Telegram mini‑app/bots)
Tier‑1 https://dashboard.yoracle.ai/docs Describes the components of the Ÿ engine (observers/processors/engineers/advisors) and the “advisor → predicted return → residual” logic.
Tier‑1 https://etherscan.io/token/0x477a3d269266994F15E9C43A8D9C0561C4928088 Onchain contract of the YAI token (Ethereum)
Tier‑1 https://www.yoracle.ai/ The website states “YAI Token … hold‑to‑use and subscription access” (the token’s role for access)
Tier‑2 https://www.coingecko.com/en/coins/y Token profile (context/navigation)
Tier‑3 https://coinmarketcap.com/currencies/yoracle-ai/ Token profile (noise/marketing layer)

No comments to display

Back to top