Quote from: noob777 on July 29, 2011, 08:35:28 PM

What kind of volume are you seeing through your bitlaundry app?

It varies quite a bit. I'm not going to put out exact status, but I can say that on some days I'll see nothing come in while on others I might see 500BTC.

Quote from: Trader Steve on July 29, 2011, 09:22:46 PM

Mike, can you give us an example of where the "single hop" would be more advantageous than the other?

Bitlaundry.com (the single-hope service) will basically wait for 10 confirmations on the input send, and then transmit the remainder immediately after taking the fee. That's probably as close to "instant" as I'll make it. The equivalent deposit to app.bitlaundry.com would involve a delay of 10 confirmations plus up to a day.

Single-hop services could conceivably be chained together to move coins around rapidly.

Quote from: lettucebee on July 29, 2011, 10:02:20 PM

Mike,
I just listened to your interview on AgoristRadio, which was fun. A question for you: something that would be useful--nay, essential--in a laundering service is the assurance that one will receive new coins and not receive back any of the same coins of the original lot.

Not any not one! Agreed?

Is there any way a user of your system could be assured of this?

No, not at present, and that's something I couldn't do without hacking the wallet management code itself, or by taking an "outside-the-system" approach like the Bitcoin mixer running on TOR. If the mods proposed at http://coderrr.wordpress.com/2011/06/30/patching-the-bitcoin-client-to-make-it-more-anonymous/ get included into Bitcoin, though, it should become possible, though still subject to the limitation that someone sending in more coins than the service's pool holds will inevitably get some of their own in return.