Trust • Diligence commitments

Blinded public commitments — without leaking pack hashes.

This page publishes an append‑only list of blinded commitments to diligence packs. It is intentionally designed to be procurement‑grade and lawsuit‑aware: the public log does not reveal underlying pack hashes or counterparty identifiers.

Verify inclusion (offline) Download log (JSON) Download signed head (DSSE) Download trust anchors
Licensing diligence Two‑layer commitment spec Public teaser pack

How it works (two‑layer commitment)

  1. MVG issues a private receipt to the counterparty containing the pack sha256 and a private nonce.
  2. MVG publishes a public commitment computed as sha256(pack_sha256_ascii || nonce_bytes).
  3. The counterparty recomputes the commitment using the nonce, then verifies inclusion in this log — fully offline using the verifier.

MVG may batch or delay publications to reduce pipeline leakage. This log is transparency evidence, not certification.

Latest signed head

FieldValue
generated_utc2026-02-11T00:00:00Z
entry_count2
head_entry_sha256d0302b1ac0dbd9481c6476ac1617748e9ef461732a4f50294c9d2493b76bcd98
log_sha2565910a3a34fbf66a8a29927de92732df0903138b9cc363ae9f5087dea251d47ee
witness_threshold2

Verify offline Download sample private receipt

Recent commitments

Commitments are blinded (do not reveal pack hashes).

public_commitment_sha256issued_utc
c4a2317cfb83b16eebb18a3fbd8f0dde2365435afefda0b0698703a8ee982a402026-02-11T00:00:00Z
d1787e041bbbd2b73810a535cdb2dd8c40e00f173a88569afbfc911e331b08ae2026-02-01T00:00:00Z
No counterparty identifiers are included. Binding terms exist only in signed agreements.