Gateway Oracle
A configurable component for delivering approved external data onchain, with source, licence, transformation, aggregation, update, fallback, dispute, and operating assumptions defined per feed.

- What it is
- Data-feed component
- Current posture
- Available for supported sources and networks
- What varies
- Architecture, providers, operating scope, and commitments
A signed value is only as reliable as the system around it.
Onchain logic cannot assess the truth, licence, timeliness, manipulation risk, or failure behaviour of external data by itself. Oracle makes those source and operating assumptions visible before a feed influences financial logic.
Keep the core authoritative.
- Licensed data
- Institutional facts
- Application rules
Change the capability at a controlled boundary.
Gateway Oracle changes the boundary, not the institution’s authority.
Sources with authority
Identify approved sources, licences, ownership, update rights, and limitations for the target use.
Failure behaviour by design
Define validation, aggregation, staleness, fallback, pause, dispute, and recovery policies.
A reviewable delivery path
Record source, transformation, signature, update, error, and operational evidence in scope.
What Gateway Oracle contributes. What still needs a decision.
Source integration
Connect approved public or private data sources according to licence and access requirements.
Validation
Apply configured type, range, freshness, quorum, signature, and source-availability checks.
Transformation
Document any normalisation, calculation, unit, currency, aggregation, and rounding behaviour.
Delivery policy
Set supported update cadence, trigger, network, contract, access, and transaction behaviour.
Fallback and dispute
Define staleness, source failure, fallback, pause, correction, and dispute handling.
Operations
Scope telemetry, alerts, retention, incidents, recovery, support, and service commitments.
Continue from Gateway Oracle into the operating model.
Bring the requirement. Define the Gateway Oracle boundary.
A focused workshop maps the target capability, existing systems, providers, controls, and deployment variables.