The attacker (see
here) is back:
link to example spammy blockHe's spamming Just-Dice with tens of thousands of tiny outputs presumably in an attempt to disrupt staking.
If you're staking CLAMs please check whether he's attacking your wallets too. You can set "mininput=0.01" in your clam.conf to tell it to ignore UTXOs worth less than 0.01 CLAMs and that pretty much defeats the attack.
Im not sure, but i think it's affecting everyone. Here is my debug.log:
SetBestChain: new best=6bb9fa2bb3c51f7526d153307d68e9acce3e00e1033e53e73f707310$
ProcessBlock: ACCEPTED
receive version message: version 60014, blocks=931607, us=51.158.75.80:31174, t$
stake took 10s
10 seconds to validate a block, as there is a lot of blocks that take only 1 second or less.
Looks like every block minted by just-dice is affected, as every time i receive them, they take more than 10 seconds to validate even in the ones that do not have dust output. Blocks that dont have your addresses, stake as quick as one second or less. Right now, i had put mininput=0.001 in the config file to see if this attack ceases, and hope this does not fork the network as someone can mint a block with outputs smaller than this and my node will reject it.
I saw blocks taking several seconds to validate months before and thought this was because some other software taking resources in my machine other than clam client. Also, the elevation in the difficulty from 90000-100000 to almost 200000 at some times started at the same time i saw these blocks that take a lot of time to validate. Maybe this attack is much more older than we think