-
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
trace_ API disagrees with debug_ API #12318
Comments
Same with the state change tracer (using trace_replayTransaction). It is also reporting a higher state diff than it should. So when transaction is being replayed for some reason a higher value is being transferred than it should. |
Hi, do you have any details on your setup? What version of Erigon are you running, are you running Erigon or |
I'm guessing it is a similar issue to this: paradigmxyz/reth#11845. Basically in one of the endpoints the beacon root system call isn't applied prior to tracing. |
Hey @shohamc1 👋 Details of that Erigon node:
|
Expected behaviour
The call trace from debug_traceTransaction should agree with the call trace from trace_transaction. However we are seeing a difference. Please see also discussion: ethereum/go-ethereum#30593 for more context.
Actual behaviour
debug_traceTransaction
trace_transaction
We can see the value of
trace[1]
in debug_ is reported as0x2386f26fc10000
whereas in trace_ is reported as0x16345785d8a0000
.The text was updated successfully, but these errors were encountered: