fix: TxBuilder blob fallback to update txType to DynamicFee #18375
+1
−0
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.
When a blob transaction type is forced but no blob data is provided, BuildTx fell back to constructing a dynamic-fee transaction but left the reported txType as Blob. Downstream signers select the signer based on Transaction.Type(), so this mismatch could result in selecting an incompatible signer (e.g., EIP-155 signer) and failing to sign. This change updates txType to types.DynamicFeeTxType in the fallback branch so EthTx.Type() matches the actual raw transaction type, ensuring consistent behavior throughout signing and sending paths.