Merkle-Meet — Tamper-evident, privacy-preserving minutes

Step 0 — From Transcript (optional)

Use a raw transcript to auto-build meeting minutes before hashing. The parser extracts agenda lines and notes into structured JSON.

Drop in a raw transcript, convert to meeting JSON, then copy, download, or fill Step 1 automatically.

Step 1 — Load Minutes

Minutes JSON is the canonical record we hash. Each agenda item becomes a Merkle leaf in the order it appears. Review or edit it before computing the root.

Paste your minutes JSON. You can load an example to explore.

Step 2 — Compute Root

A Merkle root is a single fingerprint for the entire meeting. Any change to agenda or notes alters the root, making tampering evident.

Normalize → hash items (SHA-256) → build Merkle tree.

Step 3 — Publish & Share

Share the Merkle root (and proof, if needed) with your team. Anyone can recompute the root locally and confirm it matches.

Post the root where others can see (e.g. Slack).

Step 4 — Verify Record

Verification recomputes the fingerprint from your minutes and checks it against an expected root. Matching roots confirm no changes were made.

Recompute from JSON and compare to an expected root.

Step 5 — Generate Proof

A membership proof lets you show one agenda item was part of the meeting without revealing the rest of the notes.

Select an agenda item (radio list beside the minutes) to generate its inclusion proof.

Step 6 — Verify Proof

Proof verification replays the Merkle path to ensure the proof matches the root you trust. If any hash or ordering is wrong, verification fails.

Check a membership proof against the root.

Trust the minutes. Not the note-taker.

All verification is local. No servers. No secrets leaked.

Root: —

Minutes JSON

Salt (opt.)

Terminal Feed

1. Load or convert minutes JSON.
2. Compute the Merkle root (salt optional).
3. Share or verify proofs as needed.

Output

Transcript → Meeting JSON

Choose a sample meeting