Yep, almost done. It's got a lot harder to double spend over the last few hours as the mempools become more homogeneous. My score is a big fat 0BTC -- which was the plan all along.
We did manage to pump the daily txs to an all time record: https://blockchain.info/charts/n-transactions
Over at r/bitcoin they are trying to figure out what it going on.
Interestingly, coinwallet only released a fraction of their keys (mostly from the early Sept spam attack). They have not released the most keys from the late July/early Aug spam attack. The latter looks to be about 5-6x bigger.
We did manage to pump the daily txs to an all time record: https://blockchain.info/charts/n-transactions
Over at r/bitcoin they are trying to figure out what it going on.
Interestingly, coinwallet only released a fraction of their keys (mostly from the early Sept spam attack). They have not released the most keys from the late July/early Aug spam attack. The latter looks to be about 5-6x bigger.
According to my script you were successful in cleaning the last dust. 0 UTXO left (my script only considers confirmed transactions).
Why did you do it in so many transactions? It would save a few bytes to use larger transactions and give a better fee per byte ratio. I guess the reason is that large transactions are more likely to conflict with something in the mempool and are therefore much harder to push to the miners, correct?
Total received: 28.15759741 BTC on 791 addresses (unless I have a bug in my quick 'n dirty counting script). Does this mean that the keys for the remaining 172 BTC will be published later?
PS: Another effect of these transaction is that my R-value cracker runs much much slower now. Almost 2.5 Million duplicated R-values
