forked from taikoxyz/zkevm-circuits
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Unify circuit types names and interfaces (privacy-scaling-exploration…
…s#937) Given a circuit Foo: - Unify the struct that contains the columns to FooCircuitConfig - Unify the struct that contains the witness to FooCircuit - Unify the config constructor to FooCircuitConfig::new, following the new SubCircuitConfig trait - Unify the creation of a circuit from a block to FooCircuit::new_from_block following the new SubCircuit trait - Unify the loading of fixed internal tables to load_aux_tables - Unify the synthesis step of subcircuits to synthesize_sub following the new SubCircuit trait - Remove generic associated const from circuit+config types as much as possible - Only possible in TxCircuit. Not possible in PiCircuit due to halo2 Circuit trait - Implement the Circuit trait to all subcircuits uniformly - Move circuit tunning parameters to CircuitParams so that they can be taken from a single source - Add an instance function to all circuits following the new SubCircuit trait Clean up Don't unwrap in non-test code Address some comments from pinkie Address some comments from pinkie and han
- Loading branch information
Showing
35 changed files
with
1,245 additions
and
882 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
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.