zkevm-circuits
zkevm-circuits copied to clipboard
privacy-scaling-explorations
To automatically do refactor like https://github.com/privacy-scaling-explorations/zkevm-circuits/pull/852. We can do this by `configure` the circuit and collect every polynomial used in gates/lookups, and compare them to queries in `ConstraintSystem` to assert...
currently different circuits needs witness from different sources/structs. Eg: https://github.com/privacy-scaling-explorations/zkevm-chain/blob/68982510b93fd34e06f5d2f444a3807b90668b40/prover/src/compute_proof.rs#L122 witness::Block and geth_types::{Transaction, Block} are all needed. I think we'd better unify all the procedure, so we post-process geth trace...
Description: - https://github.com/privacy-scaling-explorations/mpt-witness-generator
Depends: #740 and #812 Description: - Repo https://github.com/privacy-scaling-explorations/mpt-witness-generator (main branch) - Could require some changes to the API to this bindings. Another task: - Review the changes and witness generation...
Description: - Check the API defined by MPT and the API used by the other circuits match (main goal) Dependency - Connect Witness generation to zkEVM circuits https://github.com/privacy-scaling-explorations/zkevm-circuits/issues/811
Proposal: - Get it merge as fast as possible - Do a very quick review (like tests taking too long) - Then find the gaps with the spec and address...
https://github.com/privacy-scaling-explorations/zkevm-circuits/blob/77c93c1016c672fe51b2a63713d45d17946eb20f/zkevm-circuits/src/evm_circuit/util/constraint_builder.rs#L1133-L1147
Initial discussions here https://hackmd.io/THeVDmIkRSSqyb-lHXkRmQ Functionalities similar to #775