Required opcodes for basic L2 Bridge

[pinkiebell]

required environmental opcodes for L2 Bridge

• CALLVALUE Implement circuit for CALLER and CALLVALUE opcode #287
• CALLDATASIZE Gadget for opcode calldatasize #329
• CALLDATALOAD op CALLDATALOAD #346
• CALLDATACOPY Bus-mapping for opcode calldatacopy #393
• ORIGIN ORIGIN opcode #360
• CALLER Implement circuit for CALLER and CALLVALUE opcode #287
• BALANCE Circuit for opcode BALANCE #683
• CALL Implementation ExecutionState::CALL #278
• RETURNDATASIZE Add circuit for RETURNDATASIZE opcode #703
• RETURNDATACOPY Add circuit for RETURNDATACOPY opcode #779
• LOG1 Circuit for logs op codes #335
• ISZERO evm_circuit/witness: unimplemented opcode ISZERO #372

#277

---

A basic native deposit (L1 > L2) test in zkevm-chain given commit 223b38c79bc3c615293bfe2cb7d482cf399500a7.

bus_mapping::evm::opcodes

• Using dummy gen_associated_ops for opcode LOG1
• Using dummy gen_associated_ops for opcode SHA3
• Call to account with empty code is left unimplemented

evm_circuit/witness unimplemented opcodes

• SHR
• SHL (Opcode SHL #578)
• NOT (Add NotGadget #565)
• SHA3

zkevm_circuits::evm_circuit::execution::dummy

• ExecutionState::SHA3 is implemented with DummyGadget

---

[DreamWuGit]

What does the L2 Bridge mean here ? the L2 watcher to L1? @pinkiebell

[barryWhiteHat]

L2 bridge means the contract on l2 that allows for deposits and withdraws from L1. So these opcodes need to be supported by zkevm.