Skip to content

Commit

Permalink
clarifying image vs imageid (#875)
Browse files Browse the repository at this point in the history
Current documentation suggests verification algorithm takes the entire
binary file as input.
This PR clarifies that it just needs the ImageID

Co-authored-by: Frank Laub <flaub@risc0.com>
  • Loading branch information
pdg744 and flaub committed Sep 14, 2023
1 parent bcd8668 commit 54936aa
Showing 1 changed file with 3 additions and 2 deletions.
5 changes: 3 additions & 2 deletions risc0/zkvm/src/host/receipt.rs
Original file line number Diff line number Diff line change
Expand Up @@ -84,8 +84,9 @@ pub struct ReceiptMetadata {
///
/// A Receipt is a zero-knowledge proof of computation. It attests that the
/// [Receipt::journal] was produced by executing a [crate::Session] based on a
/// specified memory image. This image is _not_ included in the receipt and must
/// be provided by the verifier when calling [Receipt::verify].
/// specified memory image. This image is _not_ included in the receipt; the
/// verifier must provide an [ImageID](https://dev.risczero.com/terminology),
/// a cryptographic hash corresponding to the expected image.
///
/// A prover can provide a Receipt to an untrusting party to convince them that
/// the results contained within the Receipt (in the [Receipt::journal]) came
Expand Down

0 comments on commit 54936aa

Please sign in to comment.