Eduard S.
Eduard S.
See https://github.com/privacy-scaling-explorations/zkevm-circuits/blob/f185b1276b67b730448724930b33c72a342ad96a/zkevm-circuits/src/evm_circuit/execution/end_block.rs#L89-L91 Investigate current execution client behavior and see if this applies and how feasible is to solve it now.
For some time we've had discussions about fuzzying the circuits with two possible aims: - Find correctness bugs (in witness generation code / circuit constraints) - Find soundness bugs (in...
In https://github.com/privacy-scaling-explorations/zkevm-circuits/pull/484 we have the first implementation of the tx circuit. For each tx it requires (due to the signature verification): - ~205 columns - ~170k rows Things to do:...
In https://github.com/privacy-scaling-explorations/zkevm-circuits/pull/994 we introduced methods for each circuit to report the minimum number of rows required. The SignVerify circuit uses halo2wrong, making the number of rows required opaque. The number...
Currently the Transaction Table contains `TxSignHash` which is the hash of the Transaction without the signature; which is used for signature verification. This field is used to verify the validity...
Related to https://github.com/privacy-scaling-explorations/zkevm-specs/pull/354 and https://github.com/privacy-scaling-explorations/zkevm-specs/issues/259 The current design involves encoding non-existing accounts in the State Circuit as account with code_hash = 0. Notice that the update proofs that the MPT...
Complete the implementation of the `check_witness` function which checks that a witness assignment passes all the constraints from a middleware Circuit. The missing parts were: - Simulate blind rows -...
We can improve our unit test coverage in order to reduce the possibility of introducing bugs while refactoring and optimizing the code (as it happened in https://github.com/privacy-scaling-explorations/halo2/issues/321) Here are some...