Get Traces Limits From prover/backend/config
package.
#52
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Context
In this issue we are adding a new
config
pkg responsible for reading in TOML configuration files defining configuration variables for the prover.The existing
corset
code responsible for producing aWizardIOP
constraint system assumes that said configuration variables (the traces limits) are hard-coded as go constants (e.g., see these two files).As part of the issue linked above, the new
config
pkg reads in the traces limits from the configuration file, then subsequent code embeds them into a*zkevm.Builder
object passed as parameter here. Therefore, thecorset
code has to slightly change to now read the traces limits from this object.This Change
The only change is the formatting string in the
wizardiop.rs
responsible for generating the go code.Test
Tested the change with