Oracle-priced assets
Not in the preview yet. This feature is built in the repository but is off in the v2.2.6 preview (test mode). Do not treat this page as available on a preview core. See ../preview.md and the release notes.
Escrow settlement can denominate in assets whose USD price comes from an on-chain price feed. The price-feed doctrine is short and absolute: oracle-priced settlement uses fresh, in-band feed data under per-asset staleness, deviation, and haircut bounds; integer math only; stale, deviant, missing, or non-positive data fails closed. A fallback price never exists.
Where it lives in this release. Oracle pricing is a capability of the contract version 1 asset registry (AssetRegistry.listOraclePriced) and its price adapter (AggregatorPriceOracle), shown end to end on a local chain by make demo-erc20-stale. The core has no setting that lists an oracle-priced asset, so a budget opened through the owner API settles in the configured stablecoin.
The bounds, per asset
| Bound | What it refuses |
|---|---|
| Staleness | Feed data older than the asset's configured maximum age (checked by the adapter and again by the registry). A price that might be from before a market move is not a price |
| Deviation | A reading that moves more than the configured bound from the last recorded in-band observation - flash-crash prints and manipulated rounds fail closed instead of settling |
| Haircut | The accepted price is discounted by the asset's configured haircut on every conversion - volatility inside the bounds is absorbed by the haircut, not by the counterparty |
All three are per-asset configuration: the haircut and the registry's maximum age are set when the asset is listed in the registry, the feed's maximum age and deviation bound when its feed is configured in the adapter. Both are add-only (they cannot be changed or removed later), and the bounds apply in-band at each conversion - never cached from a happier time.
What "fails closed" means here
A conversion that cannot price reverts with a named error (stale feed, deviation breached, non-positive answer, unverifiable timestamp). It does not retry against a secondary source, does not use the last good price, does not average anything. Escrow stays intact and releasable throughout: closing a budget never converts. A fallback price never exists - a second source would just be a second thing to manipulate, and "approximately settled" is not a state this protocol has.
Integer math only
Feed answers, decimals conversions, haircuts, and settlement amounts are integer arithmetic end to end, with an explicit rounding direction: the feed answer is scaled down, which under-values the asset, so a budget opened against it is credited less ceiling, never more. Never floating point. The same rule that governs every other amount in the protocol governs prices.
Interface posture
The adapter builds against the open aggregator interface - the same latestRoundData shape any feed implementing the standard exposes - not against a vendor account or API key. Any feed matching the interface works; none is trusted beyond the bounds above.