Want to test a verifier against a live signed record and the rotated key? Free pilot key, one step: predge.io/start

Lesson: if your signatures verify offline, verifiers cache your key for a long time. Design the revocation path before you need it: - a status per key: active, retired, revoked - a reason and a date - verifiers that re-read the key list - an anchor outside your infra

What survives a revoked key is proof from outside your own servers. Records whose hashes a third party notarized on Base before the breach still show they existed then, unchanged. Example, notarized by FairSeal on 13 Oct: verify.fairseal.io/receipt.h…

Then we re-fetched and re-signed what partners hold. One batch of 100 records, same markets, new key: 100/100 verify offline. Dispute and outcome facts match the earlier copy for all 100. Only blocks, timestamps and signatures changed.

/verify now returns valid: false, reason key_revoked, for anything signed with the old key, even records signed weeks ago. Harsh, but it is the honest answer. Whoever holds a leaked key can sign a record with any date on it, so the date inside the signature proves nothing.

Same day: - new ed25519 attestation key, kid 3b6551a6439b9bda - old key 13fa3d18a369e6c7 stays in our key list, marked revoked, with a reason - partners told by email which kid to pin Key list: api.predge.io/.well-known/pr…

Our host, Railway, emailed customers at 01:03 UTC on 22 Oct: an unauthorized party may have accessed customer env vars, some in decrypted form. Our product is signed records. Our signing key lived in an env var, so we treated it as compromised. Here is what we did:

Thanks @encodeclub! Update since this was written: it's self-serve now. Grab a key in seconds at predge.io/start, POST /v1/verdicts and get a signed delivered / not-delivered verdict you can verify offline. v2 contracts live on Arc. Honest status: predge.io/trust

Predge signed a record of this dispute while the vote was open and again after it resolved. Both snapshots pass our verifier. Full issue, tx hashes and files: data.predge.io/dispute-of-th… Check a record: data.predge.io/verify

What an agent's settlement logic should take from this: - a price near 0.97 or 0.9995 is a price, not a resolution - after a second dispute, plan for days - do not spend collateral that is still in a vote

Round 10372 ended 20 Oct 00:00 UTC. The vote resolved 23 s later on Ethereum: Yes, the same answer as both disputed proposals. Polygon resolution followed at 00:30:38, 92.7 h after the second dispute. The 2026 median from second dispute to on-chain resolution is 88.5 h.

16:30 the question creator posted on the bulletin board: Tesla's published time for the live run is 0.81 s, and the rules count an official Tesla-published time. Yes was 0.9955 at 16:00 and 0.9995 at 17:00. The vote still decided.

Timeline, 16 Oct UTC, on Polygon unless noted: 01:24 Yes proposed 02:09 disputed, question reset 02:10 Yes proposed again, same proposer 03:48 disputed again, 22 min before it would have settled 04:20 sent to UMA's vote on Ethereum, round 10372

Dispute of the week #1: Polymarket's "Will the Tesla Roadster's 0-60 time be less than 1 second?" $5.5M open interest on 18 Oct. The Yes proposal was disputed twice and the outcome went to a UMA token-holder vote. It resolved Yes on 20 Oct at 00:30 UTC.

Thanks Josh! Happy to hear it. Easiest is Telegram: t.me/latcom. Send the idea there in 2-3 lines and I'll get back to you after our Monad submission today.

Why Monad: measured on mainnet, a verdict lands 1 to 2 s after its request and costs about $0.001 (38 markets, 66 tx). Cheap and fast enough to require before every single trade. Code: github.com/predgeAI/erc8004-…

Sign in with email (@privy_io), the wallet you already use (@dynamic_xyz) or just a passkey (mera by Category Labs). No USDC on Monad? Aurora Intents tops up from 20+ chains. On Android it's the same flow, and your fingerprint is the wallet.

Under the hood: a @chainlink CRE workflow re-checks every signed record across the DON and writes safeToAct on chain. An @envio_indexer indexer tracks every verdict, bond and slash on Monad mainnet and testnet.

Step 3, act in one tap: a @KuruExchange note that pays $1 if the answer flips (testnet, live book), a BTC short on Perpl margined in Agora's AUSD, or wait. Agents get the same rule: our @MetaMask agent wallet plugin refuses the bet while the vote is open.

Step 3, act in one tap: a @KuruExchange note that pays $1 if the answer flips (testnet, live book), a BTC short on @perpltrade margined in @withAUSD, or wait. Agents get the same rule: our @MetaMask agent wallet plugin refuses the bet while the vote is open.