PREDGE.VERIFIED

Iran leadership change by December 31?

Called YES @ 0.8400 · still open

✓ed25519 signature is valid for the signed bytes
✓content hash equals sha256 of the exact signed bytes

Signed materials — everything the checks ran on

public key (ed25519)13fa3d18a369e6c71bf941563ba47822b30182273d5106a0e8fb61c5016352d9

content hash4fed59441884d954615c5503b00e796405ef49a7735b3beba60d9734c6ab6c64

call · canonical bytes

{"condition_id":"0x377e7fe65cf198a7fc4fdae3f2136b74729279267858daaf96718b23bc2a5607","issued_at":"2026-08-03T05:57:55.152Z","issuer":"predge.io","kind":"live-call","nonce":"1b86bf94-a478-40b3-a8be-0a48f9438568","note":"mainnet smoke","platform":"polymarket","prev_hash":null,"price_at_call":"0.8400","side":"yes","size_usd":null,"version":"predge-attest-v1"}

call · signature

297c0faa07062f54650ae7af0f6ef19ccde2fcc66520b8285c49a68c5d31d87938b0b35e3e420951ae4d4afd12bb106d99c26506ee70b20adfd19946bedc3b02

Verify it yourself

curl "https://api.predge.io/verify?id=0f1dc2bb-4b52-44bc-83ac-0a68146ff6d1"

Or recompute offline with any ed25519 library: sha256 the canonical bytes and check it equals the content hash, then verify the signature against the published key at https://api.predge.io/.well-known/predge-keys.json. No call back to Predge required — that is the point.

Machine-readable verify Permalink Signing key

Predge — trust by proof, not by brand.predge.io