`cmd/evm` can't invoke post-merge opcodes correctly about go-ethereum HOT 3 OPEN

I'll get to learn about how goevmlab works.

I'm not saying you have to use goevmlab (although you probably should :) ) , but for differential fuzzing, statetest is the reference input format.

from go-ethereum.

Minimal repro

$ go run ./cmd/evm --nomemory=false --json --code 5f run   
{"pc":0,"op":95,"gas":"0x2540be400","gasCost":"0x0","memSize":0,"stack":[],"depth":1,"refund":0,"opName":"PUSH0"}
{"pc":0,"op":95,"gas":"0x2540be400","gasCost":"0x0","memSize":0,"stack":[],"depth":1,"refund":0,"opName":"PUSH0","error":"invalid opcode: PUSH0"}
{"output":"","gasUsed":"0x2540be400","error":"invalid opcode: PUSH0"}

The problem seems to be that it chooses IsMerge to false, because it doesn't have any randao input.

As I'm fuzzing evm implementations, to let geth/evm support new opcodes is important to me.

I'd advise you to use evm statetest. It's what I use in goevmlab, https://github.com/holiman/goevmlab/tree/master/evms , e.g geth https://github.com/holiman/goevmlab/blob/master/evms/geth.go#L91 , besu https://github.com/holiman/goevmlab/blob/master/evms/besu.go#L67 etc.

from go-ethereum.

Thanks for your quick reply! @holiman. I'll get to learn about how goevmlab works.

from go-ethereum.