Cast Oracles · Technical Whitepaper

RWA Oracle Layer & Agent Infrastructure on BNB Chain

A verifiable data and automation layer built around RWA feeds, 6 specialized AI agents, and micropayment-gated Proof Packs.

Chain: BNB Smart Chain (Mainnet) Access: x402 micropay (BNB native) Mode: Fully paid, per-request

Cast Oracles is building an oracle + agent infrastructure layer that treats data as a paid, verifiable service instead of a free firehose. Every RWA macro snapshot, every agent run, and every developer integration is tied to: on-chain payment, Proof Packs, and auditable receipts.

At the time of writing, the following are already live on BNB Chain:

  • RWA Oracle Layer — US 10Y yield, gold price, macro FRED layer modules, and freshness tracking.
  • 6 AI LLM Agents — market-maker, arbitrage-hunter, trend-sniper, sentiment-monitor, risk-manager, oracle-researcher.
  • Gateway + x402PaymasterV2 — BNB-native pay-per-request gateway with on-chain Paid receipts.
  • Proof Packs — JSON receipts that bind: data pull + payment tx + sources + timestamps.
“What we shipped isn’t even 10% of what’s coming.” Cast Oracles — on the current state of the stack.

2. The Problem: Free Data, Opaque Decisions

Crypto today runs on a contradictory model:

  • Billions of dollars sit in DeFi, RWA vaults, structured products and prediction markets.
  • But the inputs that drive these decisions — rates, spreads, macro signals, datasets — are usually:
    • Free, scraped, or cached without provenance.
    • Fed to models without any persistent proof of what the model actually saw.
    • Impossible to audit after the fact (“Why did this strategy blow up?”).

As RWA scale (T-Bills, real estate, private credit, tokenized funds), this “best-effort” approach is not enough. Institutions, funds, and advanced retail all need:

  • Verifiable feeds with timestamps and freshness/staleness guarantees.
  • Agents that reason over RWA, macro, and on-chain behavior — and leave a paper trail.
  • Pay-per-request economics instead of opaque “bundled” infra costs.

Cast Oracles addresses this by treating each data pull and agent run as a paid, signed, traceable event on BNB Chain.

3. Architecture Overview

3.1 High-Level Components

  • Gateway (BNB) — a stateless Node.js service behind HTTPS that:
    • Handles x402 micropay verification via on-chain receipts.
    • Pulls RWA + macro data from upstream providers (FRED, gold, etc.).
    • Builds Proof Packs binding data to the exact payment tx.
  • x402PaymasterV2 — a minimal, immutable BNB contract:
    • pay(bytes32 sessionId) (BNB-native).
    • Fixed PRICE_WEI per request, forwarded to Treasury.
    • Emits Paid(payer, sessionId, amount, timestamp).
  • RWA Oracle Layer — macro endpoints, gold, rates, spreads, and staleness info.
  • 6 AI LLM Agents — each agent consumes the same Proof Pack and live snapshots.
  • Developer Copilot — a structured AI interface for on-chain devs (BNB focus).

3.2 Data + Payment Flow

Figure 1 — Paid Oracle & Agent Flow

1Client generates a sessionId (bytes32).
2Client calls pay(sessionId) on x402PaymasterV2 (BNB).
3Gateway verifies the Paid event in the tx receipt.
4Gateway pulls RWA macro feeds (US10Y, gold, FRED layer).
5Gateway returns a Proof Pack (JSON) + data payload.
6Agents / Copilot consume Proof Packs as trusted context.

This is intentionally simple: no mutable contract config, no owner, no on-chain storage other than logs. All complexity stays in the gateway + client logic.

4. RWA Oracle Layer

The RWA Oracle Layer is the data backbone of Cast Oracles. It exposes:

  • /api/oracle/macro/latest — paid macro snapshot (requires x402 headers).
  • /api/oracle/fred/*/latest — FRED-based layer modules (DXY proxy, CPI, SOFR, BAA spread).
  • /api/market/snapshot — free BTC/ETH/BNB spot snapshot (CoinGecko).

4.1 Current Feeds

  • US 10Y Treasury Yield (US10Y)
    • Source: FRED (DGS10 series).
    • Unit: percent, with daily as-of date.
    • Used for: discounting, yield curves, risk regime.
  • Gold (USD/oz)
    • Source: gold API provider (normalized to USD per ounce).
    • Unit: usd_per_oz + provider timestamp.
    • Used for: risk-off proxy, collateral stress, macro overlays.
  • Layer Modules (FRED)
    • DXY proxy — trade-weighted USD index.
    • CPI — inflation trend (all urban consumers, all items).
    • SOFR — secured overnight funding rate.
    • BAA Spread vs 10Y — credit risk & recession signal.

4.2 Proof Packs & Freshness

Every macro pull returns a Proof Pack with:

  • Payment receipt — payer, tx hash, block, amount, sessionId.
  • Provider as-of — per-feed timestamps or dates.
  • Staleness — minutes between provider as-of and receipt timestamp.
  • Sources — URLs and identifiers for each upstream feed.

This makes RWA-driven strategies and agents explainable: users can show exactly which inputs were used, when, and whether they were fresh.

5. The 6 AI LLM Agents

Cast Oracles runs a 6-agent LLM arena on top of the RWA Oracle Layer. Each agent is specialized and consumes the same set of live inputs:

Market Maker Arbitrage Hunter Trend Sniper Sentiment Monitor Risk Manager Oracle Researcher

5.1 Roles

  • Market Maker — focuses on spreads, liquidity, execution and microstructure.
  • Arbitrage Hunter — looks for CEX/DEX, cross-venue and cross-chain mispricings.
  • Trend Sniper — regime detection (trend vs mean reversion), invalidation levels, timing.
  • Sentiment Monitor — narrative, flows, crowd positioning, catalyst mapping.
  • Risk Manager — sizing, drawdown limits, leverage sanity, failure modes.
  • Oracle Researcher — data provenance, staleness, and how to verify each claim.

5.2 Why a Multi-Agent Setup?

Single LLM “do everything” agents are hard to trust. Cast Oracles instead uses:

  • Distinct system prompts per role.
  • Shared Proof Pack context for RWA + macro + payment provenance.
  • Side-by-side outputs so humans can compare reasoning paths.

Over time, the 6-agent arena becomes a battle-tested decision surface for BNB-native trading, infra, and RWA protocols.

Figure 2 — Agents on Top of RWA Layer

The RWA Oracle Layer provides facts with receipts. The 6 agents provide opinions with traceability. Together they form an explainable AI layer for builders, traders, and protocols on BNB Chain.

6. Developer Copilot (BNB-first)

On top of the oracle and agent stack, Cast Oracles exposes a BNB Developer Copilot:

  • Helps generate and review smart contracts for BNB Chain.
  • Understands RWA feeds, Proof Packs, and the 6 agents as building blocks.
  • Targets use cases like:
    • Prediction markets and resolution oracles.
    • Agentic trading systems and automations.
    • Dashboards, bots, credit scoring, and RWA vaults.

The long-term goal is to give BNB builders a full-stack copilot: from contract scaffolding to RWA integration and risk checks — with all of it backed by the same pay-per-request Proof Pack model.

7. Tokenomics (Conceptual Design)

The Cast Oracles token (referred to here as CAST) is designed as the coordination and value accrual layer on top of x402 micropay flows. x402 handles BNB-native payments; CAST captures long-term value, governance, and alignment.

7.1 Utility
  • Fee Sharing — a portion of x402 BNB fees is routed to a Treasury governed by CAST stakers.
  • Tiered Access — higher CAST stake → discounted per-request prices and higher rate limits.
  • Priority Routing — CAST staking can prioritise specific apps/oracles for upgrades and features.
7.2 Governance
  • Choosing new RWA feeds and data providers.
  • Adjusting x402 pricing bands or yield-sharing parameters.
  • Whitelisting official Cast-aligned protocols and integrations.

7.3 Economic Flows

Flow Description
BNB → x402PaymasterV2 User pays PRICE_WEI per request via pay(sessionId).
x402 → Treasury Contract forwards funds to a Treasury address (non-upgradable).
Treasury → CAST Ecosystem Via governance: buybacks, incentives, grants, and infra subsidies (subject to final design).
CAST Staking Stakers participate in governance and may receive a share of BNB or CAST rewards.

7.4 Allocation (Illustrative)

These numbers are illustrative only and will be finalized prior to any launch.

Bucket Share Notes
Protocol & Liquidity 35% Market making, BNB pools, bootstrapping integrations.
Core Contributors 20% Vested, long-term aligned with infra growth.
Ecosystem & Builders 20% Grants for RWA apps, agents, copilot extensions.
Treasury & Reserve 15% Strategic flexibility, future partnerships.
Community / Airdrop 10% To users who actually use the oracle and agents.

All concrete tokenomics — including symbol, supply, vesting and distribution — will be announced and formalized after further test cycles, audits, and community input.

8. Roadmap

This roadmap is focused on shipping infra on BNB Chain and expanding the RWA + agent surface area.

8.1 Phase 1 — Foundation (Live Now)

Status: ✅

  • Deploy x402PaymasterV2 on BNB Chain mainnet.
  • Ship gateway with /api/oracle/macro/latest and Proof Packs.
  • Integrate US10Y, gold, and FRED-based layer modules.
  • Release 6-agent LLM arena + BNB Developer Copilot (beta).
  • Launch RWA Oracle UI, Agents UI, and Copilot interface.

8.2 Phase 2 — RWA Expansion & War Room

Status: 🚧 In Progress

  • Expand feeds to cover:
    • T-Bill baskets and benchmark yields.
    • Additional commodities and credit spreads.
    • On-chain BNB yields and protocol-specific metrics.
  • Introduce a BNB War Room dashboard:
    • 6-agent outputs side-by-side on the latest RWA + macro snapshot.
    • Session-based logs with Proof Pack links.
    • Built-in export for traders and teams.
  • Harden gateway with rate limiting and improved observability.

8.3 Phase 3 — Yield, Credit & RWA Protocol Integrations

Status: Planned

  • Dedicated Yield Desk surfaces:
    • On-chain yield across BNB DeFi + RWA products.
    • Risk-adjusted recommendations from Risk Manager + Oracle Researcher.
  • AI Credit Underwriting:
    • Wallet activity and repayment behavior analysis.
    • Macro-aware risk scores and APR ranges.
    • Exportable, verifiable credit reports.
  • Plug into BNB-native RWA vaults, lenders, and prediction protocols.

8.4 Phase 4 — Multi-Chain Anchoring & Governance

Status: Planned

  • Optional on-chain anchoring of Proof Pack hashes to BNB Chain.
  • Cross-chain attestations for other ecosystems (where relevant).
  • Launch CAST token, staking, and on-chain governance.
  • Hand over major parameterization to token-governed processes.

9. Risks & Disclaimers

⚠️ This document is not financial, legal, or investment advice.
  • Data Risk — RWA and macro feeds depend on upstream providers (APIs, FRED, etc.). Outages or errors can propagate into recommendations or models.
  • Model Risk — LLM-based agents can be wrong, overconfident, or misinterpret context. They are tools for humans and protocols, not guarantees.
  • Smart Contract Risk — x402PaymasterV2 is minimal and immutable, but any on-chain contract carries risk. Users should verify addresses and review code.
  • Tokenomics Risk — The CAST design described here is conceptual. Final parameters, allocations, and mechanisms may change.
  • Regulatory Risk — RWA and credit use cases may face local regulatory constraints. Users and integrators are responsible for compliance in their jurisdictions.

Cast Oracles is infrastructure. It does not provide investment advice or guarantee outcomes. Every protocol and user integrating these feeds and agents must perform their own diligence and risk management.

For builders who want to integrate the RWA Oracle Layer, the agent arena, or the gateway directly, technical docs and example integrations can be provided separately.