DeFi Saver
Search…
Flash loans
In a DFS Recipe, flash loan actions must be the first action in the recipe. If a FL action is put anywhere else it will fail. The flash loan is returned after all other actions are finished, and it expects to have funds return to the FL action that took the loan.
Flash loan actions are a special kind of action in the DeFi Saver Recipe system. These are the only actions that do not run in a context of the user's DSProxy, but rather the action itself is the caller and the receiver of the flash loan. When calling a flash loan action, an additional empty callData is needed, as that is used to pass on the data of the other actions in the recipe.
There are numerous FL actions implemented from various DeFi protocols, which is why we could not use a standard like ERC3156 (for example, we support multiple FLs in one transaction using the Aave V2 protocol). There are some security precautions that are taken over from the standard, which are that the receiver function that is called when getting the FL checks if the msg.sender is the protocol address and checks if the initiator of the FL is the action itself.
While other actions can be called directly (not through TaskExecutor), flash loan actions can only be called through TaskExecutor as it makes no sense to only call a flash loan action.
You may also notice that in every flash loan action there are 2 extra callData parameters flParamGetterAddr and flParamGetterData. Both are used for on-chain getting of flash loan parameters. Because the flash loan action is always the first action, we can't pipe any previous action data into these actions, so we can call the flParamGetterAddr supplied by the user and on-chain fetch flash loan amounts and other info. This is needed where we for instance want to get the exact Maker Vault debt which changes from block to block, so that information must be fetched in that transaction.
Last modified 8mo ago
Copy link