Prover tests for empty blocks

[OlivierBBB]

Note

Adds parameterized empty-block test scenarios and Besu-backed execution support (with null-transaction handling), plus minor import and test-runner tweaks.

• Tests:
  • EmptyBlockTests: Refactor to parameterized tests covering multiple E/N block patterns; add @Execution(SAME_THREAD); introduce BlockType and helper builderFromBlockTypeList; allow running against Besu via runWithBesu and validate logs only when not using Besu.
  • BlockhashTest: Add @Execution(SAME_THREAD).
• Testing infrastructure:
  • MultiBlockExecutionEnvironment: Add runWithBesuNode option; when enabled, translate empty blocks to null transactions and execute via BesuExecutionTools (one tx per block); keep existing replay path otherwise.
  • BesuExecutionTools: Accept and handle null transactions for empty blocks; add preconditions; adjust conflation tracing range for empty vs non-empty blocks; minor cleanup and state checks.
• Minor:
  • OsakaUserTransaction: Update EIP-7825 gas limit cap import to TraceOsaka.

^{Written by Cursor Bugbot for commit f5e8fd6. This will update automatically on new commits. Configure here.}

[cursor]

Bug: Null Transaction Handling Bug

When oneTxPerBlock is false, the executeTest method attempts to send all transactions without checking if they are null. This leads to a NullPointerException when calling .encoded() on a null transaction, a check that is present in the oneTxPerBlock true path.

 

[cursor]

Bug: Transaction List Nulls Cause Block Number Errors

The firstBlockNumber calculation is off when oneTxPerBlock is true and the transactions list includes nulls. The current logic subtracts numberOfLeadingEmptyBlocks from an already adjusted firstBlockNumber, which can lead to invalid block numbers (like zero or negative) and an incorrect tracing range.

 

[cursor]

Bug: Block Number Calculation Incorrect for Non-Standard Genesis Blocks

When blockNumbers.isEmpty() is true (all transactions are null), firstBlockNumber is set to 1 and finalBlockNumber is set to transactions.size(). This assumes the starting block number is 1, but blocks may start at a different number. The calculation should use the genesis block configuration or track the actual block numbers created, not hardcode 1.

 

[cursor]

Bug: Null Transaction Handling Mismatch

The else branch, which sends all transactions in a single block, doesn't filter out null transactions from the transactions list. This causes a NullPointerException when txs.next() returns null and encoded() is called, unlike the if branch which correctly handles these null entries.

 

[cursor]

Bug: Test Initialization Order Causes Null References

Instance fields (senderKeyPair, receivingAccount, storingNumber, logging, storing, reading) are initialized with references to chainConfig, but chainConfig is only initialized by the test framework after instance field initialization. This will cause these fields to use a null or uninitialized chainConfig, leading to NullPointerException or incorrect bytecode compilation. These fields should either be initialized lazily in a @beforeeach method or moved into the test methods themselves.

 

[amkCha]

Thanks for fixing the daily ref tests !!

[cursor]

Bug: Early Exit Prevents Tracer Initialization

When runWithBesuNode is true, the run() method returns early without initializing the tracer field, leaving it null. Tests that call getHub() after running with Besu node will encounter a NullPointerException since getHub() returns tracer.getHub() and tracer is null.

 

[amkCha]

addressed

[cursor]

Bug: Instance fields initialized before chainConfig is set

The instance fields receivingAccount, storingNumber, and logging use BytecodeCompiler.newProgram(chainConfig) during initialization, but chainConfig is a static field initialized in the parent class's @BeforeAll method. In JUnit 5, instance fields are initialized when the test class is instantiated, which occurs before @BeforeAll methods execute. This means chainConfig will be null when these fields are initialized, causing a NullPointerException when the tests run.

Additional Locations (2)

• arithmetization/src/test/java/net/consensys/linea/zktracer/EmptyBlockTests.java#L89-L90
• arithmetization/src/test/java/net/consensys/linea/zktracer/EmptyBlockTests.java#L102-L103