Read a Window's proof

Follow signed prints to the ledger updateOwarine

0:00Open a settled Window0:06Read the signed prints0:11Follow the update0:18Inspect the projection

Read the transcript

0:00 · Open a settled Window. Open a settled BTC two-minute Window from Proof.

0:06 · Read the signed prints. Read the Coinbase, Kraken and Bitstamp prints, their medians, quorum and spread.

0:11 · Follow the update. Follow the Ledger update link from the resolution receipt.

0:18 · Inspect the projection. The new tab shows the update id, offset, UTC time and number of witnessed events from the venue projection.

Download videoDownload captionsRecording provenance

Open Print proof from More → Records and proof. Choose a decided Window, then inspect its opening and closing evidence, median, spread, outcome or void reason. The result uses those recorded boundary prints, not the latest price on the chart.

Follow the timeline

1. Check the asset, cadence and Window times.
2. Read each oracle party's open and close print and its named source.
3. Compare the median and spread with the Series' quorum and agreement limit.
4. Read the Resolution and the parties that signed it.
5. Open the ledger update link for the step you want to inspect.

Signed oracle prints on a settled WindowOwarine

Click to expand

Signed oracle prints on a settled Window

Owarine

Capture state: A settled BTC two-minute Window on Canton DevNet. The proof links its ledger update; the linked projection showed its offset, UTC time and three witnessed events.

Captured 8 October 2026 on the hosted Canton DevNet product.

1. 1Inspect the recorded Coinbase print and its source hash.

Open original capture

A Resolution establishes the Window's result. Your payout has its own settlement receipt in Portfolio.

Hosted check — 8 October 2026: a settled BTC Window showed its signed exchange prints. Its update link opened a page with the ledger offset, UTC time and witnessed events. That page is Owarine's hosted projection of the update; it is operated by the venue rather than an independent ledger browser.

Re-verify

Re-verify asks the server to recompute the medians, spreads and outcome, compare archived source bytes with their hashes, and re-fetch supported exchange candles. Read every check: Pass, Fail and Unavailable have different meanings. A missing archived payload cannot be checked merely because its hash is on the ledger.

The proof page also states the trust boundary. Canton limits contract visibility by stakeholder, while this demo's operator holds ledger access for the demo parties. Three oracle parties are not automatically three independent operators. See price sources for what each source proves.