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
Can someone explain me this? Why is the status active if the offer is expired?
Offer is still ACTIVE but expired means that your offer amount (0.1000KSM) is still fronzen on chain.
You need to withdraw it in order to recover the amount. (#3790 (comment))
Is that intention or a bug?
it is indeed intentional (we have many issues related with this like #3401)
When the offer expires, the status should change to something else.
Well since offer is still "ACTIVE" what should be the status then?
Offer is still ACTIVE but expired means that your offer amount (0.1000KSM) is still fronzen on chain. You need to withdraw it in order to recover the amount. (#3790 (comment))
Okay, I understand now. I did not know I needed to cancel my offer even after it had expired. I think we should add this information somewhere for people like me. 😄 Maybe just small text under the table saying that: if your offer is expired, cancel it to release your locked KSM.
I checked active offers in stats and there are a lot of them that are expired and still active:
Well since the offer is still "ACTIVE" what should be the status then?
In this case, keep it - now I understand the point of it 😅
Isn't it possible to make it automatic? Releasing KSM after expiration?
Maybe just small text under the table saying that: if your offer is expired, cancel it to release your locked KSM.
🆙 this!
Isn't it possible to make it automatic? Releasing KSM after expiration?
Nope I don't think it's possible since only NftOwner or the person sending the offer CAN withdraw the offer.
(ref kodadot/snek#13 to handle expired offers)
Can someone explain me this? Why is the status active if the offer is expired?
Go to your profile - offers made:
Is that intention or a bug? When the offer expires, the status should change to something else.
The text was updated successfully, but these errors were encountered: