R Oracle

A resilient multi-source oracle chain built on Polkadot, providing reliable price data through multiple data sources with automatic failover mechanisms.

Comment

🏆 R-Oracle Devpost Inspiration Today’s Web3 applications depend heavily on real-time off-chain data. But APIs fail. RPC providers fail. Networks go down. We wanted to build something that stays alive even when everything else breaks.

R-Oracle was inspired by one question: “What would a truly resilient oracle look like on Polkadot Cloud?”

A self-healing oracle that automatically switches between multiple data sources and multiple RPC endpoints—so developers always have a reliable data backbone.

What it does R-Oracle is a resilient multi-source oracle parachain that keeps updating its on-chain values even when external systems fail.

It features:

🔁 API Failover Engine Primary: Binance API Fallback 1: Coinbase Fallback 2: Kraken Automatic selection of the first working source ⚙️ On-Chain Oracle Pallet

Stores: Last value Source Timestamp Status (OK, Fallback 1, Fallback 2, Offline) 🛡 RPC Failover The frontend auto-switches between: Polkadot Cloud RPC (primary) OnFinality RPC (fallback) If one endpoint goes down, the app remains functional.

📊 Developer Dashboard A clean UI showing: Latest on-chain oracle value Current data source System status History timeline Failover visualization

How we built it 🔨 Parachain Development Using the official Polkadot Hackathon Guide, we built: A Substrate-based parachain A custom pallet: pallet-roracle Storage: LastValue, History Extrinsic: submit_oracle_value() Event: ValueUpdated

🌐 Frontend Next.js + Tailwind Polkadot.js API Multi-source data fetcher (Binance → Coinbase → Kraken) RPC health-check + automatic failover

Timeline and status component ☁️ Infrastructure Deployed on Polkadot Cloud Fallback RPC via OnFinality free infrastructure ⚡ Tools Used Polkadot SDK Polkadot JS API OnFinality RPC Cursor for fast development

Challenges we ran into ❌ Multiple API Rate Limits APIs blocked or throttled unexpectedly. Required smart retry and fallback logic.

❌ RPC Endpoint Failures Simulating RPC failure and building a frontend with automatic switching was tricky.

❌ Substrate Runtime Debugging Custom pallet errors required debugging cross-storage references and weight fees.

❌ Time Constraints Building a parachain + UI + infra failover within 24 hours required extreme focus.

Accomplishments that we're proud of 🎉 Built a full custom Polkadot parachain in under 24 hours

Including pallet, runtime integration, and Polkadot Cloud deployment.

🎉 First “self-healing oracle” demo on Polkadot

Demonstrates a new design pattern for resilience.

🎉 Production-ready failover engine

Both API-level and RPC-level resilience in a single project.

🎉 Clean developer UX

Fast, simple, and immediately useful for anyone building Web3 apps.

What we learned 🧠 Resilience isn’t an afterthought

Most Web3 tools break when external systems fail. Building redundancy from the start changes everything.

🧠 Polkadot Cloud makes custom chains accessible

Deploying a parachain is dramatically easier than expected.

🧠 OnFinality + Polkadot Cloud = Strong Infra Stack

Perfect combo for failover systems.

🧠 Substrate pallets are powerful but require careful design

Minimalistic storage + clean extrinsics = maintainability.

What’s next for R-Oracle 🚀 1. Add more data sources

Weather, gas prices, crypto indices, DeFi metrics.

🚀 2. Full off-chain worker automation

Auto-submit values on-chain without a frontend.

🚀 3. Developer SDK

Easy integration for dApps to pull resilient oracle data.

🚀 4. Extension into cross-chain messaging

Broadcast oracle updates across parachains via XCM.

🚀 5. Apply for Polkadot Fast Grants / Open Grants

To turn R-Oracle into a production-ready, grant-supported oracle protocol.

Share this project:

Updates