Add encoded length methods to transactions#77
Open
manuelmauro wants to merge 3 commits intorust-ethereum:masterfrom
Open
Add encoded length methods to transactions#77manuelmauro wants to merge 3 commits intorust-ethereum:masterfrom
manuelmauro wants to merge 3 commits intorust-ethereum:masterfrom
Conversation
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Summary
Add
encoded_len()andpayload_len()methods to compute transaction sizes without full encoding. This enables transaction size validation for DoS protection, matching reth/alloy's approach.Motivation
Transaction pools need to enforce size limits for performance reasons and to prevent DoS attacks. Reth enforces a default maximum of 128 KB per transaction and validates transactions.
Alloy provides similar methods on transaction envelopes for this purpose.