Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Get Traces Limits From
prover/backend/config
package. (#52)
### Context In [this issue](https://github.com/Consensys/zkevm-monorepo/issues/1420) 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 a `WizardIOP` constraint system assumes that said configuration variables (the traces limits) are hard-coded as go constants (e.g., see [these](https://github.com/Consensys/zkevm-monorepo/blob/main/prover/zkevm/define/size.go) [two](https://github.com/Consensys/zkevm-monorepo/blob/main/prover/zkevm/define/size_large.go) 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](https://github.com/Consensys/corset/blob/f8ca04a74435012447630fad76ebd23a52f07c9d/src/exporters/wizardiop.go#L50). Therefore, the `corset` 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 ``` cargo run -- wizard-iop -o $WORKSPACE/zkevm-constraints/mxp $WORKSPACE/zkevm-constraints/lookup_tables/tables/instruction_decoder.lisp ``` --------- Co-authored-by: delehef <franklin.delehelle@odena.eu>
- Loading branch information