Verify a release

Anyone can confirm a Certificate of Release without an account. Paste the envelope JSON, see whether the signature matches the published Continuo signing key.

The signing key

Every Certificate of Release is signed with Continuo's Ed25519 key. The current public key is shown below. A successful verification means the envelope was issued by the holder of the matching private key — i.e., us.

Key fingerprint (SHA-256, first 16 hex):

120068d10c89e4dd
Show the full public key (PEM)
b'-----BEGIN PUBLIC KEY-----\nMCowBQYDK2VwAyEADCBOhUyjHJreyry1+pS3PbF5oTNkNpFZSb7tzFXGueU=\n-----END PUBLIC KEY-----\n'

The same key is published at /.well-known/continuo-signing-key.pem.

Paste an envelope

The envelope is a JSON object with shape {envelope: {...}, signature_b64: "..."}. You can copy this directly from the Release certificate page of any released secret, or from the bottom of any release email.

What this proves

A valid signature proves that the envelope was issued by Continuo (the holder of the private key) and that the contents have not been altered since the moment it was signed.

It does not prove that Continuo is trustworthy, that the recipient of the envelope is the intended recipient, or that the secret contents are true or accurate. It proves authenticity and integrity of the signed artifact — nothing more.

For programmatic callers

This form is the human-friendly wrapper. The same verification logic is available as a JSON endpoint for automated auditors and lawyers' systems:

POST /verify/release
Content-Type: application/json

{
  "envelope": {...},
  "signature_b64": "..."
}

Returns {valid, reason, signer_key_fingerprint, issued_at, version}. No authentication. No rate limits at present.