-
Notifications
You must be signed in to change notification settings - Fork 694
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
debug_TraceBlockByNumber reports lower gasUsed than eth_getTransactionReceipt with Avalanchego v0.12.0 #1618
Comments
Here is a good resource to understand what is happening here: https://dashboard.tenderly.co/tx/ava/0xd69a271d948cf87fc8d8e99568e82a5f87be11eb98b6ef25d01f90920613a54c/gas-usage
I'm going to close this - but if something else seems off please feel free to re-open. |
Hi @StephenButtolph, thanks for replying and that makes sense to me, but we have another endpoint with Avalanchego v0.12.3 returned
Could you please take another look? |
returns:
Gas =
returns:
Gas = These gas values are the same afaict. Which number do you think is inconsistent? (And are you sure that number isn't referring to only the gas spent while performing the calls rather than the total gas usage?) |
@StephenButtolph Let me clarify. We have two node providers that on different client version, and they return different Node on v0.12.0
Node on v0.12.3
According to your previous reply:
I believe Please let me know if there's any wrong takes and also please help take a look on that parity issues in different avalanche clients. Thanks! |
Hey @chaoyaji-cb , thanks for re-opening and reporting this. Funny timing on this one, TLDR v0.12.3 fixed the originally reported weirdness of this issue, so this is an expected change in behavior that we migrated in from geth. When you reported this issue prior to AvalancheGo v1.10.3, the behavior that @StephenButtolph described was correct ie. the debug tracer would NOT count the This discrepancy was fixed upstream in go-ethereum in v1.11.0: https://github.com/ethereum/go-ethereum/releases/tag/v1.11.0 as mentioned in the release notes section on tracing. This change was made in this PR: ethereum/go-ethereum#27029. We migrated the changes through v1.11.4 (including v1.11.0) in v0.12.3 release of Coreth, which changed the behavior and is actually the fix for the originally reported issue. The actual change here is that the tracer now uses
Previously, the
|
Thank you for the in depth explanations! @aaronbuchwald I think for now the |
Sounds good, thanks @chaoyaji-cb ! |
Describe the bug
eth_getTransactionReceipt
shows gasUsed for a specific transaction as: 1,014,929 while thisdebug_TraceBlockByNumber
shows gasUsed: 970,713.To Reproduce
Compare gasUsed for tx:0xd69a271d948cf87fc8d8e99568e82a5f87be11eb98b6ef25d01f90920613a54c
returned by:
vs. gasUsed for that same tx with:
Expected behavior
I would expect that gasUsed for a specific tx would be the same by any method that returns this data.
Operating System
Mac OS Ventura
The text was updated successfully, but these errors were encountered: