Vlad Bochok

I am so sorry, I haven't see your comment and totally forgot about this. There is a explanation on the same issue of fork - https://code4rena.com/reports/2022-08-mimo#h-04-incorrect-implementation-of-access-control-in-mimoproxyexecute. If that doesn't provide...

> I'm struggling to understand what is the problem. Yes, it is the case that an envoy can append "trash" data when calling execute, but if the first 4 bytes...

Hey @pcaversaccio, thanks for looking into the code! We want to distinguish all the EVM precompiles (ecrecover/sha256/RIPEMD-160/...) and zkSync-specific ones (only keccak256 at the moment). The idea behind this is...

Reference of place where constant is used: - https://github.com/matter-labs/era-system-contracts/blob/main/contracts/AccountCodeStorage.sol#L131

The contract deployer is a contract that is responsible for all create/create2 calls. Here is the place which prevents users from deploying on the system contracts zone (still a very...

The deploying to the address(0x01) is basically a hash collision. If it will be the case, we will have a bigger problem. From what I see on the Geth, there...

> "The idea behind this is that EVM precompiles are guaranteed to have zero code size" => This is actually a probabilistic statement that holds P-a.s. (and let's hope it...

> A non-existent account in [EIP-1052](https://eips.ethereum.org/EIPS/eip-1052) refers to an address that does not adhere to [EIP-55](https://github.com/ethereum/EIPs/blob/master/EIPS/eip-55.md) correct? Don't understand how the non-existent account relates to the EIP-55 (address checksum). Could...

@codex security review