bug: in-memory prover fails

[sdwoodbury]

using commit eace7cd9d1ff73d9a814fe24ec6fb55fc9f238ac I built the code and generated a witness as described in the readme. I used transaction 0x1e903dba5031fccd94ade18c6903f325bb90f83240bb95f0152eb56fa2c6da07 from the sepolia testnet for witness generation. I ran the program as follows:

env RUST_MIN_STACK=33554432 \
ARITHMETIC_CIRCUIT_SIZE="15..28" \
BYTE_PACKING_CIRCUIT_SIZE="9..28" \
CPU_CIRCUIT_SIZE="12..28" \
KECCAK_CIRCUIT_SIZE="14..28" \
KECCAK_SPONGE_CIRCUIT_SIZE="9..28" \
LOGIC_CIRCUIT_SIZE="12..28" \
MEMORY_CIRCUIT_SIZE="17..30" \
target/release/leader prove \
--runtime in-memory \
--num-workers 1 \
--input-witness ~/0x1e903dba5031fccd94ade18c6903f325bb90f83240bb95f0152eb56fa2c6da07.json

After generate_txn_proof there's a kernel panic and the stack trace gives me no clue as to what failed.

[Nashtare]

Hi! Thank you for reporting this. We are aware that the zkEVM prover still fails to provide proofs for some Shanghai blocks. The team is aware of it and is working on fixing the bugs. It may take some time for this specific block to be successfully proven, so I'd suggest you try playing with other blocks in the meantime!

[Cryptoflip12345]

using commit eace7cd9d1ff73d9a814fe24ec6fb55fc9f238ac I built the code and generated a witness as described in the readme. I used transaction 0x1e903dba5031fccd94ade18c6903f325bb90f83240bb95f0152eb56fa2c6da07 from the sepolia testnet for witness generation. I ran the program as follows:

env RUST_MIN_STACK=33554432 \
ARITHMETIC_CIRCUIT_SIZE="15..28" \
BYTE_PACKING_CIRCUIT_SIZE="9..28" \
CPU_CIRCUIT_SIZE="12..28" \
KECCAK_CIRCUIT_SIZE="14..28" \
KECCAK_SPONGE_CIRCUIT_SIZE="9..28" \
LOGIC_CIRCUIT_SIZE="12..28" \
MEMORY_CIRCUIT_SIZE="17..30" \
target/release/leader prove \
--runtime in-memory \
--num-workers 1 \
--input-witness ~/0x1e903dba5031fccd94ade18c6903f325bb90f83240bb95f0152eb56fa2c6da07.json

After generate_txn_proof there's a kernel panic and the stack trace gives me no clue as to what failed.