Steps to reproduce EmulationNoCompleted error in ZisK.
The workload repo allows running benchmarks not only in mainnet blocks, but in EEST benchmarks cases that we worked on some time ago to create the worst possible scenarios for different gas limits for different opcodes/precompiles/protocol-weaknesses.
The way we created this is to create worst-case blocks under different gas limits to:
- For 45M gas limit, know which are today’s worst cases.
- For lower gas limits (e.g., 10M) to have downsized attacks that we can benchmark faster, or might be relevant like for tx gas capping.
- Higher gas limits than 45M to project how mainnet bumping the gas limit can affect provers.