You are viewing a single comment's thread from:
RE: HF 20 - lessons finally learned?
You can further patch to get back to old behavior, but you can not simply roll back to a prior version without invalidating all transactions since the fork.
You can further patch to get back to old behavior, but you can not simply roll back to a prior version without invalidating all transactions since the fork.
thanks for clarifying, had just done some digging myself and realized this. my apologies, flag removed. I thought you were saying this as more of a philosophical statement. sorry. So related question though - if a HF21 was released that had same code as the last stable HF19 release that wouldn't work?
No because the new transactions that exist on the blockchain over the past 2 days, and probably some of the resulting state, would be considered invalid by HF19 code. There would need to be a new hybrid created, and that's a very significant effort.
I guess with the RC system in particular you don't even have to patch or roll back, Stinc built into HF20 the ability to roll back the RC system and go back to prior bandwidth system. From steemitblog post: ""Due to this uncertainty, we added a 'fail safe' to the code that will enable witnesses to revert from the RC system back to the old bandwidth system if absolutely necessary."
In practice that is easier said than done. It requires not only witnesses but (nearly) all nodes in the whole ecosystem to make this change.
Ah... thanks for that clarification. So even if a supermajority of top witnesses made this change, if Stinc isn't on board and doesn't update api.steemit.com for instance it wouldn't work?
Correct. Transactions go through the front end nodes first. For steemit.com users (and indeed many other app users) that means nodes run by steemit.com. If those nodes don't pass through the transactions, witnesses never receive them and they don't go the blockchain.