On mainnet, 3.5 seconds for confirmation 
 

Thanks raze182 for designing the image, it turned out perfect!

Yep, it also means Masternode payments will be fair again as of tomorrow.

There's also the fact that DarkWallet presently offers absolutely ZERO anonymity and they plan to implement coinshuffle, which is also not anonymous.  I've done a fair amount of research on what they can do and I believe coinjoin based implementations will always be broken on Bitcoin-based blockchains due to the fee structure. They just can't implement an appropriate solution due to the fact that each transaction would be huge and therefore super expensive.

https://darkcointalk.org/threads/security-advisory-for-coinshuffle-and-darkwallet.3736/

Enforcement is currently off, although I have the solution working on testnet. I'll start having the network
update in the morning, then everything will work again.

Actually it's a bit better, because I was just including 1 parties outputs. Let's say there's 15 outputs per party and 3 parties, thats 45 outputs. So 16 rounds would be as secure as 16*45 (each inputs has a separate relay). 720 rounds! At that point even 2-3 rounds is more than enough.

Masternodes currently know where your money went, they see your inputs and outputs, which is why the anonymization process uses more than 1. Unless the masternodes are colluding and recording everything, it's quite anonymous as it stands. The next stage is where you pick 20 masternodes from the list of 2000, then you split up your transaction and send 1/20 through each one and they relay it to the one talking to the three parties. This means for an 60 input transaction, there's 61 nodes involved. Way more secure.

Try DS too, I just did 3 rounds in 10 minutes. The DSTX messaging system is working really well   The next release I might just go ahead and blind the whole masternode system. The security at that point will be insane, each round theoretically is as secure as how many inputs you used. So 3 rounds will on average be the same is 30-60 rounds.

You're saying someone has $250,000 a day to throw at DRK of fake volume?  

There was a small network issue last night that I'm looking into, enforcement is off while I figure out what happened. That's actually the exact block that caused it too.

Make sure your masternodes are running on the latest version, anything below 70054 won't get paid. This happens about a week after an update to allow some time for operators to update, but it looks like about 20% of the network hasn't updated.

I see a bull flag, I used to trade these all of the time  



Good overview here: https://thestockbandit.com/bull-flag/

"FinCEN understands that Bitcoin mining imposes no obligations on a Bitcoin user to send mined Bitcoin to any other person or place for the benefit of another. Instead, the user is free to use the mined virtual currency or its equivalent for the user’s own purposes, such as to purchase real or virtual goods and services for the user’s own use. To the extent that a user mines Bitcoin and uses the Bitcoin solely for the user’s own purposes and not for the benefit of another, the user is not an MSB under FinCEN’s regulations,"

Sounds very clear to me, Masternodes are not MSBs. (I'm not a lawyer, take it for what it's worth)

Block reward just decreased by 7.1% 

http://explorer.darkcoin.io/block/000000000006a3f420f45362543704bb7405198fd7e72dec8c8e7b379701df0d

I'm going to contact the author of this and see if I can explain the strategy of Darksend. Maybe I can get him to understand the insane amount of security that provides.

In any case the way, the CoinShuffle methodology of blinding masternodes IS compatible with DarkSend. This would effectively remove the need for "rounds", even though users could still use them if they wanted. This also doesn't generate any issues from the security advisory, but for them to effectively fix their security they must adopt denominations, which isn't going to happen. As for DarkWallet, Amir is convinced using powers of 2 denominations is safe, which are as insecure as using the unique amounts (I'll write the deanonymizer as soon as they implement it). The future for Bitcoin mixing doesn't look bright, I don't believe there is a comprehensive solution.

In coinshuffle, each output is sent to the next peer in a circle, one at a time. The new peer adds an output, shuffles and then sends the list again. We can do this and actually improve upon it.

To implement blinding, each user would connect to one completely random masternode and say "Send masternode X this output/value for mix N" and pass a single output. That output would be passed to the leading masternode. It would take access to all masternodes used to know who did what, which is as solid as M rounds mathematically (M = number of outputs). This is great because all users can submit all inputs at once. So it's super fast compared to Coinshuffle and even more secure.