Thanks to visit codestin.com
Credit goes to github.com

Skip to content

traceAddress from debug_traceBlockByNumber is not correct #9784

Description

@ella-quicknode

System information

Erigon version: erigon/2.59.0/linux-amd64/go1.21.8"
OS & Version: Ubuntu 22.04.4 LTS (GNU/Linux 6.5.0-1019-oracle x86_64)
Consensus Layer: Lighthouse
Chain/Network: ETH Mainnet

Expected behaviour

Using debug_traceBlockByNumber the traceAddress should be consistent to what you see on trace_block method.
traceAddress from trace_block method is consistent to Geth trace output.

Example block 16494085 (0xfbae05) filter with address 0xbaae833f06dac8ef2ab8dea7b707dbcfa048a5f6

Geth trace on etherscan here.

Actual behaviour

Attaching 2 screen prints on the traceAddress discrepancy for better demostration.

trace_block

debug_traceBlockByNumber

Steps to reproduce the behaviour

Use this command on the node:

curl -X POST http://localhost:8545 -H 'Content-Type: application/json' -d '{"method":"debug_traceBlockByNumber","params":["0xfbae05", {"tracer": "callTracer"}],"id":1,"jsonrpc":"2.0"}' > response.json

I used a script to index the array for trace address.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions