Quote from: dooglus on December 24, 2018, 02:21:16 PM

Quote from: criptocambio on December 24, 2018, 11:42:56 AM

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

Note that the "stake took 10s" is telling you how long your client took to check through your unspent outputs to see whether you had any which were ready to stake. You should be seeing those "stake took Xs" about every 16 seconds, not once per block.

Note also that you should put "logtimestamps=1" in your clam.conf so that every line of your debug,log gets timestamped.

The "mininput" thing won't fork the network. You're not rejecting any transactions, you're just ignoring some of them. They still go into your UTXO database but your wallet doesn't recognize them as belonging to you and so it won't waste time trying to stake them.

The difficulty goes up and down wildly every day due to how it is calculated. I don't think that's anything to worry too much about. How are your "stake took ..." times looking now? Are they back to where they used to be again?

Quote

How are your "stake took ..." times looking now? Are they back to where they used to be again?

I still get 5-10 seconds to validate after a block arrives, but then it gets to 0 again. Probably not related to the dust outputs tough, as i already got mininput in the clam.conf