Independent evidence. Consensus-authorized prices.
TezOracle separates observation, validation, attestation, and publication across independently operated paths. Each path derives its own view of the market, and oracle consensus turns independent agreement into an authorized price update.
Multiple observation paths. Independent attestations. Oracle consensus.
Multiple venues, local markets, and approved oracle sources under versioned policy
Retrieves observations, applies source-health and deviation policy, derives its own price, and produces a signer attestation when the active policy is satisfied.
Retrieves observations, applies source-health and deviation policy, derives its own price, and produces a signer attestation when the active policy is satisfied.
Independent operators and validation implementations can join under the active policy.
Independent attestations from the required validation paths must agree before a price update is authorized. The signer network is designed to broaden as additional independent operators participate.
Independent observation is where consensus begins.
Independent validation paths observe approved market evidence under the same versioned policy, while retrieving, normalizing, filtering, and deriving prices through separately operated implementations.
Versioned market policy
The active policy defines approved assets and venues, minimum healthy-source counts, staleness limits, liquidity requirements, normalization rules, and deviation bounds for each feed.
Independent retrieval and derivation
Each validation path retrieves market observations separately, applies the same published policy through its own critical implementation, and attests only to the price it derives locally.
Per-feed isolation
Each feed maintains its own source health and publication state so a problem in one market does not automatically stop unrelated prices.
Retained evidence
Normalized observations, source health, policy versions, rejection reasons, and signer decisions are retained outside the price-authority path for monitoring, reproduction, and incident review.
Every attestation carries the full market context.
A TezOracle attestation covers the feed, value, observation time, update ID, policy identity, destination domain, validity window, and source commitment. A cryptographic signature authenticates each attestation, and the oracle contract verifies the required consensus threshold.
- Feed identity
- Canonical asset or batch identifier
- Price value
- Normalized integer and declared precision
- Observation time
- When the market observations used to derive the price were collected
- Update ID
- Monotonically increasing identifier for replay protection and publication order
- Policy commitment
- Source-policy version or hash
- Destination domain
- Chain, oracle contract, and deployment context
- Expiration
- Latest time the attestation may be included in a submitted price update
- Source commitment
- Reference to the normalized observation set when finalized
Accepted updates establish a pending price before activation.
After verifying an authorized price update, the oracle records its value as the pending price. Once the activation boundary has passed, that value becomes the active price available to consumers with freshness and policy metadata.
- Relay
Any relayer may submit an authorized price update. Authorization comes from the signer attestations, so relay service can be replaced without changing price authority.
- Verify
The oracle verifies unique signer attestations and their signatures, required validation-path representation, destination domain, update ID, observation time, precision, expiration, and policy identity.
- Pending
The accepted update establishes a pending price stored separately from the active price consumed by risk-sensitive applications.
- Activate
After the activation boundary, the pending price becomes the active local price and remains subject to consumer-side freshness, bounds, and action-specific risk policy.
Clear authority boundaries preserve independent control.
Signers attest to independently validated prices. A price update is authorized when the required independent attestations reach consensus. Oracle administration manages policy and protocol changes through a separate governance path. Each integrating protocol keeps its own freshness, valuation, exposure, and emergency controls.
- Price authorization
- Required signer attestations authorize a correctly formed price update under the active observation and validation policy.
- Oracle administration
- A separate delayed governance process manages signer membership, consensus requirements, policy changes, pausing, and contract upgrades.
- Consumer risk policy
- Each integrating protocol defines the freshness limits, conservative valuation, exposure caps, liquidation policy, and degraded behavior appropriate to its own application.