Eduard S.

There's a sha256 circuit implementation in the halo2 repository (from zcash) which we should probably use for this precompile: https://github.com/privacy-scaling-explorations/halo2/blob/main/halo2_gadgets/src/sha256.rs

@Brechtpd did you work on this / are you working on this? Not to put any pressure! It's just to figure out if this task should be unassigned :)

> Hey, @ed255 would love to partially help with that issue, can I do that? Hi @eliseygusev and welcome! You are very welcome to help with this issue! :D I...

@CPerezz is currently working on updating `SLOAD` and `SSTORE` @eliseygusev So previously I recommended you to start working on updating `EXTCODESIZE` but it turns out we don't have this opcode...

This week @han0110 @CPerezz and me discussed the approach we have to handle non-existing accounts between the evm-state-mpt circuits; based on some concerns raised by Han. Here are the notes:...

I'm working on updating the specs following https://github.com/privacy-scaling-explorations/zkevm-specs/issues/259#issuecomment-1372429829

Doing the lo/hi approach will require using 2 cells in the places where we were using a single cell to encode a Word. For lookup-able tables that contain words (rw_table,...

> > We would still need to do some range check to guarantee that word_lo and word_hi are 128 bits. > > if check 128 bits range by lookup ,...

Update on this topic after a chat with @barryWhiteHat and @han0110: - We're very confident that this change needs to be done eventually - This change involves a big refactor...

You can add `end_block` to the list :P