New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed trade #5751
Comments
Thanks for opening your first issue here! |
Hi @rumil2. As Bisq is a P2P trading system, the two parties need to agree on the parameters of the trade. In this case they could not come to an agreement on the current BTC market price. The maker said 58861; the taker said 58176. Since they were more than 1% different the maker aborted the trade, and the taker timed out. Price differences can happen due to each peer checking individually. Such is the difficult reality of distributed P2P trading. It can be messy. No funds left your wallet, and it should be ok to try again. I noted down this problem in our todo list of issues to try and improve. |
Thank you for the reply. |
Hi @rumil2 it is rare for this to happen. I think your got a little unlucky on your first trade. Hope your second trade goes more successful. The P2P nature of Bisq does cause some challenges but the trade offs are worth it for the decentralized platform users can access. Feel free to reach out on Keybase if you have any future support needs. |
I would label this thread better, but I am pretty ignorant about guidelines. Please let me know if I need to add anything else. Thank you!
Description
Went to buy BTC, timed out after 60 seconds and gave me an error message.
Version
1.7.4
Steps to reproduce
n/a
Expected behaviour
I wanted to buy bitcoin.
Actual behaviour
timed out, bisq failed, no bitcoin happened.
Error message:
Screenshots
Device or machine
desktop, Windows 10
Additional info
bisq.log
The text was updated successfully, but these errors were encountered: