🔗Contract Addresses
Last updated
Last updated
Web3 Functions during the private beta uses a custom deployment of the `Automate.sol` contract as an entry point.
On the Automate
smart contract users create or cancel and Gelato executes tasks. By default, Web3 Functions uses the dedicated msg.sender
module, which means all transactions to the defined destination contract will be routed via your dedicated msg.sender proxy contract.
Note: If you have an access restriction in your smart contract function and want to whitelist your personal Gelato smart contract wallet as a msg.sender, you don't need to do anything.
We automatically deploy your own dedicated msg.sender for you at the first task creation - the address to whitelist will be shown in the UI and can also be retrieved via the Automate SDK.
Contract | Address |
---|---|
Contract | Address |
---|---|
Contract | Address |
---|---|
Automate
0x2A6C106ae13B558BB9E2Ec64Bd2f1f7BEFF3A5E0
1Balance
0x7506C12a824d73D9b08564d5Afc22c949434755e
Automate
0xF27e0dfD58B423b1e1B90a554001d0561917602F
Automate
0xafd37d0558255aA687167560cd3AaeEa75c2841E