feat(specs): Introduce comprehensive state tracking objects #2063
+782
−325
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.
🗒️ Description
This PR adds two new types for tracking state:
TxStateTracking: Tracks reads and writes that happened during a transaction.BlockStateTracking: Tracks reads and writes that happened during a block.BlockStateTrackingshould be convertible into a BAL. Most of the functions of theStateobject have superseded, it is still used to:A future PR should be replace it with a suitable interface to do those things.
Note: This PR is an early draft. All pre-Amsterdam forks are broken (need back-porting) and code cleanup is required. EIP-7610 is unimplemented.
Next steps
✅ Checklist
toxchecks to avoid unnecessary CI fails, see also Code Standards and Enabling Pre-commit Checks:uvx tox -e statictype(scope):.- [ ] All: Set appropriate labels for the changes (only maintainers can apply labels).Cute Animal Picture