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

fix: add memory_layout to preprocessing so verifier doesn't rely on the prover #494

Merged
merged 6 commits into from
Nov 1, 2024

Conversation

sagar-a16z
Copy link
Contributor

Memory layout is a public input to the Jolt verifier and doesn't need to be trusted from the Proof

fixes #490

@sagar-a16z sagar-a16z force-pushed the sagar/refactor_memory_layout branch from 124f0df to ac2a9af Compare October 31, 2024 18:40
@sagar-a16z sagar-a16z changed the title fix: Move JoltDevice to preprocessing fix: add memory_layout to preprocessing so verifier doesn't rely on the prover Oct 31, 2024
@sagar-a16z sagar-a16z marked this pull request as ready for review October 31, 2024 18:46
@sagar-a16z sagar-a16z requested a review from moodlezoup October 31, 2024 21:10
self.build();
let elf = self.elf.unwrap();
let elf = self.elf.clone().unwrap();
Copy link
Collaborator

Choose a reason for hiding this comment

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

we shouldn't need this clone, we pass in elf by reference below

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Self.elf is an Option<PathBuf> the clone is required to unwrap it. Previously this API would consume itself trace(mut self), which seemed weird to me so I changed it to trace(&mut self) and that means we can't just pull elf out of Self anymore since we just have a ref to Self.

Does that make sense?

jolt-core/src/jolt/vm/rv32i_vm.rs Show resolved Hide resolved
@moodlezoup moodlezoup merged commit dbb76f3 into main Nov 1, 2024
10 checks passed
@sagar-a16z sagar-a16z deleted the sagar/refactor_memory_layout branch November 1, 2024 16:09
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.

Prover can use arbitrary memory layout
2 participants