-
Notifications
You must be signed in to change notification settings - Fork 841
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
Besu returns empty trace on block 21030627 #7804
Comments
@dylanbutler1 Which besu node are you using to test ? You need to have a Besu forest archive node otherwise you will get an empty response as a Besu Bonsai full node can trace by default |
For visibility, there was a similar issue affecting Erigon as well I am not sure how to resolve this at the moment. |
This is expected behaviour for bonsai (default). You need to have a Besu forest archive node otherwise you will get an empty response as a Besu Bonsai full node can trace by default chain height - 512 blocks. You can test again and if you see this log |
I tested with set_newHead on a bonsai node, to change the head near the block we want to trace, but it didn't work, the node had few issues
cc. @garyschulte |
#7821 adds the capability to move the worldstate along with the blockchain, to a specified block number. Since bonsai is not intended to serve as an archive node, this is a workaround that can be used until bonsai-archive feature is complete. This should allow a trace of block 21030627 on nodes which have the trielog present (nodes which are not pruning their bonsai history), but it can be a foot-gun if used carelessly or incorrectly. |
moving to review for reporter feedback. |
circling back to close this issue, with debug_setHead from #7821 besu is able to get this trace. trace attached: |
Actual behavior
Execute
curl -H "Content-Type: application/json" -d '{"id": 1,"jsonrpc": "2.0","method": "trace_block","params":["0x140e6e3"]}' localhost:8545
Result:
{"jsonrpc":"2.0","id":1,"result":[]}
Expected behavior
Expected response is a list of traces.
cc @joshuafernandes
The text was updated successfully, but these errors were encountered: