Skip to content
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

Closed
ella-quicknode opened this issue Jun 30, 2023 · 8 comments · Fixed by #8858
Closed

Gas Value is wrong in debug_trace* method for blocks in archive #7831

ella-quicknode opened this issue Jun 30, 2023 · 8 comments · Fixed by #8858
Assignees

Comments

@ella-quicknode
Copy link

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.

curl -X POST http://localhost -H 'Content-Type: application/json' -d '{"method":"debug_traceBlockByNumber","params":["0x107490F", {"tracer": "callTracer"}],"id":1,"jsonrpc":"2.0"}' | jq '.result[0].result.gas'

You will see an output "0x250bf" which is wrong. The correct gas value is 0x2aa2f.

Associated transaction on ETH scan is here

Example 2

Another example cURL for getting traceTransaction. Please replace with a valid URL.

curl -X POST http://localhost -H 'Content-Type: application/json' -d '{"method":"debug_traceTransaction","params":["0x3d7651e7556cd62950ee34fc5871bba468c3f04e547767da31db123d4ed1007c", {"tracer": "callTracer"}], "id":1,"jsonrpc":"2.0"}'

You will get a wrong gas value 0x370ff, the correct value is: 0x3eb40

Associated transaction on ETH scan is here.

@jiOnederfull
Copy link

How's going on this issue?

@ella-quicknode
Copy link
Author

The issue still persists. You can still try reproduce with my above payload, you will see node client is returning incorrect value.

@jiOnederfull
Copy link

jiOnederfull commented Jul 25, 2023

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.

  • version: 2.48.0-stable-084acc1a
curl {endpoint} \
 -X POST \
 -H "Content-Type: application/json" \
 --data '{"method":"debug_traceBlockByNumber",
       "params":[
           "0xdf23e", 
           {"tracer": "callTracer"}
          ],
        "id":1,
        "jsonrpc":"2.0"
       }'

image
image

@github-actions
Copy link

github-actions bot commented Sep 4, 2023

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.

@github-actions github-actions bot added the Stale label Sep 4, 2023
@qk-santi
Copy link

qk-santi commented Sep 7, 2023

Keeping it open

@yperbasis yperbasis removed the Stale label Sep 7, 2023
@yperbasis yperbasis self-assigned this Sep 7, 2023
@crazyokey1990
Copy link

same problem

@nateless
Copy link

Any updates on this task?

@yperbasis yperbasis linked a pull request Nov 29, 2023 that will close this issue
@yperbasis
Copy link
Member

Any updates on this task?

Fixed in v2.55.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

6 participants