How does it work?
Gasless transactions on EVM are regular transactions where the transaction signer and the gas payer are two different addresses. Rather than signing with the same address and then submitting their transaction and paying gas, a user can simply sign a transaction payload, and other entities (relayers, solvers, etc.) can submit the transaction on their behalf and sponsor the gas costs. This is not natively possible, so there are custom transaction payloads to enable this: Permit2, EIP-3009, ERC-2771 payloads, ERC-4337 user operations, etc. The core concept is that as long as the transaction execution does not rely ontx.origin (the transaction submitter), any user can sign permit payloads or Smart Account actions (EIP-7702, ERC-4337 user operations etc.) and a relayer can post those payloads on chain by wrapping them in a transaction.
This is where the /execute API comes in. The API allows users to submit raw calls (the partial payload of a regular EVM transaction). It includes the to, data, value and an optional EIP-7702 authorizationList.
How to use it?
This feature is only currently available to Enterprise Partners, learn more about the Enterprise Partner Program to get started. Once you’re an Enterprise Partner you should have an API key and a linked funding address. You’ll then need to fund your app balance, you can learn more about that here.Executing a gasless quote
In this example use case you want to execute a gasless Relay quote with the execute API.1
Get a quote
This flow assumes that the user is using a smart wallet. Use the quote endpoint to get a quote for the transaction you want to execute. The
originGasOverhead indicates how much additional gas overhead will be necessary to include the user operation on the chain as compared to a normal EOA transaction.2
Execute the transaction
With the quote in hand, you can now execute the transaction. You’ll need to pass the data from previous steps to the api.
3
Monitor
Now that the transaction has been submitted, you can monitor the status of the transaction using the requestId from the quote data and the status endpoint.
4
Refer to the quickstart guide for more information on how to monitor the status of a transaction.
More Use Cases
Gasless ERC-20 transfer from ERC-4337 Smart Account
Gasless ERC-20 transfer from ERC-4337 Smart Account
If the user has a Smart Account (such as an ERC-4337 Smart Account), any transaction can be made gasless for the Smart Account by signing an ERC-4337 user operation and submitting it to the /execute API.The only step is to create the user operation, get it signed by the user and then create the final call data of the handleOps call of the Entry Point before submitting to the /execute endpoint.Note: The maxFeePerGas and maxPriorityFeePerGas The ERC-4337 user operation should be 0; it will result in a double payment to the solver (The solver already has adjusted the cost in the quote, so no need for this payment)
1
Create the user operation
2
Send the payload to the /execute endpoint
3
Monitor
Now that the transaction has been submitted, you can monitor the status of the transaction using the requestId returned in the api response and the status endpoint.
Gasless upgrade to an EIP-7702 Smart Account
Gasless upgrade to an EIP-7702 Smart Account
Another example of a flow where the transaction execution does not depend on
tx.origin is the action of upgrading a regular EOA to an EIP-7702 smart account. In this flow, any entity can execute an upgrade payload and a signed EIP-7702 authorizationList from the EOA.The client must pass the correct fields for the to (which is the EOA that is to be upgraded), data is the call data for the initialization of the EOA’s EIO-7702 Smart Account and the authorizationList which contains the signed information about the Smart Account to upgrade to.1
Sign the EIP-7702 authorizationList
2
Send the payload to the /execute endpoint
3
Monitor
Now that the transaction has been submitted, you can monitor the status of the transaction using the requestId returned in the api response and the status endpoint.
Caveats
- Only EVM chains are supported currently.
- Partial sponsorship is not yet supported. Should the fees amount to more than the app balance, the transaction will not be sponsored.
- If the transaction relies on
msg.sender, the transaction signer must be a smart wallet (EIP-7702, ERC-4337, etc). - The API won’t work if the transaction relies on
tx.origin.