Currently in limited beta and available by invitation only. Request early access via our Dashboard.
- ERC 20 Paymasters
- Verifying Paymasters
ERC 20 Paymasters
ERC 20 paymasters allow end users (smart account wallets) to cover transaction fees without using a network’s native gas token. In essence, this gives the ability to cover transaction fees using ERC 20 tokens like USDC.Verifying Paymasters
Verifying Paymasters are more involved, in that they are typically used alongside some policies that determine whether or not a transaction’s entire gas fee will be covered by the paymaster. For example, only sponsor transactions that interact with a specific smart account, accessing a particular method.Using A Paymaster URL
Using a paymaster as a dapp involves leveraging thecapabilities
field present in EIP 5792 calls.
Setting a field like so:
calls
is an array of 5792 calls to send, paymasterServiceUrl
is a
string containing the paymaster URL and context
is an optional configuration object for the paymaster.
The context
field is paymaster specific and it might be required depending on the Paymaster implementation.
Naturally, since interacting with paymasters requires using
sendCalls
as
opposed to writeContractAsync
or similar, this will require code changes.A general guide on adapting existing code can be found
hereAs a Dapp, that is all that is required to take advantage of verifying paymasters. The rest would be handled wallet side. If the calls match the criteria set in the paymaster’s policy, then the calls’ gas would be sponsored. However, if it does not, then the transaction would be cancelled. Example implementation can be found here.