Properly removing BTC from Bisq Wallet

[noremote]

What is the correct procedure to:

• end an offer

• sweep all finds out of Bisq and into another (non-Bisq) wallet?

[MnM]

The offer ends, if there is no mediation, when seller clicks “payment received”, and both traders get their funds to addresses they’re the only owners.
Then, you can go to Funds - Send funds and send the BTC to any BTC address.

[noremote]

Sorry I didn’t communicate what I mean. I mean how do I end the offer myself because I want to stop the offer? And then how do I recover my BTC from the Bisq wallet and put back into another wallet?

[FreddieChopin]

Go to “Portfolio” and “My Open Offers”, press the red trash icon on the right side of any of your offers and then confirm with “Remove Offer” button. You will loose your “maker fee”. After that the reserved amount of BTC will be available for spending in “Funds” - “Send Funds”, where you can transfer that to any address you want.

[noremote]

Thank you! I think I’m going to stop using Bisq until they can fix the data security issues. I’m also going to post on reddit so people are aware that Bisq is either compromised or does not take security seriously at all. It’s literally the worst key handling I have seen in almost ten years, and Bisq handles money and accounts!

[MnM]

The issue is with Bisq using Tor to transmit transactions, not with the wallet. This issue has been around for a long time but no fix has been found yet.

[noremote]

@MnM

The issue is with Bisq using Tor to transmit transactions

I don’t know what issue you think I was talking about but I am talking about the fact that Bisq can not manage GPG keys properly:

New Signing Key?

There is a long-established way of handling exactly this sort of thing, and Bisq isn’t doing it. Why even use signing keys if you’re not going to use them in the proper way? I actually forget the original situation here, but if there are two keys then each of those keys should have signed each other and uploaded the new keys to the keyserver so everyone can verify that each signer knows the other. If there is a new key, all former signing keys need to sign the new key, and upload all to the …

Bad Instructions or Major Compromise?

If you go to the page explaining how to Run Bisq on Qubes (http://s3p666he6q6djb6u3ekjdkmoyd77w63zq6gqf6sde54yg6bdfqukz2qd.onion/index.php/Running_Bisq_on_Qubes#Create_qube) you will see this instruction: # Go to the folder where you downloaded the .deb package and the PGP signature cd Downloads # Import the signing key of Christoph Atteneder curl https://bisq.network/pubkey/29CDFD3B.asc | gpg --import # Verify the signature of the downloaded binary gpg --digest-algo SHA256 --verify Bisq-*.a…

But thank you for pointing out this other, unrelated issue. I don’t see it as a security issue however, so I’m not sure why you thought this is what I was talking about? Or maybe it is a security issue, I only looked at the link briefly.

The security issue is either that Bisq was compromised (the key issues that Bisq is having are generally considered by security profesionals to be a sign of a compromise) or Bisq does not understand basic key management. This has nothing whatsoever to do with Tor. Please do not confuse the issue.

[MnM]

Ah, I thought that you had issues sending funds out of Bisq, I did not associate this thread with the New Signing Key thread.
I’ll point that thread to the devs and maybe they can improve the process, on the meantime I understand you want to be out of Bisq, but me, I’m quite comfortable since I know that this change has not been considered as strange from any contributor.