<p>Either of these solutions would work. </p>

<p>If you mix it first to a previously unused address or send it directly to the merchant via the service (ignoring the issue of timeouts on a merchant terminal if they have such a feature) the effect is the same.</p>

<p>The only thing to make sure is any change does not go back into an address which has not been via a coin sharing service. This will cause a link-back to your previous transactions.</p>

<p>The easiest way to avoid this is to have two separate wallets, one which is only been mixed and one which has not.</p>

CC BY-SA 3.0
2014-03-30T13:27:19.283Z
Thanks, could you elaborate your answer a bit? The part which talks about using two different wallets to accomplish this. So, I transfer the amount of BTC I want to mix from the original unmixed wallet to a fresh new wallet. Then, from the fresh wallet, I generate a new receiving address. Transfer the BTC from the fresh wallet to the mixing service and specify the withdraw address as the receiving address I generated using the new wallet. Is that correct?
Neon Flash
CC BY-SA 3.0
2014-03-30T13:32:39.800Z
By two different wallets, I mean for example multibit, 2 seperate wallet files. Generate 100 addresses or the likes in each. One use for regular transactions and use another one for only coins which have been via a coin share. This way any time coins are sent to a change address you know they have all been mixed already and not linking to any service you sent coins directly to. You can switch between wallets seamlessly with multibit.
MaxSan
CC BY-SA 3.0
2014-03-30T13:45:17.453Z
Thanks but I wanted a method without going for Multibit :) If the mixing service returns the coins to a newly generated address from a new wallet, wouldn't that be anonymous enough as well? I could then use this address for further transactions. So, the original wallet is used only to transfer BTC to the new wallet which then pops them into the mixing service and gets its output. This thing is complicated :D
Neon Flash
CC BY-SA 3.0
2014-03-30T13:56:05.417Z
That is fine. I was assuming you were going to be doing this more than once. I think what your explaining is basically the same thing as what I m suggesting lol.
MaxSan
CC BY-SA 3.0
2014-03-30T13:19:54.373Z
2014-03-30T13:19:54.373Z
MaxSan
<p>Step #1: Create a wallet on the clearnet. (We will refer to this as wallet #1)</p>

<p>Step #2: Buy Bitcoins, and send the amount you want to mix to wallet #1.</p>

<p>Step #3: Create a second wallet, this time over the Tor network. (wallet #2)</p>

<p>Step #4: Send your bitcoins from wallet #1 directly to wallet #2.</p>

<p>The reason for this is to add plausible dependability between your clearnet wallet and in-person purchases. If you are ever investigated by law enforcement or the company from which you are buying coins (this happens with Coinbase.com especially), you can reasonably claim that you sent them to someone else who controls wallet #2 (for whatever made-up reason you have in mind as your excuse for your BTC purchase). After that you have no idea/don’t care what that person did with them, nor should anyone expect you to.</p>

<p>Step #5: Create a third wallet, also over the Tor network. (wallet #3).</p>

<p>Step #6: Use Helix Grams mixer (onion link: grams7yngnpr5rzf.onion) and set up your transaction there using the address(s) from wallet #3. It is best to use multiple addresses, and to set random time delays.</p>

CC BY-SA 3.0
2016-05-17T14:32:30.947Z
I recommend using steps 5 and 6, rather than step 4.  It's better to simply be unknown to snooping organizations than to have plausible deniability.
Jestin
CC BY-SA 3.0
2016-04-15T19:37:49.243Z
2016-04-15T19:37:49.243Z
John
<p>I want to use a mixing service and I was wondering what is the right way of using it.</p>

<p>I have some funds in my wallet (associated with a Bitcoin Address).</p>

<p>Should I generate a new address in my bitcoin client (this address would be picked up from my keypool itself right now). And after generating the address, I provide this address as the receiving address (for withdraw) to the mixing service?</p>

<p>Second case. Let's say I want to purchase something online using my bitcoins, like dedicated hosting service or something similar. The merchant wants me to send them the Bitcoins to their bitcoin address, but if I go through the mixing service for this purpose, it would take a very long time and transactions with merchants have to be completed fast.</p>

<p>In cases of mixing services like bitcoinfog, the minimum time interval is 6 hours after which the withdraw process starts.</p>

<p>So, what is the right way of using the mixing service?</p>

<mixing>
Proper way of using a Mixing Service
Neon Flash
# Proper way of using a Mixing Service

(Asked by: username_0 on 2014-03-30)

I want to use a mixing service and I was wondering what is the right way of using it.

I have some funds in my wallet (associated with a Bitcoin Address).

Should I generate a new address in my bitcoin client (this address would be picked up from my keypool itself right now). And after generating the address, I provide this address as the receiving address (for withdraw) to the mixing service?

Second case. Let's say I want to purchase something online using my bitcoins, like dedicated hosting service or something similar. The merchant wants me to send them the Bitcoins to their bitcoin address, but if I go through the mixing service for this purpose, it would take a very long time and transactions with merchants have to be completed fast.

In cases of mixing services like bitcoinfog, the minimum time interval is 6 hours after which the withdraw process starts.

So, what is the right way of using the mixing service?

**Tags:** mixing


---

## 2 answers

### Answer by username_1 on 2014-03-30. Score: 4

Either of these solutions would work.

If you mix it first to a previously unused address or send it directly to the merchant via the service (ignoring the issue of timeouts on a merchant terminal if they have such a feature) the effect is the same.

The only thing to make sure is any change does not go back into an address which has not been via a coin sharing service. This will cause a link-back to your previous transactions.

The easiest way to avoid this is to have two separate wallets, one which is only been mixed and one which has not.

> **Comments:**
> **username_0**: Thanks, could you elaborate your answer a bit? The part which talks about using two different wallets to accomplish this. So, I transfer the amount of BTC I want to mix from the original unmixed wallet to a fresh new wallet. Then, from the fresh wallet, I generate a new receiving address. Transfer the BTC from the fresh wallet to the mixing service and specify the withdraw address as the receiving address I generated using the new wallet. Is that correct?  
> **username_1**: By two different wallets, I mean for example multibit, 2 seperate wallet files. Generate 100 addresses or the likes in each. One use for regular transactions and use another one for only coins which have been via a coin share. This way any time coins are sent to a change address you know they have all been mixed already and not linking to any service you sent coins directly to. You can switch between wallets seamlessly with multibit.  
> **username_0**: Thanks but I wanted a method without going for Multibit :) If the mixing service returns the coins to a newly generated address from a new wallet, wouldn't that be anonymous enough as well? I could then use this address for further transactions. So, the original wallet is used only to transfer BTC to the new wallet which then pops them into the mixing service and gets its output. This thing is complicated :D  
> **username_1**: That is fine. I was assuming you were going to be doing this more than once. I think what your explaining is basically the same thing as what I m suggesting lol.  

---

### Answer by username_2 on 2016-04-15. Score: 0

Step #1: Create a wallet on the clearnet. (We will refer to this as wallet #1)

Step #2: Buy Bitcoins, and send the amount you want to mix to wallet #1.

Step #3: Create a second wallet, this time over the Tor network. (wallet #2)

Step #4: Send your bitcoins from wallet #1 directly to wallet #2.

The reason for this is to add plausible dependability between your clearnet wallet and in-person purchases. If you are ever investigated by law enforcement or the company from which you are buying coins (this happens with Coinbase.com especially), you can reasonably claim that you sent them to someone else who controls wallet #2 (for whatever made-up reason you have in mind as your excuse for your BTC purchase). After that you have no idea/don’t care what that person did with them, nor should anyone expect you to.

Step #5: Create a third wallet, also over the Tor network. (wallet #3).

Step #6: Use Helix Grams mixer (onion link: grams7yngnpr5rzf.onion) and set up your transaction there using the address(s) from wallet #3. It is best to use multiple addresses, and to set random time delays.

> **Comments:**
> **username_3**: I recommend using steps 5 and 6, rather than step 4.  It's better to simply be unknown to snooping organizations than to have plausible deniability.  

---

