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
Hardfork with a new time drift is the only way to stop timewarp from happening again.
It will stop for a little while when the guy doing it runs out of stakeable coins , and has to wait for them to be ready to stake again.
We fixed this at
ZEIT a while ago, and our block time is 30 seconds and we used a 1 minute time drift, since your block time is 1 minute , you could probably go a little higher to 1½ or even 2 minutes , but you want to test to confirm.
Your Block explorer looks normal now, so the attack should be over until the culprit has more coins ready to stake.
Have your Dev or someone with alot of coins ready to stake change their time ahead 1 or 2 minutes , if it does not drop the difficulty in half, then that amount of time is safe to use for a permanent timedrift . IMO, I would test 2minutes first, because you do want the highest drift possible to avoid Orphan Storms.
