Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: hollow aggregated proofs #149

Draft
wants to merge 9 commits into
base: main
Choose a base branch
from

Conversation

ninabarbakadze
Copy link
Member

@ninabarbakadze ninabarbakadze commented Feb 11, 2025

Closes #144

panic!("must provide at least 2 proofs");
}

// Read all public values
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sorry, minor update to the inputs, we should have verification keys here as well:

// Read all verification keys first

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

no worries! I'll wait for your PR to merge and then I can replicate it.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should be addressed! :)

@ninabarbakadze ninabarbakadze marked this pull request as ready for review February 24, 2025 11:57
@ninabarbakadze ninabarbakadze force-pushed the nina/hollow-aggreagted-proofs branch from e27c397 to 707643c Compare February 24, 2025 13:15
@@ -5,10 +5,6 @@
sp1_zkvm::entrypoint!(main);

use blevm_common::BlevmOutput;
use celestia_types::nmt::Namespace;
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was seeing warnings for unused imports

Copy link
Collaborator

@rootulp rootulp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

  1. Can you please add to PR description how this was tested? Also linking to GH issue helps reviewer.
  2. How does a developer switch from using the real aggregate proof to the hollowed out proof?
  3. [Optional but highly encouraged] the point of this issue is to make it easier / fasted to develop on this repo. We should include that in the description of Aggregated empty proofs for blEVM #144. In this PR, we could add to the README that it takes "x" minutes to generate a real aggregate proof for 2 EVM blocks. It takes "y" minutes to generate a hollowed out aggregate proof. That way developers know how long it should take to generate. See
    How long does it take to generate a proof?
    | SP1_PROVER | Program | Time |
    |------------|------------|------------|
    | network | blevm-mock | 30 seconds |
    | network | blevm | 6 minutes |
    for an example

@ninabarbakadze ninabarbakadze marked this pull request as draft February 25, 2025 08:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Aggregated empty proofs for blEVM
3 participants