This repository has been archived by the owner on Jul 5, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 857
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
### Description The main goal of this PR is to allow for the dynamic selection of sub-circuit parameters (`CirctuisParams`) based on the block provided as input. After this change there are 2 options for selecting circuit parameters: 1. Having them fixed before witness generation 2. Leaving them unset as `DynamicCP` and be dynamically generated together with the witness. ### Issue Link Close #954 ### Type of change - [ ] Bug fix (non-breaking change which fixes an issue) - [x] New feature (non-breaking change which adds functionality) - [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected) - [ ] This change requires a documentation update ### Contents - Addition of trait `CircuitsParams`, implemented by the `ConcreteCP` (old `CircuitsParams`) and the new `DynamicCP` - Addition of generics in all the structs that previously contained `CircutisParams`: `Block`, `CircuitInputBuilder, `CircuitInputStateRef` - Modify unit tests to use dynamic parameters - Modify variadic test to use default fixed parameters instead of dynamic parameters ### Rationale ### How Has This Been Tested? With the existing tests. ### Potential improvements Sometimes it may be difficult to track which structures contain the circuit parameters. For clarity, we could remove `CircuitsParams` from `Block` and create a new structure containing both, something like `BlockWithParams` or `CircuitInputs`. (suggested by @ed255 ) <hr> Big thanks to @ed255 for providing the ideas and design on how to solve this issue !!:partying_face: --------- Co-authored-by: Eduard S. <[email protected]>
- Loading branch information
1 parent
d067644
commit 9e974d9
Showing
62 changed files
with
415 additions
and
377 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.