feat(kos): domain-separate instances with a per-instance salt - #446
Open
AdamDawidKrol wants to merge 1 commit into
Open
AdamDawidKrol wants to merge 1 commit into
AdamDawidKrol wants to merge 1 commit into
Conversation
Add an `instance_id` to `kos::Sender`/`Receiver`, mixed into each base-OT-derived setup PRG seed via a tweakable correlation-robust hash (`FIXED_KEY_AES.tccr(instance_id, seed)`). KOS instances that share one global `delta` and the same base OT then derive independent extension transcripts, so per-instance leakage can no longer be composed to sample or recover `delta`. The mix is non-invertible in `seed`: a linear XOR mix would let a malicious receiver, who controls the base-OT seeds, pre-compensate them to cancel the salt and collapse two instances onto one PRG stream. API-breaking: `Sender::new`/`Receiver::new` gain an `instance_id: Block`. Paired sender and receiver must use the same id; distinct instances reusing one `delta` must use distinct ids.
AdamDawidKrol
added a commit
to AdamDawidKrol/tlsn-rcot-fix
that referenced
this pull request
Jul 24, 2026
Addresses the review on this PR: each RCOT consumer gets its own KOS instance but they all share one global `delta`. Give each logical consumer a distinct `instance_id` (matched across prover and verifier: sender id N ↔ receiver id N; proxy uses a single fixed id) so the same-`delta` instances are domain-separated. Depends on the KOS `instance_id` change (ethereum/mpz#446). Until that lands in a release, the `[patch]` block temporarily points mpz at an alpha.6-compatible build of the same change.
Wondertan
pushed a commit
to grndd-systems/tlsn
that referenced
this pull request
Sep 5, 2026
Addresses the review on this PR: each RCOT consumer gets its own KOS instance but they all share one global `delta`. Give each logical consumer a distinct `instance_id` (matched across prover and verifier: sender id N ↔ receiver id N; proxy uses a single fixed id) so the same-`delta` instances are domain-separated. Depends on the KOS `instance_id` change (ethereum/mpz#446). Until that lands in a release, the `[patch]` block temporarily points mpz at an alpha.6-compatible build of the same change.
Wondertan
added a commit
to libid-org/notary
that referenced
this pull request
Sep 7, 2026
Promote the PoC-qualified TLSN pin with per-consumer RCOT and KOS domain separation. Repeat its MPZ workspace patches so the notary and SDK test clients resolve the same dependency graph as the browser WASM build. Depends on tlsnotary/tlsn#1173 and ethereum/mpz#446, alongside the existing #1178 and #1179 fork changes. Assisted-by: GPT-5 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Wondertan
added a commit
to libid-org/notary
that referenced
this pull request
Sep 7, 2026
Promote the PoC-qualified TLSN pin with per-consumer RCOT and KOS domain separation. Repeat its MPZ workspace patches so the notary and SDK test clients resolve the same dependency graph as the browser WASM build. Depends on tlsnotary/tlsn#1173 and ethereum/mpz#446, alongside the existing #1178 and #1179 fork changes. Assisted-by: GPT-5 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Wondertan
added a commit
to libid-org/notary
that referenced
this pull request
Sep 8, 2026
Promote the PoC-qualified TLSN pin with per-consumer RCOT and KOS domain separation. Repeat its MPZ workspace patches so the notary and SDK test clients resolve the same dependency graph as the browser WASM build. Depends on tlsnotary/tlsn#1173 and ethereum/mpz#446, alongside the existing #1178 and #1179 fork changes. Assisted-by: GPT-5 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
Wondertan
added a commit
to libid-org/notary
that referenced
this pull request
Sep 10, 2026
Promote the PoC-qualified TLSN pin with per-consumer RCOT and KOS domain separation. Repeat its MPZ workspace patches so the notary and SDK test clients resolve the same dependency graph as the browser WASM build. Depends on tlsnotary/tlsn#1173 and ethereum/mpz#446, alongside the existing #1178 and #1179 fork changes. Assisted-by: GPT-5 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
xgreenx
pushed a commit
to libid-org/notary
that referenced
this pull request
Sep 15, 2026
Promote the PoC-qualified TLSN pin with per-consumer RCOT and KOS domain separation. Repeat its MPZ workspace patches so the notary and SDK test clients resolve the same dependency graph as the browser WASM build. Depends on tlsnotary/tlsn#1173 and ethereum/mpz#446, alongside the existing #1178 and #1179 fork changes. Assisted-by: GPT-5 Signed-off-by: Wondertan <hlibwondertan@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Adds an
instance_idtokos::Sender/Receiver, mixed into each base-OT-derived setup PRG seed via a tweakable correlation-robust hash:Prg::from_seed(FIXED_KEY_AES.tccr(instance_id, seed)).KOS's security is analysed for a single extension instance per
delta. When several instances share one globaldelta— as in tlsnotary/tlsn#1173, where each RCOT consumer gets its own instance — they fall outside that single-instance assumption, and the implementation does no per-instance domain separation.API
Breaking:
Sender::new/Receiver::newgain aninstance_id: Block. Paired sender and receiver must use the same id; distinct instances reusing onedeltamust use distinct ids. Single-instance callers can passBlock::ZERO.