This repository has been archived by the owner on Feb 6, 2025. It is now read-only.
debug_traceBlockByNumber using flatCallTracer incorrectly returns parentHash instead of blockHash #222
Comments
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Describe the bug
Looks like it was fixed in main reth repo but is still outstanding in v1.1.1 of bsc reth
paradigmxyz/reth#12415
Steps to reproduce
sending a traceBlockByNumber with flatCallTracer
{ "method": "debug_traceBlockByNumber", "params": [ "0x2bd6ea0", { "tracer": "flatCallTracer" } ], "id": 0, "jsonrpc": "2.0" }Gives the following results for blockHash and Number
"blockHash": "0x0857de5b43690e84bf4f8d9f19e97d191fbe5eedef2f4cc36525190283cfd8ef", "blockNumber": 45969056,The return blockHash is for blockNumber 45969055 (i.e. the parent)
Node logs
Platform(s)
Linux (x86)
What version/commit are you on?
reth-bsc-cli Version: 1.1.1
Commit SHA: ca0df04
Build Timestamp: 2025-01-21T05:15:15.371410019Z
Build Features: asm_keccak,bsc,jemalloc
Build Profile: maxperf
What database version are you on?
Couldn't figure out how to set the database dir for this command
Which chain / network are you on?
BSC
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: