-
Notifications
You must be signed in to change notification settings - Fork 20.2k
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
Different data returned from debug_traceTransaction/callTracer in Goerli Archive v1.11.1 and v1.10.26 #26726
Comments
@martinboehm Can you tell me how your geth node runs, because there is a problem with debug_traceTransaction, it always has a error. Thanks! example:
System information
Command
|
@PPianAIC Hi, we are running archive settings of geth My transaction was |
The difference is
|
@holiman Thank you for your answer! Just to make it clear to me. When tracking internal transactions (I mean real transfers that change the balance of an address), we should always ignore the |
If you are tracking the way ether moves across accounts, then yes, you should ignore DELEGATECALL. It can never transfer ether, and it doesn't even change "what address am I at". |
Geth v1.11 changed the tracer and are now returning the delegated value. See ethereum/go-ethereum#26726
Geth v1.11 changed the tracer and are now returning the delegated value. See ethereum/go-ethereum#26726
System information
Goerli Archive
Geth/v1.11.1-stable-76961066/linux-amd64/go1.20.1 vs Geth/v1.10.26-stable-e5eb32ac/linux-amd64/go1.18.5
Prysm/v3.2.0 (linux amd64)
Description
The call to
debug_traceTransaction/callTracer
(anddebug_traceBlockByHash
) returns for some transactions different data in the version v1.11.1 and in the version v1.10.26.Steps to reproduce the behaviour
Call the tracer, for example
curl address:port -X POST --header 'Content-type: application/json' --data '{"jsonrpc":"2.0", "method":"debug_traceTransaction", "params":["0xc0ffcf21dc1881c3f20160b530d76f1d37af7b40552f7c59d3f339bad3023dad", {"tracer": "callTracer"}], "id":1}'
.geth v1.11.1 result:
geth v1.10.26 result:
Apart from reordering of the json fields (which is OK) the difference is that the
DELEGATECALL
on the first level has value0x2386f26fc10000
in the version v1.11.1 and no value in the version v1.10.26. The topgasUsed
value also does not match.The text was updated successfully, but these errors were encountered: