-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Gas Value is wrong in debug_trace*
method for blocks in archive
#7831
Comments
How's going on this issue? |
The issue still persists. You can still try reproduce with my above payload, you will see node client is returning incorrect value. |
Yeah, I've also checked that query below produces different results as shown in the picture. I'm curious if ledgerwatch is aware of it and working on fixing it.
curl {endpoint} \
-X POST \
-H "Content-Type: application/json" \
--data '{"method":"debug_traceBlockByNumber",
"params":[
"0xdf23e",
{"tracer": "callTracer"}
],
"id":1,
"jsonrpc":"2.0"
}' |
This issue is stale because it has been open for 40 days with no activity. Remove stale label or comment, or this will be closed in 7 days. |
Keeping it open |
same problem |
Any updates on this task? |
Fixed in v2.55.0 |
System information
Erigon version:
erigon version 2.47.0-stable-5536d645
OS & Version: Ubuntu 22.04.2 LTS (GNU/Linux 5.15.0-1035-oracle x86_64)
Chain/Network: Eth-Mainnet archive node
Expected behaviour
To retrieve correct data in debug trace methods.
Actual behaviour
The gas value from
debug_trace*
methods are wrong.Steps to reproduce the behaviour
Example 1
Run this below cURL, please replace with a valid URL.
You will see an output
"0x250bf"
which is wrong. The correct gas value is0x2aa2f
.Associated transaction on ETH scan is here
Example 2
Another example cURL for getting
traceTransaction
. Please replace with a valid URL.You will get a wrong gas value
0x370ff
, the correct value is:0x3eb40
Associated transaction on ETH scan is here.
The text was updated successfully, but these errors were encountered: