You forget 0.05001234BTC which isn't mixed


As @fillippone mentioned, that would reduce your and other's privacy, so the answer is no.

The problem is that by the time you realise that you have been hacked, your funds will have been already stolen. You won't have any time to react. That's why I recommend you to reconsider your setup.

What machine are you referring to? The host? As I wrote earlier, if your host gets hacked then your VMs should be also considered as compromised. Ideally, it would be great if you used a completely separate machine to sign your transactions. Creating raw transactions using Bitcoin Core is a bit complicated so I would recommend you either using Armory + Bitcoin Core or Electrum (wallet backup would be in a form of 12 words which you wouldn't need to update after each transaction unlike your current setup).

Obviously yes, unless you use 3rd party/centralized exchange which perform KYC/AML (who usually also track your coin history) where they might freeze your coin/account.

P.S. if that's not what you mean, please specify which aspect you're asking from wasabi wallet and it's coinjoin feature.

I got that part. What I meant was asking if you are going to spend those coins often. Once you move your wallet from the offline machine to your main one, your wallet will be completely exposed. You can mitigate that by preparing transactions on the online machine, signing them on the offline one and moving the signed transaction to any online PC. This won't expose your private keys. Also, I don't think that using virtual machines is a good idea. If your host is compromised, so are your VMs. Using a separate computer would be safer.

It should be as easy as that. If it doesn't happen to work, open Console in Bitcoin Core (Window -> Console) and type in rescanblockchain after you load your backup and confirm that its balance is wrong.


Yes, you can. Your transaction will be broadcast once you connect your main PC to the Internet and let Bitcoin Core catch up with the blockchain.


Unfortunately, no. Wait for ETFbitcoin's reply.

By the way, how do you intend to spend your coins from the guest machine?

Sure, any software wallet should be able to generate a new wallet without the Internet connection. In fact, some storage setups are meant to be offline all the time.


Wallet.dat contains information about transactions so your balance will be visible while being offline. As for importing your backup, if there are any confirmed transactions associated with that wallet after you made that backup, the balance won't be up-to-date if your online node has already downloaded the blocks in which they were included. You will have to run Bitcoin Core with -rescan parameter. If you copied you wallet file after all transactions have been confirmed then simply importing it should be enough.

I'm afraid i can't understand your question, can you rephrase your question so it's easier to understand?

When you try to send a payment to a node which is not directly connected to you, your payment is routed through other nodes. Those nodes must be connected to each other. Payments usually fail if there is no route available or if the amount of coins you are trying to send exceeds the amount available in the channels which route the payment.

Let's say you are Alice and you want to pay Dave 0.1 BTC via the Lightning Network. You didn't open a channel to Dave but you did to Bob. However, Bob has an open channel with Charlie who has a direct channel with Dave. The path looks like this: Alice -> Bob -> Charlie -> Dave. Your payment will be routed through Bob and Charlie. Depending on their fee policy, they might charge you a small fee (usually under 1 satoshi) for routing. For example, if Charlie had only 0.05 BTC on his side of the channel, he wouldn't be able to route your 0.1 BTC payment so it would fail.

If your payment fails then there is nothing you can do except funding another channel or trying sending less coins.


While the development has slowed down significantly, it doesn't lack any crucial features. The app works fairly well and is user-friendly.


Sorry, but I haven't used Wasabi much. I might try answering it in the morning.

I haven't done throughtful research about privacy of both of them, but here's few pros. and cons. that i know

Wasabi :
+ Easy to use
+ Hardware wallet support
+ Many participant, so you don't need wait too long to before
- Minimum about 0.1BTC required to mix your coin
- It's very obvious your coin going through CoinJoin process due to fixed output size

JoinMarket :
+ Very low minimum bitcoin required to mix your coin (depending on maker though)
- There are less participant (market), so you might need to wait longer.
- Difficult to use (compared with Wasabi)


There's no good/best practice since it's unknown how exchange trace your coin, how far they're willing spend resource to trace your coin and how "sensitive" their system to flag your coin or not.

1. Download Zap and set it up (create a new wallet, write down the seed which can be used for wallet recovery). Wait for Zap to synchronise.
2. Send some coins from your Bitcoin Core wallet to Zap.
3. Click on 'Channels' in the bottom-right corner and select 'Create'. Now you can either use a specific node or use a suggested one. I would recommend you the latter option since it will be your first time using the Lightning Network. Whether or not your payments are going to fail often depend on the node you choose.
4. Once the funding transaction get 3 or 6 confirmations, the channel should appear as active. Now, you should be able to send payments over the Lightning Network by paying the invoices generated by merchants or other users.

Feel free to ask questions if you get stuck at one of these steps. You can also try looking for videos on YouTube. The UI has changed slightly but everything should look similar.

No, you don't have to swap your bitcoins. The Lightning Network doesn't use any form of tokens; it uses real bitcoins. In order to be able to transact using the Lightning Network, you have to open a channel using a wallet which supports the Lightning Network (i.e. Zap, Eclair Mobile). When you open a channel, you lock up your coins in a multi-signature address which is controlled by you and the other node. Once you have opened your channel, you can send payments over the LN (with some limitations). Every time you send a payment over the LN, the balance of the channel updates but it's not broadcast to the Bitcoin network in order to save money on the fees. If you want to retrieve your coins on-chain then you have to close the channel. The amount of coins + routing fees you spent on the LN will go to the other node's address while the rest minus the closing fee will be returned to you.

It's a little bit more complicated than that; consider reading basics of the Lightning Network and The Lightning Network FAQ if you want to learn more. It's not a perfect solution. Keep in mind that some of your payments might fail and not many merchants accept LN payments.

Lightning:
you'll need a lightning wallet for this task.
You send your funds, on-chain to the lightning wallet, then your lightning wallet uses this unspent output to create an on-chain transaction opening a lightning channel with an other node. From this point on, you can pay lightning invoices offchain using this channel. Once no more funds are left on your side of the channel, you can either leave it open or close it using an on-chain transaction. This closing transaction will distribute the funds between you and the node you had an open channel with, how much each partner gets depends on the state the offchain transactions left the channel in.

I've used zap wallet in the past, and on my mobile i use eclair. To be 100% honest, i found eclair more user-friendly than zap.

I'd urge you to use zap or eclair on the TESTnet before trying it out on the mainnet... Eclair defenately has a testnet version, there are testnet lightning nodes, and even a testnet lightning store.

Wasabi & CoinJoin
Wasabi is a wallet that has built-in support for coinjoining. Coinjoining is usually fine privacy and security-wise. Other options are mixing or exchanging your BTC for a privacy-centered coin, and after moving those funds around for a bit back to BTC.
Each of these methods has pro's and con's, but they depend on your point of view... If you really want the highest level of anonimity, you'll probably need more than one method.

To be honest, i've never had my deposit flagged (so far), but i've heared horror stories aswell. Apparently, some companies actually do some data mining and follow the unspent-outputs-trace several transactions deep. So, if you want to be certain your deposit won't get flagged, you might even move it around several times before spending it... I'm not an expert about this tough, somebody else might have something more usefull to say.

Using Bitcoin Core offline:
yes, you can create an address while being offline. An address is a hash of a public key belonging to the private key stored in your wallet. Your address is not "registered" with a central authority. If you create a private key, you can derive a public key, and you can hash this public key to generate an address. This address exists because you created a private key, not because it was broadcasted or registered.
It is possible to create 2 exactly thesame private keys, this is called key collision... The odds of creating a key collising when using a proper RNG are incredibly, incredibly small (allmost nonexistant).
When i say: "allmost nonexistant", i actually mean "allmost nonexistant"... Not like: you have 1% chance of having a key collision in your lifetime... No, those odds are waaaaaay smaller.

I actually did the math a while back: https://bitcointalk.org/index.php?topic=5240403.msg54220088#msg54220088
The actual discussion was about generating a private key whose public key hash was a predetermined address that was funded by somebody else, and this was the end conclusion:

Bitcoin Core would send transactions only when it detects an internet connection and is connected to its peers.

It's normal if you either :
1. Store the blockchain files on HDD
2. The HDD also used to store guest or/and host OS
3. Use shared folder feature, which is known to be slow. Source : https://superuser.com/q/1025864

Have your tried giving less ram to your guest os, so there's more left for your host?