3️⃣sponsoredCall
Permissionless sponsored transactions
After reading this page:
You'll know how to use the
SponsoredCall
SDK method. This uses the 1Balance payment method, allowing you to sponsor some/all of your user's gas costs.You'll see some code which will help you send a relay request within minutes.
Please proceed to our Security Considerations page and read it thoroughly before advancing with your implementation. It is crucial to understand all potential security risks and measures to mitigate them.
Overview
sponsoredCall
method utilises authentication via a sponsor API key to sponsor gasless transactions for your users securely. The payment method is Gelato 1Balance.
SDK method: sponsoredCall
Arguments:
request
: this is the request body used to send a request.sponsorApiKey
: an API key used to authenticate your sponsorship.options
:RelayRequestOptions
is an optional request object.
Return Object: RelayResponse
taskId
: your unique relay task ID which can be used for tracking your request.
Optional Parameters
See Optional Parameters.
Using Safe smart contract wallets for sponsoredCall
If you need to dispatch transactions from Safe smart contract wallets using Gelato Relay via sponsoredCall
, you can opt to activate Safe-enabled transactions in your Relay Dapp configuration.
Usually when submitting Gelato Relay transactions that originate from Safe smart contract wallets, the Safe wallet address is specified in the target
field of the Relay API request, whereas both the actual target contract address and its calldata
are encoded into the execTransaction
payload. By activating Safe-enabled transactions - accomplished by checking the "Allow sponsored transactions from Safes" box - Gelato Relay will validate your Safe smart contract and decode the target contract address and function selector from the execTransaction
calldata
. It will then apply your pre-configured Relay Dapp rules to these values, rather than to the values given in the Relay request.
If your intention is to deploy Safe smart contract wallets prior to their usage, be sure to whitelist the multicall
contract address in your Relay Dapp. This contract is typically invoked when you deploy a Safe smart contract wallet before it can be used for the first time.
Sending a Request
Request Body
chainId
: the chain ID of the chain where thetarget
smart contract is deployed.target
: the address of the target smart contract.data
: encoded payload data (usually a function selector plus the required arguments) used to call the requiredtarget
address.
Example Code
Since sponsoredCall
assumes you have your own security logic built in (i.e. replay and re-entrancy protection), you can go ahead and generate the payload for your function call and populate a request object.
1. Import GelatoRelaySDK into your front-end .js project
2. Deploy a smart contract
This is an example using Gelato's SimpleCounter.sol
which is deployed on Goerli and Polygon.
3. Generate a payload for your target contract
4. Send the payload to Gelato
Last updated