`timeboosted` field missed for duration 30s intermittently on `eth_getBlockReceipts`

[ella-quicknode]

Describe the bug

nitro_version: v3.5.5

Call eth_getBlockReceipts for newly emitted block, in the response data, timeboosted is missed out.

Example:
Block 368292544 was first detected on node 09:33:17.307, timeboosted is not presented. The field became present in the response on 09:33:47.361

Another example block 368300201 was first detected on node at 10:05:07.961, timeboosted was added at 10:05:43.447

There is a common thing for this behaviour, that first tx position in the block is always for self transfer on contract address 0x00000000000000000000000000000000000A4B05 .

To Reproduce

Here is a python script scans for tip block on node, then call eth_getBlockReceipts check if timeboosted field is available or not.

Expected behavior

This behaviour happens very intermittently, you can catch a couple in every few minutes.

We need to understand if this is something expected on Nitro?

[leeederek]

Hi Ella, thanks for filing this. Our team will get back to you soon! I can confirm though that the first txn will indeed never be timeboosted. Still looking into your concern about the propagation of timeboosted status to various RPC nodes but I believe, on a first glance, that this is also expected behavior