Instructions for Quickstart and Implementation doesn't align and invalid verification method

[Benny1143]

Documentation Alignment issue

Following: https://jolt.a16zcrypto.com/usage/quickstart.html#project-tour
Under Project Tour,
The book suggested that the src/main.rs looks like

pub fn main() {
    let (prove_fib, verify_fib) = guest::build_fib();

    let (output, proof) = prove_fib(50);
    let is_valid = verify_fib(proof);

    println!("output: {output}");
    println!("valid: {is_valid}");
}

But when generating new project with jolt new <PROJECT_NAME>, src/main.rs looks like

pub fn main() {
    let target_dir = "/tmp/jolt-guest-targets";
    let program = guest::compile_fib(target_dir);

    let prover_preprocessing = guest::preprocess_prover_fib(&program);
    let verifier_preprocessing = guest::preprocess_verifier_fib(&program);

    let prove_fib = guest::build_prover_fib(program, prover_preprocessing);
    let verify_fib = guest::build_verifier_fib(verifier_preprocessing);

    let (output, proof) = prove_fib(50);
    let is_valid = verify_fib(50, output, proof);

    println!("output: {output}");
    println!("valid: {is_valid}");
}

I'm unable to use build_fib as shown in the newer version of Jolt.
Am I misled by the different version of Jolt as it seems to me the documentation provides a much simplified manner to develop ZKP as compared to the version it currently presents itself.

Invalid verification method

The method verify_fib(proof) is replaced by the new verify_fib(50, output, proof) which doesn't make sense as the private input for the proof is required for the verification. This doesn't align what how ZKP are supposed to work as mentioned in Microsoft's Spartan proving the knowledge of a secret s such that H(s) == d for a public d

[0xAndoroid]

Thanks for pointing this out. We have just stabilized almost full rewrite of jolt to use Twist & Shout, and our documentation is severely out of date. Documentation will be updated in the upcoming couple of weeks.

As for the verification method comment, currently Jolt does not provide secrecy guarantees, and requires input as part of the proof. Secrecy of the input is on the roadmap, however, there isn't a specific date.

[Benny1143]

Thanks for clarifying, I will check back Jolt once it has been updated. 👍🏻

I would like to know the use cases that Jolt would be useful as a proof given if it does not provide secrecy guarantees.
Given my bare understanding that ZKP supposed to handle secret inputs.
I was looking at Jolt as an alternative to Risc Zero.

[0xAndoroid]

Most of zkVMs do not provide secrecy guarantees right now as well, unless you wrap the proof with groth/plonk.

The use case is the succinctness: it's way faster to verify proof instead of rerunning the computation itself.

[jswalens]

It seems the proving and verification part in main.rs now needs to be changed to:

    let (output, proof, _device) = prove_fib(50);
    let is_valid = verify_fib(50, output, false, proof);

Is that correct?