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
When doing a dexter fetch request for Dex of Wingriders, with a fixed swap in amount.
I have noticed when submitting the orders, they are pending to be batched in the Wingriders UI, these orders are not processed because they immeditely appear out of range, as a result it requires manual interaction to manually reclaim these orders in the UI, this is wingriders specific and other dex's work fine.
The minimum receive does in fact have the amount with the default 1% slippage so visually this looks fine.
I am also refreshing the pool state before an order is placed, thinking back I had Wingriders orders processing immediately when loading all the pools again and without the refresh pool state method being used, so this could be a factor here.
The text was updated successfully, but these errors were encountered:
Hey @ndtr2000 I saw you mention Wingriders is working for you, do you ever get out order of range issues on specifically just Wingriders? Mainly on tokens with large supply
Data Provider
Blockfrost
DEX
WingRiders
Description
When doing a dexter fetch request for Dex of Wingriders, with a fixed swap in amount.
I have noticed when submitting the orders, they are pending to be batched in the Wingriders UI, these orders are not processed because they immeditely appear out of range, as a result it requires manual interaction to manually reclaim these orders in the UI, this is wingriders specific and other dex's work fine.
The minimum receive does in fact have the amount with the default 1% slippage so visually this looks fine.
I am also refreshing the pool state before an order is placed, thinking back I had Wingriders orders processing immediately when loading all the pools again and without the refresh pool state method being used, so this could be a factor here.
The text was updated successfully, but these errors were encountered: