General context

Generally the structure of these tests are split into two:

• Setup phase
• Benchmarking block

Setup phase

The setup phase encompasses the pre-state and blocks that are needed in order to setup the block full of a specific block.
An example of this would be a "block full of EXTCODESIZE" where the setup phase would consist of N different contracts being deployed, where N is the number of EXTCODESIZE opcdes we want to put in the final block.

Benchmarking block

For benchmarking, we assume that the final block is the one with the block full of the particular opcode we want to benchmark

0-Parameter set opcodes

Environment Opcodes

• ADDRESS
• ORIGIN
• CALLER
• CALLVALUE
• CALLDATASIZE
• CODESIZE
• GASPRICE
• RETURNDATASIZE

Block & Chain Info

• COINBASE
• TIMESTAMP
• NUMBER
• PREVRANDAO
• GASLIMIT
• CHAINID
• BASEFEE

Blob Opcodes

• BLOBBASEFEE

Stack & Memory Opcodes

• MSIZE
• GAS
• PUSH0

Control Flow Opcodes

• PC

Others

• POP (will be indirectly covered at least in CALLDATASIZE)

Note

• This is a subtask of Create blockchains that consume full gas on single operations. #1453