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
Tried to take Sell Offer to buy XMR. It failed with timeout at 75%.
Result was that I had Reserved XMR and absolutely zero Open Trades.
Impossible to resolve in haveno-reto without using external XMR wallet application.
Full story:
haveno V0.1.17 in the haveno-reto/RetoSwap network.
This is a Bug Report that I'm not able to reproduce, especially since it's in a live environment, using real offers and real trades for real value. I still think developers should be aware of it. It's happened to me once, so it will happen again, to me and/or to other users.
A Maker made a Sell Offer to an unexpectedly attractive price, selling XMR against EUR, Payment Method was Revolut.
I took the Offer, the application showed me an increasing percentage of the Take Offer Progress, climbing from 0% to 75%, where the progress stopped. After 180 seconds, the Take Offer process timed out, with an error message telling me that the transaction had failed.
Due to the attractive nature of the Maker's Sell Offer, I tried again. Same progress up till 75%, timeout at 180 seconds, failed transaction.
I tried a third time. Same error.
Now I noticed that the application had Reserved a significant amount of my XMR.
I checked at Portfolio => Open Trades.
-- No Open Trades, empty list. (This was as expected, since I had no other opened trades at the moment.)
I also checked the tab Portfolio => My Open Offers.
-- No Open Offers, empty list. (This too was as expected. I had no open offers at the moment.)
I found no way to 'unreserve' the XMR that had been reserved.
I had no open trades and no open offers.
My only resolution was to use a different XMR wallet application with the same XMR 'wallet seed' to send all my XMR funds from my haveno-reto wallet to an external wallet (to a different wallet seed). This went fine and all funds were 'recovered' from haveno-reto. And of course, the Reserved XMR amount in haveno-reto went down to zero, as expected.
I could then re-fund haveno-reto/RetoSwap from my external XMR wallet and everything went back to the expected state in haveno-reto. (Except, of course, that I had twice payed the mining fee for two XMR transfers that I used to un-reserve my XMR funds in haveno-reto.)
When status was re-established to a controlled order, the Sell Offer was gone.
Either bought by someone else or simply removed by the Maker.
This makes me think it was related to some kind of concurrency error, race condition or such.
Expected behavior:
When haveno-reto failed to process my Buy transaction of the Sell Offer, timing out at 180 seconds and giving me the error message, it should have re-released my funds that were reserved for the transaction that failed.
This should work flawlessly even if the Taker tries multiple times.
The text was updated successfully, but these errors were encountered:
StafrGotar
changed the title
V0.1.17, Failed 'Take Sell Offer' resulted in 'Reserved XMR' with no 'Open Trades'
V0.1.17, Failed 'Take Sell Offer' resulted in 'Reserved XMR' with no 'Open Trades' (is:bug)
Jan 8, 2025
This failed offer with reserved amount can be reinstated in PortfolioHistory.
Left-click on Trade-ID and 'Create new offer like this', reserved amount is taken over.
EDIT:
I'm just realizing now that you were a taker. My solution only helps if you were a maker.
<TL; DR;>
Tried to take Sell Offer to buy XMR. It failed with timeout at 75%.
Result was that I had Reserved XMR and absolutely zero Open Trades.
Impossible to resolve in haveno-reto without using external XMR wallet application.
Full story:
haveno V0.1.17 in the haveno-reto/RetoSwap network.
This is a Bug Report that I'm not able to reproduce, especially since it's in a live environment, using real offers and real trades for real value. I still think developers should be aware of it. It's happened to me once, so it will happen again, to me and/or to other users.
A Maker made a Sell Offer to an unexpectedly attractive price, selling XMR against EUR, Payment Method was Revolut.
I took the Offer, the application showed me an increasing percentage of the Take Offer Progress, climbing from 0% to 75%, where the progress stopped. After 180 seconds, the Take Offer process timed out, with an error message telling me that the transaction had failed.
Due to the attractive nature of the Maker's Sell Offer, I tried again. Same progress up till 75%, timeout at 180 seconds, failed transaction.
I tried a third time. Same error.
Now I noticed that the application had Reserved a significant amount of my XMR.
I checked at Portfolio => Open Trades.
-- No Open Trades, empty list. (This was as expected, since I had no other opened trades at the moment.)
I also checked the tab Portfolio => My Open Offers.
-- No Open Offers, empty list. (This too was as expected. I had no open offers at the moment.)
I found no way to 'unreserve' the XMR that had been reserved.
I had no open trades and no open offers.
My only resolution was to use a different XMR wallet application with the same XMR 'wallet seed' to send all my XMR funds from my haveno-reto wallet to an external wallet (to a different wallet seed). This went fine and all funds were 'recovered' from haveno-reto. And of course, the Reserved XMR amount in haveno-reto went down to zero, as expected.
I could then re-fund haveno-reto/RetoSwap from my external XMR wallet and everything went back to the expected state in haveno-reto. (Except, of course, that I had twice payed the mining fee for two XMR transfers that I used to un-reserve my XMR funds in haveno-reto.)
Either bought by someone else or simply removed by the Maker.
This makes me think it was related to some kind of concurrency error, race condition or such.
Expected behavior:
When haveno-reto failed to process my Buy transaction of the Sell Offer, timing out at 180 seconds and giving me the error message, it should have re-released my funds that were reserved for the transaction that failed.
This should work flawlessly even if the Taker tries multiple times.
The text was updated successfully, but these errors were encountered: