dormant other ORA
Ora Protocol logo

Ora Protocol

The verifiable AI oracle stopped answering in September 2025 and the team repointed the Ora name at an AI trading-fund product that does not use the token. The contract is immutable and admin-free. Nothing else is running.

D
Quadrant
Avoid
25
Freedom
/100
F
16
Returns
/100
F
Verdict · Weak on both axes

The oracle stopped serving in September 2025, leaving five requests unanswered, and the team repointed the Ora name at an AI trading-fund product that does not use the token. The standards work and the immutable contract survive. The protocol does not.

Strengths
  • + The token contract has no mint path, no admin and no proxy, so supply can only ever fall
  • + Three Ethereum standards authored into the public record: ERC-7641, ERC-7007 and ERC-6150
  • + opML and the Salus staking audit remain published under an MIT licence in the project's GitHub org
Risks
  • The oracle took its last request on 26 September 2025 and left five requests unanswered
  • The documentation site was deleted, taking the tokenomics and node guide with it, and the pivot was never announced
  • About half of supply has no published allocation, and the December 2025 release arrived with no schedule
Independent verification 10 claims checked · 6 corrected · checked on-chain · as of 2026-09-08
Our call on each · 6 freedom · 5 returns
See Ora Protocol in the integrity board →
Freedom Score
F25/100?

The engineering was real and the standards contributions are permanent, but the protocol this score was written about has stopped. OAO took its last inference request in September 2025 and left it unanswered, the documentation site has been deleted, and the team has repointed the ORA name at an unrelated AI trading-fund product that does not use the token. What still scores is the token contract itself, which is immutable and admin-free, and the open-source record.

Everything that depended on the network running does not.

Infrastructure decentralisation3/20 Overstated

The inference network is not answering. On Ethereum, the canonical OAO deployment (0x0A0f4321214BB6C7811dD8a71cF587bdaF03f0A0, a proxy last upgraded 2025-01-23), the lifetime request counter reached requestId 4615 on 2025-09-26 and no request has arrived since. Requests 4611-4615 (11 Aug to 26 Sep 2025) were never answered: the only AICallbackResult after 2025-04-29 landed on 2026-05-05 and settled requestId 4606, an older request, not any of the outstanding ones. Every request from April 2025 onward came from 0x61423153f111BCFB28dd264aBA8d9b5C452228D2, ORA's own SimplePrompt demo contract listed in the OAO README, so the closing traffic was self-generated. Last activity we could read elsewhere: Base 2025-05-26, Arbitrum 2025-08-13, Linea 2025-03-11. The '500+ Tora nodes' figure was always self-reported and is now unverifiable: docs.ora.io, which hosted the node-operator guide, no longer resolves.

Our independent check
They claim

ORA's Onchain AI Oracle is live, has processed 180,000+ AI inference calls, and runs on 500+ Tora nodes across Ethereum, Optimism, Base and Arbitrum. source →

We found

The oracle has stopped serving. Reading the OAO proxy 0x0A0f4321214BB6C7811dD8a71cF587bdaF03f0A0 on Ethereum directly: the lifetime AICallbackRequest counter reached requestId 4615 on 2025-09-26 and has not advanced since, so the canonical deployment served 4,615 requests in its life, not 180,000. Requests 4611 through 4615, spanning 11 August to 26 September 2025, have no matching AICallbackResult and were never answered. The last request answered in ordinary time was 4610 on 2025-04-29. The single result event since then, on 2026-05-05, settled requestId 4606, an older request, so it is a backfill and not a return to service. Every request from April 2025 onward originated at 0x61423153f111BCFB28dd264aBA8d9b5C452228D2, which the OAO README names as ORA's own SimplePrompt example contract on Ethereum mainnet, so the closing traffic was ORA calling itself rather than third-party integrations. Last readable activity elsewhere: Base 2025-05-26, Arbitrum 2025-08-13, Linea 2025-03-11. The node count cannot be re-verified at all, because the node-operator guide was hosted on the deleted docs domain. Read the OAO implementation ABI (0x6238282cf67aeee19559886b93177434d87d7f41, the target of the last Upgraded event at block 21681956, 2025-01-23) to obtain the real event signatures, hashed each topic0 with cast keccak rather than assuming, then scanned logs from block 22,300,000 to head for both the v1 and v2 AICallbackRequest signatures and for AICallbackResult, and matched requests to results on the indexed requestId. Counting direct transactions alone would have been wrong, because requests arrive as internal calls from user contracts. Verdict human-set.

Our call

Overstated The load-bearing finding of the 2026-09-08 review, and the one that moved both scores. Our own page carried the 180,000-call figure as evidence for Revenue Sustainability 8/25 and Infrastructure 10/20; both are now 1/25 and 3/20. Note the shape of the failure: unanswered requests are worse than no requests, because a user contract that called OAO in August 2025 paid its fee and is still waiting. Design intent versus deployed behaviour applies in the usual direction here, except that the design doc has been deleted and only the contract remains to read.

evidence → signed · as of 2026-09-08 · how it’s signed
Governance decentralisation2/20 Overstated· 2 checks

ORA's own documentation listed governance as a core token utility ('$ORA holders play a crucial role in shaping the future of the protocol through decentralized governance'), and no venue to exercise it was ever built: the Snapshot Hub API returns nothing for ora.eth, oraprotocol.eth or ora-io.eth, and no on-chain governance contract is documented. The page carrying that claim has since been deleted along with the rest of docs.ora.io, so the promise was withdrawn by takedown rather than kept. Holders were given no vote on the pivot that abandoned the product their token was issued against.

Our independent check
They claim

The ORA token carries governance utility: holders shape the future of the protocol through decentralised governance. source →

We found

No governance venue has ever existed. The Snapshot Hub GraphQL API returns an empty result for ora.eth, oraprotocol.eth and ora-io.eth, a name search surfaces no ORA space, and no on-chain governance contract is documented or deployed. The claim is now also unkeepable: the page carrying it was deleted with the rest of docs.ora.io, and the team repointed ora.io to an unrelated product without putting the change to holders. Direct API query for the plausible space identifiers plus a name search. No on-chain governance contract is documented to check instead.

Our call

Overstated RESTORED 2026-09-08, having been withdrawn earlier the same day. The withdrawal was wrong on its facts. It rested on the finding that the only archived ORA tokenomics page was 'a GitBook navigation shell whose content the Archive never captured', but that describes just one page (docs.ora.io/doc/foundation/tokenomics, which covers Axon liquidity mining) at one capture. The governance claim lives on a different page, docs.ora.io/doc/foundation/ora-coin-usdora, which the Archive captured in full six times between January 2025 and December 2025. The 2025-12-13 capture renders the Token Utility section verbatim: 'Governance: $ORA holders play a crucial role in shaping the future of the protocol through decentralized governance.' It resolves 200 for a logged-out reader and the wording keyword-checks on the page, so rule 34 is satisfied by a first-party source rather than by press. The lesson: an absence claim about the Archive needs the CDX index enumerated for the whole host, not one URL guessed and found wanting.

evidence → signed · as of 2026-09-08 · how it’s signed
They claim

ORA is a verifiable AI oracle protocol, and $ORA is the token of the ORA ecosystem. source →

We found

The same team now runs a different product under the same name, and the token did not come with it. ora.io serves an AI-managed prediction-market fund product titled 'ORA - Optimized Return Agents'; its rendered page and 2.3MB of JavaScript bundles contain no occurrence of the ORA token contract address, '$ORA', 'tokenomics', 'opML', 'oracle', 'IMO' or 'staking', and do reference Polymarket and USDC. Team continuity is established three independent ways: the github.com/ora-io org still holds opml, OAO and awesome-ora while describing itself as 'Optimized Return Agents'; the new @ora-io/agent-sdk npm package is published by hyper-oracle, ORA's original npm account, under ORA's pre-rebrand name; and the verified X account @OraProtocol, joined January 2022 with 218.6K followers, carries the new bio. The domain did not lapse: WHOIS shows ora.io ACTIVE at GoDaddy to 2027-05-01 on unchanged AWS Route 53 nameservers. The pivot was never announced on any channel ORA owns: the blog has not posted since 13 January 2025, the docs were deleted rather than updated, and the X account's own posts are fund results rather than any statement about the oracle or the token. Tested the four competing explanations rather than assuming a pivot. A lapsed domain or registrar takeover is ruled out by WHOIS status and unchanged nameservers plus three separate identity continuities. A second product alongside a running oracle is ruled out by the on-chain liveness reconciliation. Abandonment by the team is ruled out by shipping activity (ora-agent-sdk pushed 2026-06-24). The transition is dated by capture digests: www.ora.io served the old homepage on 2026-05-05 and /funds first appears 2026-06-07. Verdict human-set.

Our call

Out of date Recorded as its own row because the flag raised on governance_venue asked for exactly this review before anything else on ORA was trusted as current. The governance reading is deliberate: a token sold with governance utility had the product it was issued against retired, and the name and team redirected to an unrelated venture, with no vote, no notice and no wind-down statement. The successor product is live but trivially small, six funds with combined AUM in the low hundreds of dollars and a World Cup leaderboard showing no ranked entries, so this is not a case of a token being left behind by a runaway success.

evidence → signed · as of 2026-09-08 · how it’s signed
Token distribution fairness5/15 Overstated

Measured on-chain: Ethereum top-10 holders are 94.7% of supply raw, 81.4% excluding the LayerZero OFT adapter, and about 77% resolves to insiders once the funding trace attributes a 26.3% EOA to the team/treasury Safes. The 'community-first' framing described the initial float, not the supply. Roughly half of supply entered circulation in a single unannounced 110,000,000 ORA transfer on 2025-12-16, and the party that could have documented it has now deleted its documentation site.

Our independent check
They claim

ORA launched through a Decentralized AI Community Offering inspired by Vitalik Buterin's DAICO, making it a community distribution. source →

We found

Ethereum ORA top-10 holders = 94.7% raw; infra-excluded (the LayerZero OFT adapter) still 81.4% of supply. 50.1% sits in two Gnosis Safe multisigs (0x8Eb8… 27.1% + 0x5e546… 23.0% — team/treasury/foundation); the funding-trace then resolves the third-largest holder, a 26.3% EOA (0x8520…), to Safe-funded (from:SafeProxy), so it too is insider — lifting insider concentration to ~77%. The launch FLOAT may have been community, but the SUPPLY is ~77% insider-controlled (D0). This answers the score's 'where is the other 83%?'. sources/holders.py: top holders + is_contract + labels, classified holder/insider/infra/cex/burn; Safes counted as insider concentration, the OFT bridge adapter excluded as neutral infra. Concentration = raw balance / total_supply. Ethereum is ORA's canonical chain (OFT); a minority is bridged to spokes.

Our call

Overstated Confirms + quantifies the low 7/15 distribution score. The 'community-first' claim describes the initial float, not the supply. The coldstart holder-source's insider/infra split found 50.1% in two team/treasury Safes; the funding-trace (--trace) then resolved the 26.3% EOA to Safe-funded (team/treasury), lifting insider concentration to ~77% — the earlier re-check on that EOA is now answered. Contrast with OriginTrail, where the same-looking top-10 was mostly neutral bridge/staking infra (D1). Attribution corrected 2026-09-08: ORA does have a citable published home for this claim, recovered from the Wayback CDX index. docs.ora.io no longer resolves (NXDOMAIN), and ora.io has pivoted to an agent-managed-funds product whose /token, /tokenomics, /docs and /blog paths all 404. The '100% of float to the community' wording survives only in third-party press, which we will not cite as the project's own claim, and it sits oddly beside the reported ~$20-23M VC raise. Search exhausted 2026-08-13. The '100% of float to the community' wording is real and traces to ORA's own TGE announcement, but that announcement no longer has a reachable home: docs.ora.io does not resolve, ora.io has pivoted away from the token, mirror.xyz/orablog is bot-gated, and the Wayback captures of the Mirror index render as an empty shell. Decrypt's coverage carries the wording but press is not the project speaking. Left unsourced rather than cited to a secondary source. Freshness wired 2026-08-17. The refresher reproduced this verdict's hand-authored figures, which is the check that made wiring safe rather than merely convenient. Caveat carried from the index: the infra-excluded figure rests partly on addresses Blockscout does not label, and a change in how many of those sit in the top ten is a signal to re-trace by hand, not a new measurement. Claim source restored 2026-09-08. The row previously carried claim_attribution none-published on the reasoning that the '100% of float to the community' wording survived only in third-party press. That wording does, but the underlying claim does not need it: ORA's own ORA Coin page frames the launch as a Decentralized AI Community Offering after Vitalik's DAICO, and the Archive holds full-body captures of that page through December 2025. The claim is now stated in ORA's words and cited to ORA, so the damaging verdict rests on a first-party source as rule 34 requires.

evidence → signed · as of 2026-08-13 · how it’s signed
Censorship resistance7/15 Verified

Re-scoped to the token layer, which is the part that still runs. The deployed ORACoin contract has no Ownable, no AccessControl, no pause and no blacklist; owner(), hasRole(), minter() and paused() all revert, and both EIP-1967 slots read zero, so nobody can freeze, seize or upgrade a balance. That is genuinely strong and it survives the pivot. The opML AnyTrust argument that previously carried this dimension does not: there is no live inference to resist censorship of.

Our independent check
They claim

ORA is a permissionless ERC-20 with no privileged control over holders' balances.

We found

Confirmed at the token layer. The verified source contains no blacklist, no pause modifier, no Ownable and no AccessControl, and the deployed contract reverts on every corresponding call. Nobody can freeze, seize or claw back an ORA balance, and nobody can replace the logic that would allow it, because the contract is not upgradeable. This is a narrower finding than network-level censorship resistance: ORA's inference runs off-chain and is not covered by it. Same runtime probe as the supply verdict, read for the freeze question: absence of pause/blacklist in the verified source, corroborated by reverts on the deployed contract, plus zero EIP-1967 slots to rule out a future upgrade adding them. Scope stated deliberately: this covers the token, not the off-chain inference layer, per the verdict spec's scope-matching rule. Verdict human-set.

Our call

Verified Worth recording because the absence of a freeze function is rarely checked and often assumed. ORA's 9/15 on this dimension is reasoned entirely from the opML AnyTrust model and off-chain inference; the token layer itself is cleaner than that score implies, and the two should be scored as separate scopes at review. Attribution reviewed 2026-09-08: the supply figure ORA published was recovered from the Archive and is cited on the supply row, but ORA never published a freeze or permissionlessness claim, so this row stays none-published rather than borrowing that source.

not re-checked since 2026-08-16
evidence → signed · as of 2026-08-16 · how it’s signed
Data sovereignty3/15

The verifiable-inference provenance that justified this dimension is no longer produced. OAO stopped returning results, so no new inputs or outputs are written on-chain and ERC-7007 provenance has no live issuer. What remains is the historical record of 4,615 Ethereum requests, which is permanent and publicly readable, and nothing forward-looking.

Open source transparency5/15 Understated· 2 checks

The code and the standards survive and are real: 46 public repos, MIT-licensed opml (317 stars), ERC-7641, ERC-7007 and ERC-6150 authored into the public record, and a genuine Salus Security audit of the staking contract (2024-07-13; 2 high, 3 medium, 6 low, 11 of 13 resolved) published in ora-io/audit-report-staking. Against that, the publication surface has collapsed: docs.ora.io was deleted (it served content as late as 2026-04-22), the blog at paragraph.com/@orablog has not posted since 13 January 2025, foundation.ora.io no longer resolves, and no audit ever covered the opML or OAO core. The pivot itself was never announced on any channel the project owns.

Our independent check
They claim

ORA publishes protocol documentation for the Onchain AI Oracle and opML at docs.ora.io. source →

We found

Confirmed, and now dated and explained. docs.ora.io returns NXDOMAIN, while ora.io resolves normally from the same resolvers. The takedown is not a migration: the Wayback CDX index shows docs.ora.io serving full content as late as 2026-04-22, and www.ora.io serving the old oracle homepage (digest JLT5REU75WO6CLXEQMG66PUAHTM7E4OJ) as late as 2026-05-05, with the replacement /funds page first captured 2026-06-07. So the documentation was retired alongside a product pivot in May-June 2026, not moved. What survives: the github.com/ora-io org, and the blog at paragraph.com/@orablog whose most recent post is dated 13 January 2025. foundation.ora.io, printed in ORA's own docs as the foundation's home, no longer resolves either. Queried three independent public resolvers for an A record and captured the response status, with a known-good hostname on the same domain as the control, then confirmed the failure in a browser. Separately enumerated the GitHub org and walked the blog's post index to establish what first-party publication survives. Verdict human-set.

Our call

Out of date The re-check requested for the 2026-09-01 review is done: it is not a migration, and the 90-day cadence is relaxed to 180 because the question is settled. Our open-source evidence credited published documentation and research at 10/15 while the host serving it was gone; that dimension is now 5/15. Search engines still index docs.ora.io, so published links dead-end for readers.

evidence → signed · as of 2026-09-08 · how it’s signed
They claim

ORA publishes third-party security audits of its contracts. source →

We found

Confirmed, and it corrects us rather than ORA. The repository ora-io/audit-report-staking contains ORA_staking-contract_audit_report_2024-07-13.pdf: a Salus Security review of ORA's staking contract at version v5, commit f4ddf14, engagement logged across 21 June to 13 July 2024. It reports 2 high-severity, 3 medium-severity and 6 low-severity issues, with 11 findings marked Resolved, 1 Mitigated and 1 Acknowledged. The audited source sits alongside it in ora-io/staking-contract-audit. The scope is the staking contract only: no published audit was found for the opML or OAO core, and the ORA token contract itself needs none, since it is an unmodified OpenZeppelin ERC20Permit/ERC20Burnable with no admin surface. Enumerated the org's repositories, downloaded the report and extracted its text to read the auditor name, date, contract version, commit and per-severity counts, rather than relying on the repository name. The named-firm-plus-public-report bar in the open-source rubric is met. Verdict human-set.

Our call

Understated Our own evidence said 'No audits found despite $23M funding' and used it to hold open_source_transparency at 10/15. A named firm with a public, dated report clears the rubric's audit bar, so the clause was wrong and has been corrected in both the research JSON and ora.mdx. The score is held pending the 2026-09-01 review because the audit covers staking rather than the opML core, which is the part carrying the thesis. Found because Rob pointed at the ora-io org; the lesson is that a project's GitHub org is a publication surface, and 'no audits found' should always be checked against it before it is written down.

not re-checked since 2026-08-16
evidence → signed · as of 2026-08-16 · how it’s signed
Returns Score
F 16/100 ?

Overall returns potential is weak at 16/100. Strongest dimension: supply dynamics (9/20). Weakest: revenue sustainability (1/25).

Token utility2/20

Every documented use has lapsed. Staking concluded, inference fees have no inference, IMO and Pump.ai ran on a site that no longer exists, governance never had a venue. The successor product does not reference the token.

Value accrual1/20

No fee to accrue. OAO fees required inference that stopped, ERC-7641 revenue sharing applied to IMO tokens rather than ORA, and no buy-back or burn was ever built.

Supply dynamics9/20 Verified

The contract carries no mint path, no admin and no proxy, so supply can only fall. Against that, about half of supply has no published allocation and the December 2025 release arrived with no schedule.

Our independent check
They claim

Total Supply: 333,333,333 $ORA. source →

We found

Confirmed, and stronger than 'fixed' usually means. The runtime checks are independent of the published source: both EIP-1967 slots read zero, so the token is not behind a proxy and its logic cannot be replaced; owner(), getOwner(), hasRole(), DEFAULT_ADMIN_ROLE(), MINTER_ROLE(), minter() and paused() all revert, so there is no owner, no role admin, no minter and no pause; and totalSupply() returns exactly 333,333,333000000000000000000, matching the TOTAL_SUPPLY constant. The verified source carries no mint function at all: ORACoin is ERC20Permit plus ERC20Burnable, and the only _mint calls are the four in the constructor, closed by assert(totalSupply() == TOTAL_SUPPLY). Supply can fall through burns and cannot rise. Probed the deployed contract for every standard control surface (ownership, role admin, minter, pause) and read both EIP-1967 slots directly, so the immutability finding rests on runtime behaviour rather than on reading the project's own source. The source was then read to confirm no mint path exists and to locate the constructor's four _mint calls. Verdict human-set.

Our call

Verified A confirming positive, and the strongest supply posture in the corpus on the code axis: no cap to raise because there is no mint, and no admin to raise it. Note the split this creates with the distribution verdict on the same project: the supply is beyond anyone's control while roughly 77% of it sits with insiders. Those are different questions and both answers stand. Claim source recovered 2026-09-08: this row previously recorded 'no reachable tokenomics page' and carried claim_attribution none-published. That was an unverified absence claim. Enumerating the Wayback CDX index for docs.ora.io returns full-body captures of the ORA Coin page through December 2025, so the first-party claim is citable again and the on-chain finding now reconciles against the project's own words rather than standing alone.

evidence → signed · as of 2026-08-16 · how it’s signed
Revenue sustainability1/25

The Ethereum oracle served 4,615 lifetime requests, not the 180,000 claimed, and the last months' traffic came from Ora's own demo contract. The successor funds hold AUM in the low hundreds of dollars.

Liquidity & access3/15 Verified

Four tickers on four decentralised venues, no centralised listing, turnover a fraction of a tenth of a percent of market cap. The token now has no product behind it to attract one.

Our independent check
They claim

ORA trades only on Uniswap V3 and PancakeSwap with no CEX listings, effectively illiquid, too thin to trade without significant price impact.

We found

Accurate, and if anything generous. Four tickers on four venues, all decentralised: Uniswap V3 on Ethereum at 83.5%, PancakeSwap V3 on BSC, Uniswap V3 on Base and a Raydium CLMM pool. No centralised venue quotes ORA. Total reported 24h volume across every venue is $152, so turnover reads a 0.047% 7-day median and "significant price impact" understates what a single ordinary order would do. Paginated the CoinGecko ticker set and summed 24h volume per venue; turnover from the trailing 7-day median of volume over market cap.

Our call

Verified One of the accurate ones, and the measurement makes it sharper rather than softer. Two DEX venues beyond the two named (Uniswap V3 on Base, Raydium) are the same class of liquidity and change nothing.

evidence → signed · as of 2026-09-06 · how it’s signed
Quadrant D — Avoid ?
Price
$0.0043
Market Cap
$707K
FDV
$1.4M
24h Change
+14.2%
+14.2%

Not financial advice. Scores are opinions, not recommendations. Crypto is high-risk – you could lose everything you invest. Full disclaimer.

Embed this rating
Own Your Mind rating: Freedom F 25/100, Returns F 16/100

The badge updates automatically when the score changes.

Token Details
ORAEthereum, Optimism, Base, Arbitrum, Solana, Hyperliquid0x3333...3333
· Updated
On this page
On-chain data2026-09-14
333.3M
Token Supply
ethereum
Value Loop

The loop as built, and where it stopped

This is the mechanism Ora built, drawn as it was designed to run. Smart contracts called the Onchain AI Oracle through the IAIOracle Solidity interface and paid inference fees in ORA. Tora client nodes ran the model off-chain and posted results on-chain, which opML finalised unless challenged; on dispute a bisection game pinpointed the disagreement and the Fraud Proof VM settled the contested step. Node stakers bonded ORA as submitters or verifiers. The loop is no longer turning: the Ethereum oracle took its last request on 26 September 2025 and left it unanswered.

ORA Value Loop OAO inference requests, opML fraud-proof verification, node stakers CONTRACTS CALL OAO IAIOracle interface prompt + ORA fee TORA NODES INFER off-chain ML run post results on-chain opML FINALISES bisection-game disputes FPVM resolves on-chain NODE STAKERS ORA bonds Tora nodes submitters + verifiers OPTIMISTIC ML Inference runs off-chain, verify only when challenged, AnyTrust needs one honest node. DESIGN, NOW RETIRED 333.3M ORA CAP no mint path, no admin CHAINS ETH · OP · Base · Arbitrum + Solana deployments VERIFICATION opML + FPVM AnyTrust: 1 honest validator STANDARDS AUTHORED ERC-7641 · ERC-7007 + ERC-6150 hierarchical NFT opML optimistic machine-learning verification FPVM Fraud Proof Virtual Machine OAO Onchain AI Oracle ownyourmind.ai/projects/ora Independent DeAI Research

What it does

Ora Protocol was a verifiable oracle that brought AI inferenceInferenceRunning a trained AI model to produce an answer. Inference is what happens when you type a prompt into ChatGPT and get a response. The model takes your input, computes a best guess, and returns it.Like asking an expert for their opinion. The training was the decades they spent becoming an expert. The inference is the 30 seconds it takes them to answer your specific question.Read more → on-chain. Smart contracts could call it for a model output and get back a result carrying a cryptographic guarantee that it had been computed honestly. That description is now historical.

Three things happened, and none of them was announced.

The oracle stopped serving. On Ethereum, the Onchain AI Oracle contract at 0x0A0f4321214BB6C7811dD8a71cF587bdaF03f0A0 counts every request it has ever received. That counter reached 4,615 on 26 September 2025 and has not moved since. The last request answered in ordinary time was number 4,610, on 29 April 2025.

The documentation was deleted. The site at docs.ora.io served content as recently as 22 April 2026 and now returns no DNS record at all. It took the tokenomics page, the node-operator guide and the whitepaper link with it. Search engines still index those pages, so anyone following a link from a paper or a tutorial lands on nothing.

The name was reused. Between 5 May and 7 June 2026, ora.io was repointed at an AI-managed prediction-market fund product. It kept the Ora branding and expanded the acronym to Optimized Return Agents.

This is a pivot, not a hijack

An apex domain that stops resolving while a new site appears on the www subdomain is the shape of a lapsed registration or a registrar takeover, so that was worth ruling out before anything else. That’s ruled out four ways:

  • The domain never lapsed. WHOIS shows ora.io active at GoDaddy with registry expiry in May 2027, on the same Amazon Route 53 nameservers it has always used.
  • The GitHub org is the same org. The ora-io organisation still holds the opml, OAO and awesome-ora repositories, with their history intact, and now describes itself as Optimized Return Agents.
  • The npm publisher is the same account. The new agent SDK package is published by hyper-oracle, the account Ora used under its original HyperOracle name.
  • The X account is the same account. The verified handle joined in January 2022 and carries the same follower base under the new bio.

So the team that built the oracle is the team running the funds. What did not survive the move is the token.

Value proposition

The oracle stopped answering

Ethereum's request counter reached 4,615 and stopped. Five requests from August and September 2025 were never answered.

Standards work survives

ERC-7641, ERC-7007 and ERC-6150 are authored into the public record and outlive the protocol that produced them.

The token was left behind

The successor product routes USDC on Polymarket and never mentions the ORA token, its contract or its tokenomics.

The engineering was worth taking seriously, which is why the ending matters. opML (optimistic machine learningMLMachine Learning. The branch of AI where systems learn patterns from data instead of being explicitly programmed with rules. Modern AI (LLMs, image generation, recommendation systems) is almost entirely machine learning.Like teaching a child to recognise dogs by showing them thousands of pictures of dogs, instead of writing down a precise rulebook for what makes a dog. The child learns the pattern from examples rather than from instructions.Read more →) ran inference off-chain and posted the result on-chain as correct unless challenged. A challenge triggered a bisection game that narrowed the disagreement to a single computational step, which a Fraud Proof Virtual Machine then settled on-chain. Because verification only ran on dispute, it cost far less than zkMLZKMLZero-Knowledge Machine Learning. A cryptographic technique that lets a prover convince a verifier that a specific model produced a specific output, without revealing the model weights or the input.A sealed-bid auction with a referee. You don't see the bids and you don't see the model that picked the winner, but the referee hands you a tiny receipt that proves the winner was selected by the agreed rules. ZKML is the maths that produces that receipt.Read more →, which proves every computation whether anyone doubts it or not.

The team also authored three Ethereum standards: ERC-7641 for revenue-sharing tokens, ERC-7007 for verifiable AI-generated content, and ERC-6150 for hierarchical NFTsNFTNon-Fungible Token. A unique blockchain-tracked asset where each token is distinguishable from every other. Where regular tokens are interchangeable, NFTs represent unique items like art, collectibles, in-game assets, or domain names.Like the difference between a $20 note and a signed first-edition novel. The notes are interchangeable, any $20 buys the same thing as any other. The book is one of a kind, and its value depends entirely on which specific book it is.Read more →. Those are in the public record permanently. They are the part of this project that outlives it.

What the chain says about usage

Ora’s own materials claimed more than 180,000 inference calls, over 500 nodes running the Tora client, and 20-plus projects building on the oracle. Those figures were self-reported through documentation that has since been deleted, so they can’t be re-checked. The contract can be read directly instead, and it tells a smaller story.

Reading, Ethereum mainnetValue
Lifetime requests received4,615
Last request received26 September 2025
Last request answered on time29 April 2025
Requests never answered4,611 to 4,615
Only result event since5 May 2026, settling request 4,606

Two details there carry most of the weight. The single result posted in May 2026 answered request 4,606, an older one, so it was a backfill rather than a return to service. And every request from April 2025 onwards came from 0x61423153f111BCFB28dd264aBA8d9b5C452228D2, which Ora’s own oracle repository names as its SimplePrompt example contract. In its final months the oracle’s only caller was Ora’s own demo.

Elsewhere the picture is the same. The last activity readable on Base was May 2025, on Arbitrum August 2025, and on Linea March 2025.

What replaced it

The current product lists AI-run funds that trade prediction markets. It’s live, and it’s small: six funds with a combined AUM in the low hundreds of dollars, and a headline Ora World Cup leaderboard showing no ranked entries. The team is shipping, with an agent SDK published in June 2026 that submits orders to Polymarket in USDC.

The ORA token has no part in it. The site’s rendered page and its JavaScript bundles contain no occurrence of the token’s contract address, its ticker, its tokenomics, opML, the oracle, the model-offering programme or stakingStakingLocking up a cryptocurrency to help secure a blockchain network, usually in exchange for rewards. The locked tokens act as a security deposit that can be taken away if the staker misbehaves.Like putting down a large rental deposit for an apartment. You get the money back if you behave, you earn interest while it's locked, and the landlord takes it if you trash the place.Read more →.

Tokenomics

Circulating supply Live · CoinGecko · 14 Sept 2026
166.3M
Circulating
49.89% of total
333.3M
Total supply

The token contract is the strongest thing left, and it’s stronger than a fixed supply usually implies. Reading the deployed contract directly: there is no owner, no role admin, no minter and no pause, every corresponding call reverts, and both proxy storage slots read zero, so the logic cannot be replaced. The verified source carries no mint function beyond four constructor calls, closed by an assertion that total supply equals the cap. Supply can fall through burns and cannot rise. Contract address: 0x33333333FEde34409Fb7f67c6585047E1F653333.

Set against that, the disclosure record is poor and has now been made permanent. A single on-chain transfer of exactly 110,000,000 ORA on 16 December 2025 moved circulating supply from roughly 17% to roughly half, with no published schedule and no announcement. Holders could not have anticipated it, and cannot anticipate what remains. Around half of total supply still has no public allocation, and $23M was raised from institutional investors whose token terms were never disclosed.

On-chain concentration is heavy. The top ten Ethereum holders control 93.8% of supply raw, and 80.7% after excluding the bridge adapter as neutral infrastructure. Around 77% resolved to insiders when the funding trace last ran, once two team multisigs and a Safe-funded wallet were attributed. Ora described the launch as a Decentralized AI Community Offering modelled on Vitalik Buterin’s DAICO idea, which describes the initial float rather than the supply sitting behind it.

Every documented use for the token has now lapsed:

  • Node staking concluded before the oracle stopped.
  • Inference fees have no inference to price.
  • Model-offering participation and agent creation ran on a site that no longer exists.
  • Governance was listed as a core token utility in Ora’s own documentation and never had a venue to exercise it.

That last one deserves its own line. Ora’s ORA Coin page told holders they would shape the future of the protocol through decentralised governance. No Snapshot space was ever registered under any plausible identifier, and no on-chain governance contract was ever deployed. When the future of the protocol was actually decided, holders were not asked, and the page carrying the promise was taken down rather than honoured.

How to participate

Beginner
Read the standards, not the protocol

There is no live participation route. Node operation ended with the inference network, building on the oracle means integrating with something that does not answer, and the agent-creation product went down with its website.

If you hold ORA, the practical position is a token with an immutable supply, a heavily concentrated holder base, thin decentralised liquidity and no product behind it. If you came here for the technology, the standards and the opML papers are still published and still worth reading.

Honest assessment

Freedom Score: 25/100

Infrastructure Decentralisation: 3/20. The network is not answering. The Ethereum request counter has been static since September 2025, five requests from that period were never served, and the closing traffic came from Ora’s own demo contract. The 500-node figure was self-reported and cannot be re-checked, because the node-operator guide lived on the deleted documentation domain.

Governance Decentralisation: 2/20. Governance was published as a core token utility and no venue was ever built. Querying the Snapshot hub for the plausible Ora identifiers returns nothing, and no on-chain governance contract is deployed. The decision to retire the product and reuse the name was taken without a holder vote, notice or wind-down statement.

Token Distribution Fairness: 5/15. The great majority of supply sits with insiders on-chain, as the tokenomics section sets out. The community framing described the initial float. Roughly half of supply entered circulation in one unannounced transfer, and the party that could have documented it has deleted its documentation.

Censorship Resistance: 7/15. Re-scoped to the token layer, which is the part still running, and it’s clean there. No owner, no roles, no pause, no blacklist and no upgrade path, so no balance can be frozen or seized. The AnyTrust argument that previously carried this dimension no longer applies, because there is no live inference to censor.

Data Sovereignty: 3/15. The verifiable-inference provenance that justified this score is no longer produced. The 4,615 historical requests remain permanently readable, which is worth something, and nothing new is being written.

Open Source Transparency: 5/15. The code and the standards hold up: 46 public repositories, an MIT-licensed opml repo, three authored ERCs, and a Salus Security audit of the staking contract dated 13 July 2024 reporting 2 high, 3 medium and 6 low findings with 11 of 13 resolved. The publication surface around them has collapsed. The documentation site is deleted, the blog has not posted since January 2025, the foundation subdomain no longer resolves, no audit ever covered the opML or oracle core, and the pivot was announced nowhere the project owns.

Returns Score: 16/100

Token Utility: 2/20. Staking concluded, inference fees have no inference, the model-offering and agent products went down with their website, and governance never had a venue. Axon liquidity mining is the one mechanism not shown to be dead, and its documentation has been deleted. The successor product does not mention the token anywhere.

Value Accrual: 1/20. There is no fee to accrue. The oracle’s model, callback and network fees needed inference that stopped. ERC-7641 revenue sharing applied to model-offering tokens rather than to ORA, and no buy-back or burnBurnPermanently removing tokens from circulation by sending them to an address that no one controls. Burns reduce total supply, which (all else equal) makes each remaining token worth more of the network's value.Like a company buying back its own shares and shredding them. The company's total value stays the same, but each remaining share now represents a slightly bigger slice of that value.Read more → was ever implemented. Whatever the funds product earns, it earns in USDC and routes none of it here.

Supply Dynamics: 9/20. Held up almost entirely by the contract. No mint, no admin, no proxy, and a supply that can only fall. The deductions are for the undisclosed half and the unannounced December 2025 release, which are disclosure failures rather than code ones.

Revenue Sustainability: 1/25. The evidence that carried this dimension described a network that has stopped. The Ethereum lifetime counter reached 4,615 against a claimed 180,000, and the last traffic was self-generated. The successor funds are live at a combined AUM in the low hundreds of dollars.

LiquidityLiquidityHow easily a token can be bought or sold without moving the price. High liquidity means you can enter or exit large positions quickly at the quoted price. Low liquidity means even small trades can swing the market.Like the difference between selling a house and selling a share of Apple stock. The house might be worth more on paper, but finding a buyer at that price takes weeks. The Apple share converts to cash in one click.Read more → & Access: 3/15. Four tickers on four decentralised venues, with Uniswap V3 on Ethereum carrying about 84% of the flow. No centralised venue quotes ORA. Turnover is a fraction of a tenth of a percent of market cap, and the token now has no product behind it to attract a listing.

Quadrant: D (Low Freedom, Low Returns)

Ora leaves Quadrant B and lands in D. The technical work was substantive and the standards contributions are permanent, but a protocol that has stopped serving cannot score on infrastructure, usage or data, and a token its own team has walked away from cannot score on utility or accrual.

Key risks

  • The protocol is dormant. The oracle has taken no request since September 2025 and answered none since April 2025.
  • Five requests were never answered. Contracts that called the oracle in August and September 2025 paid and are still waiting. Unanswered is worse than idle.
  • The team has moved on without saying so. No blog post, documentation update or announcement covers the retirement of the oracle or the future of the token.
  • The documentation is gone, permanently. Tokenomics, node guide and whitepaper links all dead-end, so nothing about the token’s design can now be checked against a live first-party source.
  • About half of supply is undisclosed. No allocation, no vesting schedule, and a 110M release that arrived unannounced.
  • The great majority of supply is insider-controlled on-chain, against thin decentralised-only liquidity.
  • No audit covers the oracle core. The published Salus audit covers the staking contract only.
  • The successor product is tiny. Six funds at a combined AUM in the low hundreds of dollars is not evidence of a team that traded up.

Score change log

DateScoreChangeReason
2026-09-08BothFreedom 47 → 25 (F), Returns 43 → 16 (F)The oracle is dormant and the project pivoted. Ethereum’s request counter stopped at 4,615 on 26 Sep 2025 with requests 4,611 to 4,615 unanswered, and the only later result backfilled an older request. Status set to dormant.
2026-09-08DataN/APivot established rather than assumed. Lapse and takeover ruled out via WHOIS, the ora-io GitHub org, the hyper-oracle npm account and the X account; transition dated to 5 May to 7 Jun 2026 by capture digests. The successor product references the token nowhere.
2026-09-08DataN/AGovernance verdict restored to inflated after being withdrawn earlier the same day. The withdrawal generalised one uncaptured page to the whole host; the archived ORA Coin page carries the governance claim verbatim. Claim sources also recovered for supply and distribution.
2026-09-06DataN/AResearch JSON resynced to the frontmatter Returns breakdown. Supply Dynamics read 10 in the JSON after the 2026-09-05 move to 11 never propagated. No published score changed.
2026-09-05BothSupply Dynamics 10 → 11 (Returns 42 → 43), Token Distribution Fairness 7 → 6 (Freedom 48 → 47)Resolves the 15 August deferral: the dilution overhang halved when circulating was corrected to ~50%, but the same 110M arrived with no published schedule, so disclosure reads worse. Both grades held at D.
2026-08-16DataN/ACorrected “No audits found”: Salus Security audited the staking contract (13 July 2024), 2 high / 3 medium / 6 low, 11 of 13 resolved, though no published audit covers the opML core. Open Source Transparency 10/15 held pending monthly review.
2026-08-15DataN/ACirculating supply corrected from 16.9% to 49.89% (~166.3M) and FDV/MCap from 5.9x to 2.0x, after an on-chain transfer of exactly 110,000,000 ORA on 16 Dec 2025 (Ethereum block 24025314). Supply Dynamics 10/20 and Token Distribution Fairness 7/15 held pending monthly review; weighing in docs/quarterly-review-backlog.md.
2026-08-13DataN/AORA has no citable published source for the distribution claim: docs.ora.io no longer resolves and ora.io has pivoted to an agent-funds product with /token, /tokenomics, /docs and /blog all 404. Recorded as unsourced rather than cited to third-party press.
2026-08-10DataN/AWS3 holder-source + funding-trace: authored token_distribution_fairness (inflated, onchain), confirming the 7/15 score. Ethereum top-10 ex-infra 81.4% of supply, ~77% insider: two team/treasury Safes plus a 26.3% EOA the trace resolved to Safe-funded. The “community-first TGE” describes the float, not the concentrated supply. No score change.
2026-06-26DataN/ADefiLlama LlamaAI harvest cross-check, verified independently (api.llama.fi + CoinGecko, coingeckoId ora-coin). Published figures held up: 16.9% circulating (~56.3M of 333.3M), sub-$1M market cap ($264K), $23M total funding. Corrected the FDV/MCap ratio (5.2x → 5.9x; 16.9% circulating mathematically implies 5.9x). Re-verified ATH decline at ~99.9% (CoinGecko -99.91% from $5.37, TGE day 19 Nov 2024). Two DefiLlama warehouse bugs noted but they do not touch our data: the broken coingecko:ora-protocol price map is a slug we do not use (ours, ora-coin, resolves), and the double-logged $20M Series A (summed to $43M under ora+ora-protocol) is already deduped to the correct $23M in our copy. No score change.
2026-03-06BothN/AInitial publish. Freedom 48/100, Returns 42/100.

Score changes, new reviews, one editorial take every two weeks. No spam.

Team overview

Kartin Wong Co-Founder doxxed

BS Information Science & Technology, University of Arizona. Former software engineer at Google (cryptography and AI) and TikTok. Started crypto ~2011.

Norman Von Co-Founder & CTO doxxed

Background in supercomputer architecture. Whitehat hacker. Authored ERC-7007 and ERC-7641 standards.

Suede Kam Co-Founder anon

Limited public information available.

Polychain CapitalHashKey CapitalHongShan (ex-Sequoia China)dao5SevenX VenturesForesight Ventures
Total raised: $23.0M
Round Amount Date Lead
pre-seed $3.0M 2023-01-01 HongShan (ex-Sequoia China), dao5
strategic $20.0M 2024-06-01 Polychain Capital, HashKey Capital

Source: OYM Research · Last updated 2026-09-14

Technical snapshot

Verifiable AI oracle using opML (optimistic machine learning) — off-chain ML computation with on-chain fraud-proof verification. Optimistic execution with interactive dispute game using bisection protocol. Fraud Proof VM for single-step on-chain verification. AnyTrust security (one honest validator sufficient). Core products: OAO (Onchain AI Oracle), IMO (Initial Model Offering via ERC-7641), RMS (Resilient Model Services), opAgent (on-chain perpetual agents), Pump.ai (permissionless agent creation).

Consensus N/A — uses host chain consensus. opML adds optimistic verification layer with fraud proofs.
Chain Ethereum, Optimism, Base, Arbitrum, Solana, Hyperliquid

Commit Activity

0 commits last 52 weeks
Sept Nov Jan Mar May Jul Aug 1/wk
Stars
317
Forks
71
Contributors
4
Last Commit
2026-06-21
ora-agent-sdk
Flagship Repo
2024-12-11
opml

Source: OYM Research · Last updated 2026-09-14

Tokenomics deep dive

Token utility

  • Node staking (validators and submitters)
  • IMO participation
  • Protocol governance
  • Agent creation on Pump.ai (1 ORA minimum)
  • OAO inference fees (Model Fee + Callback Fee + Network Fee)

Source: OYM Research · Last updated 2026-09-14

Participation at a glance

none n/a

No live participation route remains. Node operation ended with the inference network, OAO integration has nothing answering, and Pump.ai agent creation ran on a site that no longer exists. Holding or selling the token on a decentralised venue is all that is left.

Barriers: The protocol is dormant

Source: OYM Research · Last updated 2026-09-14

Community

Source: OYM Research · Last updated 2026-09-14

Read next