zkevm-specs
zkevm-specs copied to clipboard
privacy-scaling-explorations
Part of https://github.com/privacy-scaling-explorations/zkevm-specs/issues/230 I introduced `StepState` and `Instruction` to `LT`, `GT` and `EQ` opcodes. The circuit constraints and logics are aligned with zkevm-circuits. https://github.com/privacy-scaling-explorations/zkevm-circuits/blob/main/zkevm-circuits/src/evm_circuit/execution/comparator.rs#L31 I would appreciate it if you...
Currently Bytecode circuit is implemented with access to previous row, and with `is_final` indicator as main constraint flag, which seems not that straightforward to think about all kinds of possible...
Closes https://github.com/privacy-scaling-explorations/zkevm-specs/issues/151
Checking if a TX is invalid by adding a few auxiliary columns to the TX table. So far the balance, nonce and intrinsic gas checking is ready. The access list...
# Todo - [ ] implement precompile table lookup - [ ] implement precompile bytecode https://github.com/ashWhiteHat/zkevm-specs/blob/feat/precompile-dataCopy/src/zkevm_specs/evm/typing.py#L255 - [ ] design native call name space - [ ] change dir: precompile...
Close https://github.com/privacy-scaling-explorations/zkevm-specs/issues/275 I added constraints to `check_start` and fixed `test_state_circuit` test.
Close https://github.com/privacy-scaling-explorations/zkevm-specs/issues/334 Related circuit PR https://github.com/privacy-scaling-explorations/zkevm-circuits/pull/973 As issue described, there should be no `transfer` invocation for call related opcodes (except [CALL](https://github.com/ethereum/go-ethereum/blob/master/core/vm/evm.go#L167)) - [CALLCODE](https://github.com/ethereum/go-ethereum/blob/master/core/vm/evm.go#L253), [DELEGATECALL](https://github.com/ethereum/go-ethereum/blob/master/core/vm/evm.go#L301) and [STATICCALL](https://github.com/ethereum/go-ethereum/blob/master/core/vm/evm.go#L340). ~~And callee balance is...
Currently the specs of opcodes that check the state assume that even though an account may not exists, a lookup to an account field will succeed with the default value...
