Building on top of Enso API, we’d like for our end users to have more granular control over the route generated via the shortcuts endpoint.
For instance, they may want to swap a fixed amount of USDC into WETH, supply however much WETH is output from that swap as collateral on Aave, and then borrow a fixed amount of DAI from the position.
In this example, there are two parameters that we'd like to configure on the REST endpoint:
- The whitelisted protocol(s) through which a supply/borrow action is conducted (e.g. borrowing DAI from Aave)
- The option to specify which amounts are fixed and which are dynamic (e.g. DAI borrowed is fixed, but WETH supplied is dynamic and dependent on previous transaction)
Building on top of Enso API, we’d like for our end users to have more granular control over the route generated via the shortcuts endpoint.
For instance, they may want to swap a fixed amount of USDC into WETH, supply however much WETH is output from that swap as collateral on Aave, and then borrow a fixed amount of DAI from the position.
In this example, there are two parameters that we'd like to configure on the REST endpoint: