Log.BlockTimestamp is 0 for ethclient.BlockReceipts and potentially other methods that return Log

[DenyVeyten]

System information

go-ethereum 1.16.1

Expected behaviour

Log.BlockTimestamp is never 0

Actual behaviour

Log.BlockTimestamp is 0 for some eth methods

Steps to reproduce the behaviour

1. call ethclient.BlockReceipts for any block (https://ethereum-rpc.publicnode.com/ was used as RPC node)
2. inspect a Log for some Receipt

Workaround

Get block timestamp from Header, e.g. via ethclient.HeaderByNumber Is this the most "lightweight" call as of today to get a timestamp of a block?

Additional info

Probably related #31887 (comment)

[Muzry]

It has been fixed. I tested Geth from master, and Geth v1.16.2; the issue could not be reproduced on either.
Below are the test results.

curl --location 'http://127.0.0.1:8545' \
--header 'Content-Type: application/json' \
--data '{
    "jsonrpc":"2.0",
    "method":"eth_getBlockReceipts",
    "params":["0x4f7"],
    "id":1
  }'
{"jsonrpc":"2.0","id":1,"result":[{"blockHash":"0x48ee8f0003831f0af7e391128bff2ab814caa63396cbd427ad790d5b56efec25","blockNumber":"0x4f7","contractAddress":null,"cumulativeGasUsed":"0x8ea8","effectiveGasPrice":"0x8","from":"0x71562b71999873db5b286df957af199ec94617f7","gasUsed":"0x8ea8","logs":[{"address":"0xbcdfc870ea0c6463c6ebb2b2217a4b32b93bcfb7","topics":["0x0f6798a560793a54c3bcfe86a93cde1e73087d944c0ea20544137d4121396885","0x00000000000000000000000071562b71999873db5b286df957af199ec94617f7"],"data":"0x00000000000000000000000000000000000000000000003635c9adc5dea00000","blockNumber":"0x4f7","transactionHash":"0xa5f10a700bab4fd36abab96d5cf264f3a262743ea9edab0837559fa65d7387c3","transactionIndex":"0x0","blockHash":"0x48ee8f0003831f0af7e391128bff2ab814caa63396cbd427ad790d5b56efec25","blockTimestamp":"0x68a84f4e","logIndex":"0x0","removed":false},{"address":"0xbcdfc870ea0c6463c6ebb2b2217a4b32b93bcfb7","topics":["0xddf252ad1be2c89b69c2b068fc378daa952ba7f163c4a11628f55a4df523b3ef","0x0000000000000000000000000000000000000000000000000000000000000000","0x00000000000000000000000071562b71999873db5b286df957af199ec94617f7"],"data":"0x00000000000000000000000000000000000000000000003635c9adc5dea00000","blockNumber":"0x4f7","transactionHash":"0xa5f10a700bab4fd36abab96d5cf264f3a262743ea9edab0837559fa65d7387c3","transactionIndex":"0x0","blockHash":"0x48ee8f0003831f0af7e391128bff2ab814caa63396cbd427ad790d5b56efec25","blockTimestamp":"0x68a84f4e","logIndex":"0x1","removed":false}],"logsBloom":"0x00000000000000000000000000000000040000000000000000000000004000000000000000000000000000000000000000000000000000000000000000000000000000000020000000000008000000000000200000000000000000000000000000000000020000000000000081000800000000000000400000000010000000000000000000000000000000000000000000000000000000000000000000000000000080000020000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000020000000000000000000000000000000000000000000000000000000000000000000","status":"0x1","to":"0xbcdfc870ea0c6463c6ebb2b2217a4b32b93bcfb7","transactionHash":"0xa5f10a700bab4fd36abab96d5cf264f3a262743ea9edab0837559fa65d7387c3","transactionIndex":"0x0","type":"0x2"}]}

Additionally, I tested the Geth SDK. All log block timestamps were non-zero.

Block timestamp from Header: 1755860814
Receipt[0] Log[0] BlockTimestamp: 1755860814
Receipt[0] Log[1] BlockTimestamp: 1755860814
Total Logs: 2, Logs with zero timestamp: 0
All Log.BlockTimestamp fields are non-zero.

The issue seems to have been caused by https://ethereum-rpc.publicnode.com/ not being updated.

[s1na]

It has been fixed. I tested Geth from master, and Geth v1.16.2; the issue could not be reproduced on either.

@Muzry thanks for confirming and reporting. As you mentioned it seems to have been caused by an out-of-date server. Closing the issue now.