Skip to content
PlutusShield
Live on Cardano Preview testnet

Oracle

Depeg cover settles on data, not on a person: three authenticated feeds carry a 24-hour USDM price on Cardano Preview, and the validator reads them directly. Here is what they say right now and everything they have said.

← Back to site
Cardano PreviewTestnet onlyLoading

Reading the oracle feeds on Cardano Preview…

Decoding each feed's inline datum with the same code the Buy uses.

  • feed-a

    …

    —

    USDM 24h TWAP

  • feed-b

    …

    —

    USDM 24h TWAP

  • feed-c

    …

    —

    USDM 24h TWAP

Claim trigger
< $0.9500 for 24 h
Claim quorum
2 of 3 feeds
Sale needs
all 3 feeds, < 2 h old
Relay cadence
checks every 20 min

Every reading published

64 publishes · Oct 6 → Oct 13

Each point is one Preview transaction that wrote the same 24h TWAP to all three feeds. Live market readings ranged from $0.9891 to $1.0072, never near the $0.9500 trigger line. The first two were fixed $1.0000 test readings from before the live relay.

$0.95$0.98$1.00claim trigger
Gold points are the two fixed test readings; blue points are live market TWAPs. Source: the publisher's deployment record, contracts/cardano/deploy/deployments/preview.json.
PublishedUSDM 24h TWAPPreview tx
Oct 13, 9:26 PM UTC$0.9978 87ffffde…0ada ↗
Oct 13, 8:09 PM UTC$0.9983 2a469f96…fb94 ↗
Oct 13, 6:55 PM UTC$0.9996 e2173d92…a278 ↗
Oct 13, 5:29 PM UTC$1.0004 ff254d2b…e0b0 ↗
Oct 13, 4:02 PM UTC$1.0013 dbf8256e…9239 ↗
Oct 13, 2:37 PM UTC$0.9983 21a22a80…4f5b ↗
Oct 13, 1:20 PM UTC$1.0069 5c61d4ce…8cc9 ↗
Oct 13, 11:46 AM UTC$1.0050 ea97797f…d522 ↗

How a reading gets on-chain

  1. Step 1

    Read three live venues

    CoinGecko's USDM price, the Minswap ADA/USDM pool read on-chain and priced with Kraken ADA/USD, and the Minswap USDCx/USDM pool. Fewer than two answering venues means nothing is published.

    venues.ts ↗
  2. Step 2

    Median, then a 24h TWAP

    The cross-venue median is averaged over 24 hours with the same SDK math the validator mirrors, so one venue spiking or going dark can't move the reading on its own.

    oracle.ts ↗
  3. Step 3

    Publish only a healthy peg

    A healthy TWAP is written to all three feeds in one transaction, recycling the superseded feed UTxOs. A depeg is never published as healthy: the publisher stops, the readings age out, and sales close on their own.

    oracle-publisher.ts ↗
  4. Step 4

    The validator decides

    A Buy must reference a fresh healthy reading from every feed. A depeg claim pays only when 2 of 3 feeds attest a price under the trigger for the full window, inside the policy's term. Unauthenticated oracle UTxOs are ignored.

    oracle.ak ↗
Honest statusNot audited

Who runs the feeds today

On Preview one PlutusShield relay signs for all three feeds, so the 2-of-3 quorum is enforced by the validator but not yet independent in practice. The market data is real; the operators are not yet separate. Before any mainnet capital, each feed moves to an independent operator running this same relay, which is what makes the every-feed sale check and the 2-of-3 claim quorum meaningful. The same move is under way for the claims committee on /assessors.

Uses this oracle

Buy cover →

The Buy runs the same sale check in your browser before it asks you to sign.

Depeg claims

Claim checker →

Quorum, TWAP trigger and claim window against the live feeds.

Trust model

Oracle risks →

What a dishonest or offline feed can and can't do.

Every system

Status →

Sales, both pools and the Midnight registry, read live on one page.