You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, we are tolerant at max on the price impact swap transactions might incur. On Osmosis we accept whatever impact, whereas on Astroport the DEX limits that to 50%.
The recent market fluctuations called for a more conservative solution. It would only process swap transactions above a pre-configured minimum price impact. The immature DEX APIs make error recognition tough, if not impossible. Therefore our solution should be generic and applicable to other error types on swapping.
Our initial analysis has concluded with a solution that asks for a more restrictive maximum impact calculated based on the last price obtained from the oracle. We have listed the following options, though:
A swap failure waits for manual healing.
A swap failure immediately triggers another transaction attempt by fetching a fresh spot price from the oracle.
A swap failure sets a time alarm for a pre-configured time that would do what option 2. would have done immediately.
2'. 2 + execute the swap operation without max-impact if the transactions have fallen for a given pre-configured timeout.
3'. 3 + execute the swap operation without max-impact if the transactions have fallen for a given pre-configured timeout.
An open question:
should we apply the same swapping policy for all swapping instances, for example, buy the asset on opening, buy LPN at payment, sell an asset on partial closure, or only upon liquidation?
The text was updated successfully, but these errors were encountered:
Currently, we are tolerant at max on the price impact swap transactions might incur. On Osmosis we accept whatever impact, whereas on Astroport the DEX limits that to 50%.
The recent market fluctuations called for a more conservative solution. It would only process swap transactions above a pre-configured minimum price impact. The immature DEX APIs make error recognition tough, if not impossible. Therefore our solution should be generic and applicable to other error types on swapping.
Our initial analysis has concluded with a solution that asks for a more restrictive maximum impact calculated based on the last price obtained from the oracle. We have listed the following options, though:
2'. 2 + execute the swap operation without max-impact if the transactions have fallen for a given pre-configured timeout.
3'. 3 + execute the swap operation without max-impact if the transactions have fallen for a given pre-configured timeout.
An open question:
The text was updated successfully, but these errors were encountered: