RE: HF20 Update: Restoring Continuity
It is ultimately up to the witnesses to decide whether the code is safe enough to use, however, one of the reasons we chose this particular path is due to the fact that simply multiplying the resource budgets by 10 is a simple fix, and with this simplicity, the code easy to audit.
It’s interesting that you decide to mention something like this after you already dropped such a massive hard fork on everyone. It is exactly this kind of post hoc pretense of responsibility that irritates a lot of witnesses.
If they choose to adopt this change, user experience could begin improving as soon as tomorrow night.
If they choose...??? Seriously? You drop a buggy fork (with major problems you knew about), ask for adoption, insinst on no rollback to bandwidth, then pretend that these patches are somehow optional while basic user activity is still throttled?
No other community on Earth is trying to do what we are...
And rightfully so. Testing known buggy code on production shouldn’t happen.
We’ll hopefully get this fixed. After that, I think it’s time for STINC to step aside as the lead dev team for this blockchain. At this point, SMTs are a no-go. I’m not even going to entertain that insane proposal from your team, given the many mistakes and complete lack of foresight we’ve all witnessed since last year.