GATEWAY
Components · Data-feed component

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.

Data-feed componentAvailable for supported sources and networks
Gateway Oracle data-feed component
Approved sourcesValidation and fallbackOnchain delivery
What it is
Data-feed component
Current posture
Available for supported sources and networks
What varies
Architecture, providers, operating scope, and commitments
Why it exists

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.

What changes

Gateway Oracle changes the boundary, not the institution’s authority.

01

Sources with authority

Identify approved sources, licences, ownership, update rights, and limitations for the target use.

02

Failure behaviour by design

Define validation, aggregation, staleness, fallback, pause, dispute, and recovery policies.

03

A reviewable delivery path

Record source, transformation, signature, update, error, and operational evidence in scope.

Product boundary

What Gateway Oracle contributes. What still needs a decision.

01

Source integration

Connect approved public or private data sources according to licence and access requirements.

02

Validation

Apply configured type, range, freshness, quorum, signature, and source-availability checks.

03

Transformation

Document any normalisation, calculation, unit, currency, aggregation, and rounding behaviour.

04

Delivery policy

Set supported update cadence, trigger, network, contract, access, and transaction behaviour.

05

Fallback and dispute

Define staleness, source failure, fallback, pause, correction, and dispute handling.

06

Operations

Scope telemetry, alerts, retention, incidents, recovery, support, and service commitments.

Related paths

Continue from Gateway Oracle into the operating model.

Scope Gateway Oracle

Bring the requirement. Define the Gateway Oracle boundary.

A focused workshop maps the target capability, existing systems, providers, controls, and deployment variables.