You are viewing a single comment's thread from:

RE: The Coindesk article...a message to @ned.

AMEN!


I was informed that the main problem between the 2 versions was the 12 hour voting lockout (in place since HF17) was conflicting with the 12 SECOND lockout of HF20. Testnet did not find this conflict I guess, and even the Steem Blockchain "tolerated" it for a while, even as low as our witness was in the standings, we successfully did 2 blocks, running 0.20.0 before the system had enough!The latest HF20 induced "outage" was relatively minor, if said witness was Prepared. Part of our relative ease of getting back in was likely from our lofty "TOP 100(+)" status, but @sapphic was "Loaded for Bear" and had very minimal downtime. She had us up and running ASAP when the Top 20 decided to run 19.12 to get the chain back up, and was right with them when they set 20.2 to work. Much of our problems here on Steem were due to a large number of witnesses doing their own thing?

So like your letter says, it all falls back on Ned and Team, primarily. But we as Witnesses should be fully prepped for anything. @SAPPHIC -Witness was up and running faster and sooner than most of the Top20. Partly because of lesser equipment to reset, admittedly :D

#learntoacceptcriticism is a great tag, and Steem Inc. should be open to feedback from the Witness Brigade, but the other side of that coin is we as witnesses should be up to the task of not only producing blocks and all that entails, but capable of helping guide and mold our future-finished product.

Don't ever change, Bernie. I admire the "cut to the chase" NO BS style, even if it is sometimes a slap in the face to get our attention.
MARINE SALUTES2.png