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

mockprover error hint #270

Merged
merged 2 commits into from
Oct 10, 2024
Merged

mockprover error hint #270

merged 2 commits into from
Oct 10, 2024

Conversation

hero78119
Copy link
Collaborator

No description provided.

@hero78119 hero78119 requested a review from zemse September 24, 2024 06:24
@hero78119 hero78119 force-pushed the feat/mock_prover_hint_msg branch from f0e59e8 to 5e418ef Compare September 24, 2024 06:24
@hero78119 hero78119 force-pushed the feat/mock_prover_hint_msg branch from 5e418ef to 576b33d Compare September 26, 2024 12:49
@@ -548,6 +548,15 @@ impl<'a, E: ExtensionField + Hash> MockProver<E> {
println!("======================================================");
println!("Error: {} constraints not satisfied", errors.len());

println!(
r"Hints:
- If you encounter a constraint error that sporadically occurs in different environments
Copy link
Collaborator

Choose a reason for hiding this comment

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

That sounds like we need to tighten up our constraints? Otherwise, a malicious prover might be able to exploit the UB?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

That sounds like we need to tighten up our constraints? Otherwise, a malicious prover might be able to exploit the UB?

It not related to constraints :) This problem just related to the witnesses where we assuming them to be zero and skip their assignment, but actually unassigned witnesses is "undefined behaviour" due to we enclosed MaybeUint when allocated vector.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Oh, that makes sense.

Btw, why do we do these shenanigans? Have we done a benchmark to check whether MaybeUninit actually helps us?

@matthiasgoergens matthiasgoergens enabled auto-merge (squash) October 10, 2024 01:13
@matthiasgoergens matthiasgoergens merged commit 06590d1 into master Oct 10, 2024
6 checks passed
@matthiasgoergens matthiasgoergens deleted the feat/mock_prover_hint_msg branch October 10, 2024 01:22
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.

2 participants