AtHeartEngineer/website
1
0
Fork 0
mirror of https://github.com/tlsnotary/website.git synced 2026-01-09 06:48:08 -05:00
Code Issues Packages Projects Releases Wiki Activity

Convert more docs

Browse Source
This commit is contained in:
Hendrik Eeckhaut
2025-05-14 08:40:57 +02:00
parent 7dd42235cc
commit 8232d0da96
50 changed files with 1748 additions and 53 deletions
Download Patch File Download Diff File Expand all files Collapse all files

15
docs/MPC/commitments.md Normal file
View File

@@ -0,0 +1,15 @@
---
sidebar_position: 6
---
# Commitments
Here we illustrate the commitment scheme used to create authenticated commitments to the plaintext in scenarios where a general-purpose [`Notary`](../intro.md#tls-verification-with-a-general-purpose-notary) is used. (Note that this scheme is not used when the `Prover` proves directly to the `Verifier`)
A naive approach of extending the [`Encryption and Decryption`](../protocol/mpc-tls/encryption.md) steps to also compute a commitment (e.g. BLAKE3 hash) using MPC is too resource-intensive, prompting us to provide a more lightweight commitment scheme.
The high-level idea is that the `Prover` creates a commitment to the active plaintext encoding from the MPC protocol used for [`Encryption and Decryption`](../protocol/mpc-tls/encryption.md).
We also hide the amount of commitments (to preserve `Prover` privacy) by having the `Prover` commit to the Merkle tree of commitments.
![Commitment](../diagrams/encoding_commitment.svg)