Gelato Relay, as easy as 0xabc...
- Gelato Relay's main smart contract is deployed at:
0xaBcC9b596420A9E9172FD5938620E265a0f9Df92on every supported network!
- Gelato Relay's ERC-2771 compatible smart contract is deployed at:
0xBf175FCC7086b4f9bd59d5EAE8eA67b8f940DE0don every supported v2 network!
After reading this page:
- You'll go through a decision process to understand the best way to integrate with Gelato Relay.
- You'll know exactly which SDK/API method is for you.
Depending on your final destination, please click the corresponding number to find about your chosen SDK method:
If you do not want to sponsor your user's gas, you will use the callWithSyncFee SDK method with the SyncFee payment method, and this will require you to deploy a new contract (or upgrade if you can) to be compatible with Gelato's relay context contracts.
Gelato Relay allows for partial sponsoring of gas based on certain conditions with developer-defined rules! For example, an app could sponsor user's gas based on a certain NFT being present in their wallet, or perhaps the NFT allows the user to have 10 gasless transactions a day. As a sponsor, you will able to customise with Gelato Relay's sponsor dashboard, coming soon™.
- Gelato handles user signature verification: go ahead and use sponsoredCallERC2771 where Gelato handles user signature verification for you. In this method, you can use ERC-2771's
_msgSender()to validate your relay calls on-chain. This will require an upgrade to your target contract for
ERC2771Contextsupport, if it does not support it already.
- You handle user signature verification: If your app workflow already handles its security in-house (i.e. use of user signatures, replay/reentrancy protection etc.) and you do want to sponsor all of your user's gas, you are ready to use Gelato Relay without any change to your existing smart contract logic. This will be using the sponsoredCall method.