As I expected, the HF 21 went a bit rogue, and there was a need for a new hardfork, 22, to make things stable again. At the moment of writing, the blockchain seems to be stable for about 12 hours already, which means there are little to no chances to see another chain halt in this setup. My witness started to produce blocks again on HF 22 and it is now stable. My backup node is still replaying and I'm expecting it to be fully functional in about 8-10 hours.
Although I kept my backup node on a previous version of the blockchain, ready to flip it in case of emergency, this strategy didn't seem to work out this time. The chain halt made this potential flip both impossible and not useful. From which we see that no HF is the same. Never.
During the process, my node seem to have missed a few blocks, somewhere between the chain halt and the new HF 22. I wish I could have prevented that, but I couldn't, this time. Will try to make sure next time I'll have a list of nodes with a high availability and unregister my node if there will be another hiccup. At least it will not "miss" blocks, although I don't know the impact of those missed blocks in the highly unstable situation between HF21 and HF22.
Personally, for me this hardfork meant a lot less drama and a lot more technical breakthrough. I am now more confident that my hardware setup is fit for this specific job and that the process of upgrading, patching and managing the stack is more solid.
I will continue to support the Steem blockchain to the best of my abilities and resources and I want to thank again to those who are supporting and voting me.
I'm a serial entrepreneur, blogger and ultrarunner. You can find me mainly on my blog at Dragos Roua where I write about productivity, business, relationships and running. Here on Steemit you may stay updated by following me @dragosroua.
Wanna know when you're getting paid?
|I know the feeling. That's why I created steem.supply, an easy to use and accurate tool for calculating your Steemit rewards|