-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
ERROR: Deposit transaction ID N/A #6205
Comments
Thanks for opening your first issue here! |
Thanks for writing this up. @w0000000t sent me the logs and it is on my todo list to put a guard against exiting the app while a trade is being started. (I'll reference this issue when submitting the PR). In regards to your immediate situation, as you did not get the mediation proposal, the mediator will have to perform a "manual payout". That involves communicating with both buyer and seller using a Bisq tool for both to sign the proposed payout. Please DM your mediator on Matrix (and if in communication with your peer, DM/trader chat them too) referencing this issue. |
@dgcfusII @jmacxx @w0000000t Is there any way to remove the trade from Portfolio > Open Trades? |
@Drazen-V to remove it, all open trades can be nuked by deleting|renaming a file.
|
Description
while exiting my bisq client a buyer took one of my sell offer, this caused an error in the multisig deposit transaction.
The buyer was able to send me the payment but all my button are grayed out and i cannot release the BTC using my client. Already tried resyncing SPV, restoring a backup and unistalling/reinstalling.
We already went trough mediation, the mediator proposed a solution, but i didn't get it in my client.
Version
1.9.1
Steps to reproduce
Exit bisq when an offer is being accepted.
Expected behaviour
not sure
Actual behaviour
bisq thinks i sent btc out of my wallet instead of sending it to a multisig wallet for the trade.
Screenshots
Device or machine
Additional info
multisig deposit: 59f5f0702d4ddda5239c4c0475abcd0a39a12df51ad7b0af3984fe2cdf74694b
logs may contain sensible data, i can share it on matrix
@dgcfus:matrix.org
The text was updated successfully, but these errors were encountered: