diff --git a/README.md b/README.md index acc82e5..658839d 100644 --- a/README.md +++ b/README.md @@ -80,11 +80,19 @@ make test # runs cargo test + go test ./... ``` The `cockpit` command is a teaching instrument: it runs the full multi-party -ceremony and streams **every cryptographic operation** — sampling, ElGamal -encryption, Fiat-Shamir challenges, the Bayer-Groth shuffle, Ed25519 signatures, -X25519 key agreement — as **the mathematics that is executing, with the real -runtime values**, the instant it runs. One `pkg/trace` event stream feeds two -surfaces: +ceremony and streams **every cryptographic operation** as **the mathematics that +is executing, with the real runtime values**, the instant it runs. It goes down +to the level of the Swiss Post `crypto-primitives` class structure — you can watch +the Bayer-Groth shuffle proof being *constructed*, not just referenced: + +- ElGamal encryption, Fiat-Shamir challenges, Ed25519 signatures, X25519 key agreement +- **Pedersen matrix commitments** (`CommitmentService`) +- **all five Bayer-Groth sub-arguments** (`ShuffleArgument`, `ProductArgument`, + `HadamardArgument`, `ZeroArgument`, `SingleValueProductArgument`, + `MultiExponentiationArgument`) +- **partial decryption + decryption proofs** (`DecryptionProofService`) + +One `pkg/trace` event stream feeds two surfaces: - **Browser** (default): a self-contained page renders each operation as typeset MathML (no libraries, offline). A stakeholder sidebar highlights the acting diff --git a/cmd/evote/web/crypto.html b/cmd/evote/web/crypto.html index b54ff57..39d38f2 100644 --- a/cmd/evote/web/crypto.html +++ b/cmd/evote/web/crypto.html @@ -1016,6 +1016,7 @@ r = 833704513946265251405968611993787771762... "The output ciphertexts are the correct multi-exponentiations of the inputs with the permutation matrix as exponents."
Simplified intuition: Imagine you have 6 sealed boxes numbered 1-6. You rearrange them and put them in new boxes. The ProductArgument proves "I used each number exactly once" (it's a valid permutation). The MultiExponentiationArgument proves "the new boxes contain the same items as the old boxes" (the ciphertexts were correctly re-encrypted, not swapped for fakes).
+
Watch it happen. Run evote cockpit (browser) or evote cockpit --tmux (terminal): as the mix-net executes, each of these sub-arguments is rendered as live typeset mathematics with the real runtime values, in the order it is constructed — the Pedersen commitment to the permutation matrix, then the Product / Hadamard / Zero / SingleValueProduct / MultiExponentiation arguments, then the partial decryptions. The tree above is not a diagram of the code; it is the code, narrating itself.
` }, diff --git a/presentation-crypto.html b/presentation-crypto.html index b54ff57..39d38f2 100644 --- a/presentation-crypto.html +++ b/presentation-crypto.html @@ -1016,6 +1016,7 @@ r = 833704513946265251405968611993787771762... "The output ciphertexts are the correct multi-exponentiations of the inputs with the permutation matrix as exponents."
Simplified intuition: Imagine you have 6 sealed boxes numbered 1-6. You rearrange them and put them in new boxes. The ProductArgument proves "I used each number exactly once" (it's a valid permutation). The MultiExponentiationArgument proves "the new boxes contain the same items as the old boxes" (the ciphertexts were correctly re-encrypted, not swapped for fakes).
+
Watch it happen. Run evote cockpit (browser) or evote cockpit --tmux (terminal): as the mix-net executes, each of these sub-arguments is rendered as live typeset mathematics with the real runtime values, in the order it is constructed — the Pedersen commitment to the permutation matrix, then the Product / Hadamard / Zero / SingleValueProduct / MultiExponentiation arguments, then the partial decryptions. The tree above is not a diagram of the code; it is the code, narrating itself.
` },