Tezos-native oracle infrastructure across Tezos X, from Layer 1 to Layer 2.

TezOracle publishes natively across Tezos X, with direct Michelson publication on Layer 1 and a native oracle domain in the Layer 2 execution environment. One validation network supports both, with destination-bound authorization and local price state at each deployment.

Oracle information moves in both directions.

Native Atomic Composability lets EVM applications receive TezOracle's independent Tezos-native price. In the other direction, compatible EVM oracle readings can reach the Michelson side as additional market evidence evaluated by TezOracle's independent validation paths.

Michelson to EVM
The locally authorized TezOracle price gives EVM applications an independent Tezos-native oracle reading through NAC.
EVM to Michelson
Compatible EVM oracle readings add independent reference evidence to the observations available for TezOracle validation.
Validation boundary
Each TezOracle validation path evaluates imported readings under the same source identity, freshness, precision, confidence, and deviation policy applied to other evidence.
Consensus boundary
EVM readings contribute evidence; they do not count as signer attestations. TezOracle consensus still requires authorized signers to attest to the price their own validation paths derive.

One validated price

Independently derived across multiple validation paths

Tezos X — Layer 1

Michelson oracle

chain_id · L1_oracle · update_id · policy

A destination-bound price update establishes local Layer 1 oracle state.

Tezos X — Layer 2 execution

Michelson interface oracle

chain_id · X_oracle · update_id · policy

A separately attested price update establishes local oracle state inside the execution layer.

Native composability connects the oracle path in both directions.

Michelson applications read TezOracle's local oracle state directly, while EVM applications receive the same independent Tezos-native price through NAC. Compatible EVM oracle readings can travel back through NAC as additional evidence for TezOracle validation.

  1. Local oracle state

    A destination-bound update establishes the authorized TezOracle price in the execution layer's Michelson oracle.

  2. Direct Michelson access

    Michelson applications consume the local oracle state without crossing an interface boundary.

  3. TezOracle to EVM

    EVM applications reach the same independent TezOracle price through the execution layer's native cross-interface path.

  4. EVM readings to TezOracle

    Compatible EVM oracle prices return through NAC as additional evidence that independent TezOracle validation paths may evaluate before signers attest.

Production support will pin gateway encoding, callback behavior, reentrancy protections, failure propagation, and gas bounds through end-to-end testing before enabling cross-interface price use for financial applications.

Independent EVM readings broaden the evidence set.

High-quality EVM oracle readings can add another independently operated view of the market to TezOracle's validation evidence. They strengthen the observations available to validation paths without replacing TezOracle's own validation, signer attestations, or consensus requirements.

Coverage

External feeds can extend the evidence set where their asset definitions and venue coverage complement TezOracle's direct market observations.

Semantics

Each imported reading is evaluated through explicit decimals, timestamps, confidence, heartbeat, source identity, and stale-price rules.

Provenance

Provider upgrades, administrative controls, and feed-definition changes remain explicit properties of the evidence source.

Independence

External readings add evidence, while TezOracle's independent validation paths and signer attestations retain price authority.

See the planned data model