Two already-proven primitives — a third party's signed attestation (SPEC.md §5.11) and asset issuance (SPEC.md §5) — combined into one automatic claim, with no manual review step in between.
You buy a flight-delay policy. An independent flight-status oracle — a genuinely different signing key than the one that issued your policy — reports how delayed the flight actually was. The moment a report meets the policy's threshold, requesting a payout mints it on the spot: no adjuster, no claim form, no waiting. Every step below is a genuine, live call to this domain's own server.
Swap "flight delay" for anything an independent party can observe and sign: a shipment arriving late, a temperature threshold crossed in transit, a game's final score, a benchmark closing above or below a line. Whoever holds the policy gets paid the instant a qualifying report exists — the oracle never touches the money, and the issuer never decides who wins.
One honest limitation, stated plainly: the "independent" oracle here is this same domain's second, independent key — the exact stand-in the attestation demo's reviewer and the reserve-bank demo's auditor already use, not a genuinely separate flight-data provider. The signature check works identically either way; a real deployment would point this role at an actual airline-data feed's own published key. The 120-minute payout threshold is also fixed for this demo, the same for every policy, rather than something a real underwriter would price per policy.
One click mints a bound policy credential to a fresh identity generated in your own browser. Its flight and payout terms are recorded against the credential's own id — the generic asset shape has no room for custom fields, so this is exactly the kind of thing §5.11's attestation half of this demo has to reach outside a bare credential for.
Paste a policy, an oracle report, or a payout's raw JSON below — copy one from a "View raw" details box above. This runs entirely in your own browser: it fetches this domain's public key(s) directly, then checks the signature itself.
Your policy identity is an ordinary ECDSA keypair generated fresh in your own browser tab, exactly like every other demo on this site — no accounts, nothing stored server-side beyond the credentials and policy record themselves. Back to the plaza.