Comment on page
Understanding Web3 Functions
Sometimes, automation tasks require data that isn't readily available on the blockchain, or they might need computations that are better performed off-chain. In such cases, Typescript Functions should be the choice.
If all the conditions necessary for your automation task can be directly verified on the blockchain, you have the option to select between Typescript Functions, Solidity Functions & Automated Transactions
Main features of Web3 Functions include Typescript Functions, Solidity Functions & Automated Transactions
Before jumping into the core features of the Web3 Functions, it is highly recommended that you first learn how you'd like to trigger your run. To learn more:
Learn more about each of the 3 actions that your trigger can run:
Smart contract functions in the target contract that can be automated should follow these properties:
- They need to be functions that are usually called by the development team or external keepers, not "user facing" functions called by users directly
- They need to be either
- They do not have access restrictions like an
onlyOwnermodifier, unless the user's dedicated
msg.senderaddress is whitelisted through the proxy module.
- They do not require