Misbehaviour in debug_traceCall #8103
Labels
A-execution
Related to the Execution and EVM
A-rpc
Related to the RPC implementation
C-bug
An unexpected or incorrect behavior
Describe the bug
In reth, we fail to retain
contract address
when using debug_traceCall,however the exact same function, without anychanges, returns the right values in geth
Steps to reproduce
Reth, faulty response:
[":29014e76b0986d11d3cdf684c1f9f21c48ee047d65ac69db0da87068aa883c4f"]
Geth right response:
*just change localhost to this geth node:
https://eth-pokt.nodies.app
*["c02aaa39b223fe8d0a0e5c4f27ead9083c756cc2:29014e76b0986d11d3cdf684c1f9f21c48ee047d65ac69db0da87068aa883c4f"]
as you can see, the contract address before the
:
is missing in reth responeNode logs
No response
Platform(s)
Linux (x86)
What version/commit are you on?
reth Version: 0.2.0-beta.6
Commit SHA: ac29b4b
Build Timestamp: 2024-05-03T11:36:14.574613897Z
Build Features: jemalloc
Build Profile: maxperf
What database version are you on?
Current database version: 2
Local database is uninitialized
Which chain / network are you on?
mainnet
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: