Added paymaster validation - #117
Merged
Merged
Conversation
AlonzoRicardo
approved these changes
Aug 4, 2026
Merged
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
2 participants
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
Add paymaster-address validation to the ERC-4337 token-paymaster flow. In _applyPaymasterToUserOp, after createPaymasterUserOperation returns, we now compare the RPC-returned paymaster against the configured paymasterAddress (case-insensitive, token mode only) and throw a ConfigurationError on mismatch — before the UserOperation is signed/submitted. Added a matching unit test.
Motivation and Context
paymasterAddress was required in config but never checked against the address the paymaster RPC actually returned. Since the SDK-generated ERC-20 approval targets that returned address, a mismatched/malicious paymaster could receive an approval the user never intended. Failing fast on mismatch ensures the generated approval always targets the configured paymaster. This brings ERC-4337 in line with the existing validation in wdk-wallet-evm-7702-gasless.
Related Issue
PR fixes the following issue:
#116
Type of change