[Draft] custom paymaster handler & zyfi integration #51
+235
−3
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
Added paymaster plugin support that enables developers to create external paymaster plugins that integrate with SDK easily.
Key changes:
CustomPaymasterHandler
type and integration in transaction flowwip: add paymaster handler to passkey clients
Additional context
With these changes users can start using external paymasters easily with just 2-3 lines of code
How it works:
customPaymasterHandler
acts as a middleware which is triggered just before signing a transaction.Simplest paymaster handler will just add static
paymaster
andpaymasterInput
to a transaction.The more complex one, like ZyFi's, will send the transaction to some backend service and can fetch not only paymasterInput, but also gas fees since some paymasters may rely on exact values of these fields to account for ERC20 tokens.