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(l2): integrate ExecutionDB, prove execution #956

Merged
merged 83 commits into from
Oct 31, 2024
Merged

Conversation

xqft
Copy link
Member

@xqft xqft commented Oct 23, 2024

Motivation

Integrates the ExecutionDB defined in the ethereum_rust-vm crate with the L2 prover, using it to represent the blockchain state in the zkVM and executing a block.

Description

  • prover server creates the DB from a pre-execution at request
  • the zkVM program takes the DB and block as inputs, and executes the block
  • generate groth16 proof instead of the default, which is not EVM-friendly and has no recursion. Recursion adds proving time and computing requirements, so we must take it into account.

@xqft xqft marked this pull request as ready for review October 24, 2024 16:10
@xqft xqft requested a review from a team as a code owner October 24, 2024 16:10
@xqft xqft changed the title feat(l2): integrate ExecutionDB feat(l2): integrate ExecutionDB, prove execution Oct 24, 2024
xqft and others added 3 commits October 24, 2024 16:44
**Motivation**

the default proof is not EVM-friendly and has no recursion. This change
ups the proving time by x4.

**Description**

- generate groth16 proof
**Motivation**

the block execution program is missing many validation steps, this PR
adds them.

**Description**

- adds validation steps to zkVM program
Base automatically changed from l1/cache_db to main October 30, 2024 16:18
@jrchatruc jrchatruc added this pull request to the merge queue Oct 31, 2024
Merged via the queue into main with commit 7800e5f Oct 31, 2024
11 checks passed
@jrchatruc jrchatruc deleted the l2/integrate_cache_db branch October 31, 2024 14:23
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.

3 participants