-
Notifications
You must be signed in to change notification settings - Fork 1.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
debug_traceCallMany
returns unexpected result
#11541
Comments
debug_traceCallMany
returns unexpected result
yeah Address now serializes as checksumed address, which is still valid hex, so this is likely a no-fix |
Aren't we aiming though to standarize / be as close as possible on the api as the other clients? I believe erigon returns lowercase (as reth did), unless they changed it as well, since I have not used them for a long time. Geths In my case, my scripts were broken with that change. |
This was a breaking change for me too. Erigon and geth both return the keys lowercased. |
Describe the bug
In the past
debug_traceCallMany
withtracer: 'prestateTracer'
andtracerConfig: { diffMode: true }
would return the addresses insidepost
andpre
in lowercase.Since the latest release those addresses are checksumed.
Steps to reproduce
debug_traceCallMany
Node logs
No response
Platform(s)
Linux (x86)
What version/commit are you on?
Commit SHA: ab06997
What database version are you on?
2
Which chain / network are you on?
mainnet
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
No response
Code of Conduct
The text was updated successfully, but these errors were encountered: