Yeah I think we should learn from this. In hindsight I think it's clear that the last-24h-limit was a bad idea in this case. The intention is good, but should not be combined with a fixed time limit (March 8th in this case) as we are bound to see anomalies in the registrations in the last hours. Maybe it would have been better to relax the condition to allow the 24h period to have been at any earlier point and not necessarily the last 24 hours? Not sure it would make a whole lot of more sense though.I have seen a few update delays over the years with Dash, but this in my opinion would be the hardest delay to sell and also the hardest delay to defend.
A manual spork activation (basicly nothing more then a switch of a button) possibly getting delayed because of too much updating on the last day, while at the same time
having already a majority (63+ %) updated.
Sure i could live with having to wait another month (and pray that the 24H registration condition does not form a factor again), but at the same time it would undermine
my confidence in future Dash update cycles as it will introduce an element of uncertainty with future spork activations.
At this point i just pray for a miracle and hope this spork gets activated tomorrow somehow.
A simple fixed percentage is probably the best anyway. Maybe 80% is a bit much? Or maybe not. Maybe I just need to be a bit more patient
Anyway. Let's hope we get 80% before the next cycle to rule out any potential last minute spikes ruin another month for us! We should be safe