Quote from: HarryPorter on March 05, 2016, 01:48:19 PM

Quote from: kiklo on March 05, 2016, 12:35:04 PM

Quote from: HarryPorter on March 05, 2016, 12:25:03 PM

is anybody staking success last days? I had no any staked coins since 08 January, even if I leave open client by 24h. Got v. 2.2.1.0 of client, over twenty connections, right no. block same as explorer...etc. It was staking before, up to my last staked coins on beginning of this year. Had no problems before, I changed nothing but looks like staking stop for me. Anyone got similar symptoms? Or there is some solution to fix that?

Hmm,

Looking at the block explorer someone is using the timewarp attack on your coin.
1011503   just now   20.4 kB   7,756.286929 AC   1.26    Proof of Stake
1011502   just now   20.4 kB   15,531.449013 AC   1.24    Proof of Stake
1011501   just now   20.4 kB   1,814.045 AC   1.25    Proof of Stake
1011500   just now   30.6 kB   26,656.904027 AC   1.23    Proof of Stake
1011499   just now   20.4 kB   177.443835 AC   1.30    Proof of Stake
1011498   just now   20.4 kB   621.961369 AC   1.37    Proof of Stake
1011497   just now   20.4 kB   9,960.027753 AC   1.33    Proof of Stake

They set the time on their PC toward the upper end of the timedrift and are out staking everyone else.
Dev will need to release a code update changing the time drift from 2 hours down to 1 minute or so.

Cool

FYI:
http://bitcoinist.net/interview-presstab-pos-vulnerabilities/

Thanks for quick answer and clarify that case. So all in dev hands now.

this description from Kiklo does not fit here as difficulty is quite high - 1.77 was last . main point of Kiklo is that difficulty will tank a lot during such an attack

anyway, trying to figure out what to do with time drift parameter

1 minute is reasonable

dev says now - less time drift means more orphans

as to drift attack - it looks as something different here : now no block creation for 34 minutes

edit : 14:55 UTC: limiting time drift would mean : hard fork again?
do we want another hard fork?
for this moments hard fork seems unavoidable if want to decrease time drift

edit:14:59 UTC - now blockchain stopped for 47 minutes already. becoming scary.

edit: 15:01: UTC - which block to use for hard fork ?

edit 15:11 UTC blockchain moves again, no signs of this attack : "just now" and difficulty goes up to 2.03 and going higher.
maybe Kiklo was right about nature of attack

really should be getting more opinions : do we need this one hard fork - with limiting time drift?

please to submit feedback