feat: support for additional fields on TransactionReceipt and Block #66
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.
Motivation
Right now we don't have support for additional fields on both
Block
andTransactionReceipt
, and we need support for these as foundry and other projects make use of the equivalent field on ethers types. This specifically makes supporting L2 blocks/receipts easier, as we can accomodate their additional field.Solution
Add the
OtherFields
struct which can be transparently deserialized, and add it toBlock
andTransactionReceipt
.PR Checklist