Workspace

Local signing and verification for self-contained proofs across the ternent.dev suite.

Verify

Active signer

No identity loaded

No identity
Online

Online. The app shell is cached for offline use.

Verify

Validate proof structure, signature, and content integrity

Paste or upload a proof JSON payload, compare it with original bytes when needed, or verify the published site artifacts directly.

Verification input

Provide a proof payload, choose the verification depth, and inspect the staged result surfaces below.

Verifier

JSON, plain text, or downloaded proof payloads are accepted.

Choose whether to verify the proof alone or compare it with original content.

Structure + signature

Overall verification

Stage 1 — Proof validation

Not run

No verification run yet.

Content match

Optional content validation

Not run

No content validation run yet.

Published artifacts

Verify deployed site proof

Not run

Fetch `/dist-manifest.json`, `/proof.json`, and optional `/public-key.json` from the current site origin and validate them locally.

No published-artifact check run yet.

Fully client-side. No data leaves your browser.

Seal produces proofs for text, files, and release artifacts.