JIL Sovereign - CourtChain Attestation
Independent. Offline. No keys or password required.
verify.html#h=<anchor_hash>&e=<ed_sig>&p=<pq_sig>&anchor=<url-encoded anchor>
-
1. Classical signature (Ed25519) over the anchor hash
The JIL sealing authority's Ed25519 signature is checked against the published authority public key, over the exact 64-character anchor hash.
2. Post-quantum signature (ML-DSA-65) over the anchor hash
The independent ML-DSA-65 (Dilithium-III) signature is checked against the published post-quantum public key. This keeps the seal valid across the post-quantum transition.
3. Independent timestamp anchor
Whether a third party can establish when this seal existed without trusting JIL. The independent timestamp is an RFC3161 token from a third-party authority (freetsa). A seal with valid signatures but no RFC3161 token is still validly signed; it simply is not independently dated, and this check will say so.
What a VERIFIED result proves. The bundle's anchor hash was signed by the JIL sealing authority using both a classical (Ed25519) and a post-quantum (ML-DSA-65) key whose public halves are published and baked into this file. The seal also carries an independent RFC3161 timestamp (freetsa) fixing when that hash existed - the independent anchor. The CourtChain (jil-mainnet-1) values shown are a deterministic commitment computed from the signed hash: they bind the commitment to this exact seal, but are not a claim of an independent ledger write. Any change to the sealed content breaks the anchor hash, which breaks both signatures and the commitment.
Independence. This page carries its own copy of the verification code and the published public keys. It makes no network requests, needs no login, and never asks for a private key or password. A court, relator, or auditor can archive this single file and re-run the check at any time, offline.
The public keys here verify signatures only; they cannot create them. JIL Sovereign Technologies, Inc.