log's topics is null

[amncjf]

Checklist

• This is not a security-related bug/issue. If it is, please follow please follow the security policy.
• I have searched on the issue tracker and the lotus forum, and there is no existing related issue or discussion.
• I am running the Latest release, the most recent RC(release canadiate) for the upcoming release or the dev branch(master), or have an issue updating to any of these.
• I did not make any code changes to lotus.

Lotus component

• lotus daemon - chain sync
• lotus fvm/fevm - Lotus FVM and FEVM interactions
• lotus miner/worker - sealing
• lotus miner - proving(WindowPoSt/WinningPoSt)
• lotus JSON-RPC API
• lotus message management (mpool)
• Other

Lotus Version

All versions

Repro Steps

1. curl --data '{"jsonrpc": "2.0", "id":1, "method": "eth_getBlockByHash", "params": ["0x53b5686d0309e3617e02c8e3f2fe8a5facc14672d746afd948a2db8eb29f292b",true] }' -H 'Content-Type:application/json' https://api.calibration.node.glif.io/rpc/v1

Describe the Bug

https://api.calibration.node.glif.io/rpc/v1 has obtained the receipt of transaction 0x53b5686d0309e3617e02c8e3f2fe8a5facc14672d746afd948a2db8eb29f292b, where the logIndex is 7 and the topics of the log are null. Why? topics are always not null

Logging Information

N/A

[maciejwitowski]

Looks like this has already been discussed on Slack.
This can happen if the contact uses LOG0.

[amncjf]

It is recommended to set the topics of log0 to [] instead of null, so that I can use getLogs of ethers instead of writing it myself

[maciejwitowski]

Not sure why it results in null but I agree [] would make more sense.

[amncjf]

There is also better compatibility!