v1.5.0

Verifier 1.5.0 checks LedgerSeal evidence format 2 (LedgerSeal 4.0.0: code signing, approval routes and signing on the transition screen). verify-evidence.mjs runs the format 2 checks whenever the evidence content needs them, whatever the unsigned format field says:

• signing policies, and code signing on every signature that needs it (by the policy and project each entry names);
• the declaration text of each signature, which must fit its action (approve, reject or revoke);
• route versions;
• the stage signatures of the sealing run;
• quorum and stage order;
• one stage per person;
• no entry of a run after the entry that ended it.

Format 1 output and exit codes are the same as 1.3.0. Adds vectors-route-1.json for --self-test. The FourRealities report verifier (1.4.0) and the public keys are unchanged.

Check the assets with sha256sum -c SHA256SUMS.

v1.4.0

Adds verify-fourrealities-report.mjs, which checks FourRealities evidence reports (manifest, hashes and sizes, Ed25519 signature, report header, previous-report chain, issues not in the report), and the public keys fr-prod-2026-11 (SHA-256 of DER 07b6b5e5749e282627a112d99dac364e199b4a355913e1b820145221cca30419) and fr-dev-2026-11. The LedgerSeal verifier is unchanged.

LedgerSeal offline evidence verifier 1.3.0

LedgerSeal offline evidence verifier 1.3.0

• The production public key ls-prod-2026-11 (LedgerSeal production, the Marketplace app) is published in keys/ls-prod-2026-11.pub.pem and attached to this release. SHA-256 fingerprint (DER): 09f2b807adc803a7f687e0561e90b8dcadadd6c1d752c66b55980a27b89cc5d3
• ls-dev-2026-11 stays the key of development builds only.
• The verifier code and the checks are unchanged; evidence exported for 1.0.0 to 1.2.0 still verifies.

Check the download: sha256sum -c SHA256SUMS

LedgerSeal offline evidence verifier 1.2.0

LedgerSeal offline evidence verifier 1.2.0

• A fifth check: the attestation's status must be the state of the newest history entry that is not a redaction (SEAL_VALID for LS_SEALED, SEAL_BROKEN for LS_CHANGED, SEAL_REVOKED for LS_REVOKED). Evidence whose attestation claims another state fails with exit code 1.
• The CI workflow file carries the Apache-2.0 header.
• Evidence exported for 1.0.0 and 1.1.0 still verifies.

Check the download: sha256sum -c SHA256SUMS

LedgerSeal offline evidence verifier 1.1.0

LedgerSeal offline evidence verifier 1.1.0

• Prints a NOTE line for each redaction entry (LS_REDACTED) in the history. LedgerSeal now names people by party token; records made before that were converted once, and the redaction entry records the head hash before the conversion and the number of values replaced. The chain check covers the entry.
• Prints a NOTE line when the evidence has a "parties" map (party token to account id, null for a closed account). The map is not signed and no check uses it.
• The four checks and the exit codes are unchanged. Evidence exported for 1.0.0 still verifies.

Check the download: sha256sum -c SHA256SUMS

v1.0.0

LedgerSeal offline evidence verifier 1.0.0.

Download verify-evidence.mjs, vectors.json and the key you need, then check them with sha256sum -c SHA256SUMS. Read the README for what a PASS means and what it does not.

Public keys in this release: ls-dev-2026-11 (development builds only). The key of the Marketplace app will be added before the app is listed.