core/tracing: add GetTransientState method to StateDB interface for accessing transient state data #30531
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…accessing transient state data
|
Is there anything else that we need to add? would appreciate if we do it in one PR. |
|
I think not, I tested a lot of functionality and it seems to me that all the necessary things are there. Thanks |
holiman
pushed a commit
that referenced
this pull request
Nov 19, 2024
Allows live custom tracers to access contract transient storage through the StateDB interface.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The previous tracing implementation gave access to
TransientState, in the current one is missing, so I extended the interface. I checked and no hooks collect it.This gives the ability to analyze the transient state for custom tracers (e.g. mine).