Repository navigation
Conversation
tcoratger
added this pull request to stack #625
October 11, 2026 22:45
This was referenced Oct 11, 2026
Benchmarks: base against this PR, on one runnerfc64b14 merged into its base, against the base ff3104f: each benchmark run in turns on one runner, base and PR 5 times each. A size is shown when it changed; a time or a peak memory when it moved the same way in every round and its median by at least 1% (the change is the median ratio, with the rounds' range). Threads shows the named configuration; BLAKE2s
Fibonacci
Flock
leanSPHINCS
Prover stages
leanXMSS
Prover stages
Every resultBLAKE2s
Prover stages
Fibonacci
Prover stages
Field and transpose kernels
Flock
PCS
leanSPHINCS
Prover stages
leanXMSS
Prover stages
|
tcoratger
force-pushed
the
zk-stack/2-hidden-scalars
branch
from
October 11, 2026 23:18
3819720 to
b912ae9
Compare
tcoratger
changed the title
tcoratger
force-pushed
the
zk-stack/2-hidden-scalars
branch
from
October 12, 2026 08:39
b912ae9 to
5972e1d
Compare
A zero-knowledge prover sends some scalars padded by keys it committed beforehand. - ProverState takes its keys once; while hiding is on, each message is XORed with the next key, used once. A key is one element of E, so it pads one 24-byte message, and in E, XOR is addition: x travels as x + key. Anything else sent while hiding is on panics, as do running out of keys and hiding without keys. - The sponge absorbs the padded bytes, the only ones the proof carries. A proof-of-work nonce stays in the clear. - Both sides track the hidden section: ProverState and VerifierState have set_hidden and is_hidden, and so does the Verifier trait, whose default tracks nothing. A verifier of values reads a padded message as it is; a recording verifier holds it as its value plus an unknown key. - ProverState::proof is the proof written so far, which the prover replays. Co-Authored-By: Kevaundray Wedderburn <kevtheappdev@gmail.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
tcoratger
force-pushed
the
zk-stack/2-hidden-scalars
branch
from
October 12, 2026 14:08
5972e1d to
fc64b14
Compare
This branch has not been deployed
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.
Stack: #619 spec → #620 transcript → #621 pcs → #622 outer proof → #623 ZK leaves → #624 recursion. Replaces #532.
Part 2 of 6 of the zero-knowledge stack (spec: Annex F, "The transcript").
A zero-knowledge prover sends some scalars under a one-time pad it committed beforehand.
What
ProverState::set_keystakes them once.set_hidden(true)holds, each message is XORed with the next key, which is used once.E, so it pads exactly one 24-byte message.E, XOR is addition, soxtravels asx + key.ProverStateandVerifierStateeach haveset_hiddenandis_hidden, and so does theVerifiertrait;ProverState::proofis the proof so far, which the prover replays.Tests
x + key, and the challenges match.Co-authored-by: Kevaundray Wedderburn kevtheappdev@gmail.com
🤖 Generated with Claude Code