-
Notifications
You must be signed in to change notification settings - Fork 463
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
Support tracing of synced, not-processed blocks #4205
Comments
Related issue: #4143 |
This is fairly unlikely to be implemented, would require spinning up database for traces as well as developing a p2p syncing protocol for those traces, which only nethermind would support. I think that what we actually want to do is to have archive node footprint be minimal with state db redesign. |
@LukaszRozmej is there any workaround in the configuration to let's say store last 30K states instead of running archive node, so last 30K blocks will be available for tracing?
|
@gituser we will consider adding this, but nothing we can do short-term |
@LukaszRozmej this is quite crucial feature stopping us from switching completely from OpenEthereum to Nethermind. I think many other users are having similar issue, cause there are many relying on How hard it will be to implement this? Thanks. |
Any update on this or maybe there is some other mechanism to check for ERC-20 transfers or internal ETH transactions besides using tracing? |
@gituser created a plugin that stores the traces and retrives them through json rpc, the only thing is this needs FullSync (but not archive state). |
Describe the bug
I've synced Nethermind on the mainnet to replace OpenEthereum client, but trace_filter returns empty response for some reason:
On my old OpenEthereum node the result is correct though:
I've tried enumerating through latest blocks and found out that the only available blocks for trace_filter are last 2910 +/- 10 blocks from the latest synced block.
E.g. If I try to
trace_filter
block beyound that rangelatest_block
- 3000 nethermind gives me an error:NOTE: old OpenEthereum node was running with fast sync (NOT archive!) and
trace_filter
worked just fine there and consumed ~1.1T, new Nethermind node consumes little bit less ~729G but tracing seems to be not working. I do not want to run archive node, simply because of the storage requirements.To Reproduce
Steps to reproduce the behavior:
Expected behavior
Nethermind should return trace filter info same as OpenEthereum
Desktop (please complete the following information):
1.13.3-14-g2500d3daf
(built from master branch)The text was updated successfully, but these errors were encountered: