# Properly removing BTC from Bisq Wallet **URL:** \ **Category:** Support\ **Created:** [January 21, 2023, 4:38am UTC](https://bisq.community/t/properly-removing-btc-from-bisq-wallet/11882 "2023-01-21T04:38:56Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![noremote](https://bisq.community/letter_avatar/noremote/32/5_5575768a8748004e209b776fc1b2916d.png) [@noremote](https://bisq.community/u/noremote)\ **Post date:** [January 25, 2023, 7:06am UTC](https://bisq.community/t/properly-removing-btc-from-bisq-wallet/11882/7 "2023-01-25T07:06:06Z")
> [@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?](https://bisq.community/t/new-signing-key/11853/14): > > 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?](https://bisq.community/t/bad-instructions-or-major-compromise/11893/1): > > If you go to the page explaining how to Run Bisq on Qubes ([http://s3p666he6q6djb6u3ekjdkmoyd77w63zq6gqf6sde54yg6bdfqukz2qd.onion/index.php/Running\_Bisq\_on\_Qubes#Create\_qube](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. --- _[View the full topic](https://bisq.community/t/properly-removing-btc-from-bisq-wallet/11882)._