Oracle

Oracle — 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).

Oracle — an AI/Other project on the Base network, token (symbol: ORCL).

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: per the Tier‑1 links (website/docs/whitepaper), the project is positioned as AI‑relevant, but the content of these materials could not be verified per Tier‑1 (the content at the links was unavailable for verification at the time of verification).
Who it’s for: not established per Tier‑1.
Why onchain/token: the ORCL token on the Base network is confirmed; the necessity of the token is not established per Tier‑1 sources.

How it works (very briefly)

The user does: — (not established per Tier‑1).
The system does: — (not established per Tier‑1).
The user gets: — (not established per Tier‑1).
Where the blockchain is: an ERC‑20 token on the Base network (for the contract, see links_*).
Token role: not established per Tier‑1.

Quick links: AI thesis fit

Project passport

Field	Value
Project name	Oracle
Also known as (aliases)	ORCL
Logo (logo)	—
Token symbol (ticker)	ORCL
Category	AI/Other
Primary chain (chain)	Base
Type	EVM
Network status	mainnet
Consensus (consensus)	PoS (Base; Ethereum L2)
Launch date (launch_date)	—
Project status (status)	active
Token (standard)	ERC-20
Token contract	0xD1D7aa941c71Fd95E9d31bBd81937B3E71Bd6231
Token model (token_type)	—
Max supply	21,000,000 ORCL (max total supply)
Issuance	fixed
Tokenomics (tokenomics, brief)	Not established per Tier‑1.
Governance	—
Admins/keys	—
Audit	—
Bug bounty	—
Team (team)	—
Funding (investors/funding)	—
AI component (ai_component)	—
Use‑case (use_case)	—
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 0 / evidence_score 2
Last verified	2026-02-11

Links (links_*)

Type	Link
Website	https://www.oracleaibase.com
Docs	https://docs.oracleaibase.com/
GitHub	—
Releases / Changelog	—
Whitepaper	https://oracleaibase.com/whitepaper
Roadmap	—
Security advisories	—
Explorer	https://basescan.org/token/0xD1D7aa941c71Fd95E9d31bBd81937B3E71Bd6231
X	https://twitter.com/oracleaibase
Discord	—
Telegram	https://t.me/oracleaibase
Medium	—
Audit report(s)	—
Bug bounty	—
CoinGecko (profile, reference)	https://www.coingecko.com/en/coins/oracle-3
CoinMarketCap (profile, reference)	https://coinmarketcap.com/currencies/oracle/

General project overview

This card contains Tier‑1 links to the website/docs/whitepaper, but the content of these pages could not be verified per Tier‑1 (the content at the links was unavailable for verification at the time of verification). At the level of onchain facts, the ORCL token on the Base network (ERC‑20) is confirmed.

Features/modules

— (not established per Tier‑1).

Typical scenarios

Scenario 1: —.
Scenario 2: —.

Getting started (wallet/network)

What you need: an EVM wallet for Base (for operations with the token).
Network/chain: Base.
Fees: Base fees for onchain operations.

Architecture/tech (non‑AI)

Components: an ERC‑20 token (onchain); the rest of the architecture is not established per Tier‑1.
Where logic runs: —.

Token/economics (expanded, no forecasts)

Token utility: not established per Tier‑1.
Issuance: max total supply 21,000,000 ORCL (per BaseScan).

Governance

Who makes decisions: —.

Security and incidents

Audits: —.
Bug bounty: —.
Incidents: —.

Project status and timeline

Current status: the token exists on the Base network (see links_*); the rest is not established per Tier‑1.
Roadmap: —.

Ecosystem/integrations

Integrations: —.
Partners: —.

AI component of the project

What is real AI here? Not established per Tier‑1 (the content at the website/docs/whitepaper links was unavailable for verification at the time of verification).
What is truly onchain? The ORCL token (ERC‑20) on the Base network.
Why is a token needed? Not established per Tier‑1.
Red flags (based on the information found): a lack of verifiable Tier‑1 data on the AI/product; onchain is limited to the token; the role of the token is unclear.

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	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): The existence of AI intentions is not established per Tier‑1 sources (the content at the website/docs/whitepaper links was unavailable for verification at the time of verification).
Evidence: Tier‑1 — https://oracleaibase.com/whitepaper ; https://docs.oracleaibase.com/ ; https://oracleaibase.com/
Why sufficient / why not (one line): Without verified Tier‑1 content, the flag is left at 0 (conservatively).
Conflict note (if any): —

AI_1 — what the AI does (1/0)

AI_1 (decision): 0
Claim (one line): Not established per Tier‑1.
Evidence: Tier‑1 — https://oracleaibase.com/ ; https://docs.oracleaibase.com/
Why sufficient / why not (one line): There is no verified Tier‑1 description of the AI functions.
Conflict note (if any): —

AI_2 — demos/examples (1/0)

AI_2 (decision): 0
Claim (one line): Not established per Tier‑1.
Evidence: Tier‑1 — https://oracleaibase.com/ ; https://docs.oracleaibase.com/
Why sufficient / why not (one line): Demos/examples are not confirmed per Tier‑1.
Conflict note (if any): —

AI_3 — metrics/quality (1/0)

AI_3 (decision): 0
Metrics: —
Context (version/date/how measured): —
Evidence: Tier‑1 — https://oracleaibase.com/whitepaper
Why sufficient / why not (one line): Quality metrics are not established per Tier‑1.
Conflict note (if any): —

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

AI_4 (decision): 0
Claim (one line): The tech description/architecture is not established per Tier‑1.
Evidence: Tier‑1 — https://oracleaibase.com/whitepaper ; https://docs.oracleaibase.com/
Why sufficient / why not (one line): The materials could not be verified per Tier‑1 (the content at the links was unavailable for verification at the time of verification).
Conflict note (if any): —

Onchain necessity

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

OC_1 (decision): 1
Chain: Base
Addresses/identifiers: token contract 0xD1D7aa941c71Fd95E9d31bBd81937B3E71Bd6231
Evidence: Tier‑1 — https://basescan.org/token/0xD1D7aa941c71Fd95E9d31bBd81937B3E71Bd6231
Why sufficient / why not (one line): BaseScan confirms the existence of the token and max total supply 21,000,000 ORCL.
Conflict note (if any): —

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

OC_2 (decision): 0
What useful logic is onchain: Not established (per Tier‑1 only the token is confirmed).
Evidence: Tier‑1 — https://basescan.org/token/0xD1D7aa941c71Fd95E9d31bBd81937B3E71Bd6231
Why sufficient / why not (one line): There is no Tier‑1 confirmation of other onchain logic.
Conflict note (if any): —

OC_3 — onchain is critical (1/0)

OC_3 (decision): 0
“Replace the blockchain” test: it is not established that the product breaks down without onchain; per Tier‑1 only the token is confirmed.
Evidence: Tier‑1 — https://oracleaibase.com/
Why sufficient / why not (one line): There is no verified 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, ORCL (ERC‑20, Base).
Evidence: Tier‑1 — https://basescan.org/token/0xD1D7aa941c71Fd95E9d31bBd81937B3E71Bd6231
Why sufficient / why not (one line): BaseScan confirms 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): Not established per Tier‑1.
Evidence: Tier‑1 — https://oracleaibase.com/whitepaper
Why sufficient / why not (one line): There is no verified Tier‑1 confirmation.
Conflict note (if any): —

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

TK_2 (decision): 0
Claim (one line): Not established per Tier‑1.
Evidence: Tier‑1 — https://oracleaibase.com/whitepaper
Why sufficient / why not (one line): There is no verified Tier‑1 confirmation.
Conflict note (if any): —

TK_3 — governance (1/0)

TK_3 (decision): 0
Claim (one line): Not established per Tier‑1.
Evidence: Tier‑1 — https://oracleaibase.com/whitepaper
Why sufficient / why not (one line): There is no verified Tier‑1 confirmation.
Conflict note (if any): —

TK_4 — token is replaceable (1/0)

TK_4 (decision): 0
Claim (one line): Not established per Tier‑1.
Evidence: Tier‑1 — https://oracleaibase.com/whitepaper
Why sufficient / why not (one line): There is no verified Tier‑1 confirmation.
Conflict note (if any): —

Evidence (table)

Tier	Source	What it proves
Tier‑1	https://basescan.org/token/0xD1D7aa941c71Fd95E9d31bBd81937B3E71Bd6231	Onchain fact: the Oracle (ORCL) token on the Base network, max total supply 21,000,000.
Tier‑1	—	A Tier‑1 source for claim “what exactly the AI component does” is not confirmed (the content at the website/docs/whitepaper links was unavailable for verification at the time of verification).
Tier‑1	—	A Tier‑1 source for claim “why the ORCL token is needed in the product” is not confirmed (the content at the website/docs/whitepaper links was unavailable for verification at the time of verification).
Tier‑2	https://www.coingecko.com/en/coins/oracle-3	Token profile (for reference, not proof).
Tier‑2	https://coinmarketcap.com/currencies/oracle/	Token profile (for reference, not proof).