Expand description
Types for modeling and interacting with a transcript sponge when applying the Fiat-Shamir transformation on a an interactive protocol.
Modules§
- counting_
transcript - An implementation of a
TranscriptSpongethat increments an internal counter for each squeeze. For testing purposes only! - ec_
transcript - keccak_
transcript - poseidon_
sponge - An implementation of a
TranscriptSpongethat uses the Poseidon hash function; Useful for recursive proving. - test_
transcript - An implementation of a
TranscriptSpongethat always returns 1. For testing purposes only! - utils 🔒
Structs§
- Transcript
- A type used for storing an immutable version of the transcript.
A
Transcriptis typically generated by the prover using aTranscriptWriter, and is then serialized and saved on disk as part of the generated proof. The verifier de-serializes the transcript and can access it through theTranscriptReaderinterface. - Transcript
Reader - A
TranscriptReaderis typically created using aTranscriptproduced by aTranscriptWriter. - Transcript
Writer - The prover-side interface for interacting with a transcript sponge. A
TranscriptWriteracts as a wrapper around aTranscriptSpongeand additionally keeps track of all the append/squeeze operations to be able to generate a serializableTranscript.
Enums§
- Operation 🔒
- Describes an elementary operation on a transcript.
- Transcript
Reader Error - Errors that a
TranscriptReadermay produce.
Traits§
- Prover
Transcript - Transcript
Sponge - A
TranscriptSpongeprovides the basic interface for a cryptographic sponge operating on field elements. It is typically used for representing the transcript of an interactive protocol turned non-interactive view Fiat-Shamir. - Verifier
Transcript