Price updates with explicit provenance.
TezOracle will expose active prices plus the metadata needed to evaluate feed identity, observation time, policy, and update sequence. Each consuming protocol can then apply the action-specific risk limits appropriate to its own application.
Every price arrives with the context required to evaluate it.
The exact Michelson type will be finalized during implementation. These are the semantic fields an integrator should expect to evaluate.
feed_idCanonical identifier for the priced asset or batch member.
pricePositive fixed-point value interpreted with the declared precision.
decimalsStable feed precision published explicitly for the consumer.
observed_atTime of the source observations used to derive the attested price.
update_idMonotonically increasing identifier that prevents replay or rollback to an earlier accepted update.
activated_atTime or level at which the pending price became the active price.
policy_idCommitment to the source, normalization, and validation policy used for the price update.
Keep application risk policy at the application boundary.
TezOracle authenticates the price update and exposes the resulting active price. The consuming protocol defines how fresh, conservative, and economically bounded that price must be for each action it authorizes.
- Identity
Require the expected oracle address, feed identifier, precision, destination domain, and policy version.
- Time
Evaluate the underlying observation time against the action-specific maximum age and future-time tolerance.
- Activation
Use the active price only after the activation boundary.
- Bounds
Apply asset-specific absolute limits, maximum-change policy, stablecoin depeg policy, and any independent reference checks required by the application.
- Exposure
Bound the economic consequence of a bad value through supply, borrow, position-size, liquidation, and market caps.
- Degraded behavior
Define which operations remain available as publication pauses or the last active price approaches the consumer's maximum age.
Protective mode preserves recovery and risk reduction.
Price-sensitive actions carry different risk. Consumer policy should pause new exposure as confidence falls while preserving repayment, added collateral, and other clearly risk-reducing actions where the protocol can support them safely.
Every deployment ships with its evidence.
Every supported deployment is paired with the source, configuration, and evidence needed to reproduce and evaluate it.
Exact contract, validator policy, signer tooling, serialization logic, and reviewed release artifacts.
Chain identity, oracle address, feed IDs, active signer set, attestation threshold, policy ID, activation parameters, and release version.
Michelson types, views or entrypoints, precision, timestamps, update semantics, attestation requirements, failure behavior, and integration examples.
Testnet and shadow results, source and signer availability evidence, monitoring coverage, known limitations, audit report, and remediation status.
Any published specifications or machine-checked proofs for the exact release, with the proven properties stated explicitly.