[bisq-network/bisq] Monero auto-confirm fails with AMOUNT_NOT_MATCHING or NO_MATCH_FOUND in certain cases (#4557)

[James Cox]

Well, after doing some testing I think this problem is even more convoluted.  Bisq already does truncate the amount expected to 8 decimal places, thanks to the Monetary class.  My theory above was wrong.

The only other issue I can find is that there were different maker and taker prices at the time of the trade (confirmed by the logs).  It is possible (though not yet confirmed) that the maker used 0.00848493 (X) price while the taker used 0.00848404 (Y).  So the taker sending the XMR was told to send BTC/Y XMR while the maker was expecting BTC/X XMR.  The resultant difference in amount would then be at the third decimal place.  I need to try this out in a test.

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/bisq-network/bisq/issues/4557#issuecomment-698399973
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.bisq.network/pipermail/bisq-github/attachments/20200924/a676c987/attachment.html>