CACHET — verify a resolution, trusting nobody

This page reads Circle Arc directly and checks a Predge resolution in front of you. It has no build step, loads no library, and calls no Predge server for steps 1–3. Save it to disk and it keeps working — that is the only kind of verifier worth having.

running self-test…

marketId (bytes32)

Or leave empty and give platform + market ref below; this page derives the id itself as keccak256(abi.encode(platform, ref)), exactly like the contract.

platform

market ref

Arc JSON-RPC endpoint

PredgeOracle address

key registry (step 4 only — this one is a Predge server)

What this page does not ask you to trust

Not Predge. The record comes from the chain, and PredgeOracle has no edit path: no upgrade, no admin override, no delete. What was written stays written.
Not a server holding the preimage. When the signed envelope is embedded on-chain, the bytes you are checking arrive from the same place as the hash they must match.
Not a library. keccak-256, the ABI codec and the RPC calls are written out in this file. Nothing is fetched from a CDN, so nobody can change the verifier after you read it.
Not this page's word for it. Every hash, key and timestamp below is printed in full so you can compare it against a block explorer or re-run node verify-cachet.mjs and get the same answer.

And what it does depend on, stated plainly:

The RPC endpoint you point it at. A lying RPC can feed this page a lying record. The field is editable for exactly that reason — use your own node, or two you don't control, and see if they agree.
The key registry fetch, for step 4 only. That is a Predge web server. Steps 1–3 stand entirely without it: they prove the bytes settled and were signed by a specific key. Step 4 only says whose key it is.
Your browser's ed25519. The signature check runs on WebCrypto. If the browser has no ed25519, this page says UNAVAILABLE and refuses to call it a pass.