The date for October 6th in the HF24 blockchain code has already passed- did we actually fork? No, and here's why.
Eclipse is a big set of changes- across the chain itself, and impacting almost every service and piece of infrastructure that interacts with it. As per the previous posts about HF24, the blockchain code itself is called HiveD and it is finished, tested, and ready to go. Many witnesses are already running it, the hardfork date has passed... so why haven't we forked?
A reminder of how hardforks work on Hive from the last announcement post:
The Hive blockchain does not fork at a specific block height (after a certain amount of finalized blocks) like some chains. A timestamp is set in the code, and when a super-majority of witness servers are running the upgrade at or after this time, the chain will fork to the new version. In non-tech speak: as long as enough of the top 20 are running HF24 when we hit the coded time on October 6th, the hardfork happens automagically.
The consensus witnesses in the top 20 have indicated they all support the hardfork code, but are purposefully holding off having a super-majority running it for a few more days. This has been to make sure that the interfaces that everyone uses and the Hivemind nodes they need to run are available to support the network.
TL;DR: There were not enough steady Hivemind nodes and not enough real application testing to support activating the fork on the 6th, so the top 20 witnesses plan to wait until October 14th for last fixes and node upgrades. If you are a backup witness already ready to go, then you are fine and there's nothing for you to do!
This has been a pretty humbling learning experience for us as we all try to work towards cooperative decentralization. When checking in the final hours before the hardfork activation date, it became clear to witnesses that many dApps hadn't had a chance to test against Hivemind to make sure that they would be able to continue running smoothly after the fork, a few had already experienced some breakage, and that many RPC node operators would not be able to have a Hivemind node up in time to support everyone's needs after the chain forked.
Previously, API changes have been small, easy to test, and upgrading at the eleventh hour has been easy enough. Sometimes they were launched with one specific site in mind and no concern for breaking everything else. With HF24, enough is changing that almost every site, interface, and project will be impacted. Even should the blockchain itself fork smoothly, if every single service ends up broken then the hardfork is not a success for the users of Hive.
This is a pretty unique set of circumstances (you don't rebuild everything from the foundations up every day, or even really more than once) but that doesn't change the fact there are some major improvements to be made for everyone on the development and node operator end of the ecosystem. While we knew from the inception of Hive that decentralization requires cooperation, having to make the choice to not activate the hardfork on the scheduled date has really hammered that point home. It's a good example of where we as a whole need to fix friction points in communication and how we support developers who are used to different circumstances, but it's also an opportunity to help everyone recognize the importance of personal responsibility. Decentralization thrives with cooperation, and that can always be improved.
To all of the users who have been excited for this major retooling to be done as the next step in Hive's journey, thank you for your passion. It's not easy when things are beyond your control or aren't working the way you expect. You are one of the most engaged and communities there is, and that's part of why getting things right matters.
For witnesses who are already upgraded and waiting for the fork to be activated, you're still good to go! A big thank you for being prepared in time for the activation date and for being a part of the network.
In the intervening time between the hardfork activation date on October 6th up to the time of this post, community members have been reaching out to talk to every known dApp team to check if they've tested, to figure out what needs to change to make their lives easier through the HF process, and to double check that core services will be up following the hardfork. Small things coming up in the course of this new testing are being patched and snapshots are being created so that more Hivemind API nodes can be synced up faster to help handle the increased load that the hardfork will put on different parts of our network infrastructure. And finally, the top 20 have chosen October 14th at 14:00 UTC as the time that the majority will switch over and we'll finally get our Eclipse.
LOL...This about sums it up.
Thanks for the update, greatly appreciated. Bold changes sometimes lead to less than bold results in the field. I can wait :)
I appreciate the update and explanation... with a lot of major back end changes like that, I understand the wisdom in proceeding slowly! And it seems there's a lot of old garbage dating back to the early days of Steem that are being retooled.
=^..^=
Glad to see you're working to do everything you can to make sure we don't have a hard-fork headache like we saw happen so many times on the old chain.
Thank you for this update and for keeping the technical stuff within the grasp of folks like me. 🤭
However, the most salient bits, for me, are this:
Cooperation, personal responsibility and communication are so often missing and hearing that all three of these are playing a role in helping to build this ecosystem is music to my ears. I have no doubt it's very hard work - in more ways than one, so thank you to everyone and best wishes for an uneventful eclipse.
Better safe than sorry! I expect this fork to go quite smoothly — of course one never knows. But mad respect for all the behind-the-scenes work of witnesses and devs as always!
I have a lot more confidence in HIVE forking successfully than the cluster*#&@$ that were Steemit, Inc. led updates. Lol.
and that it is impossible to make hardforks generally paid? Paid 1Hive - moved to a bright future, no - sit quietly in a stable
Thank you for the update.
One week is a small fraction of BUIDLing HIVE Network with 2025 vision
Congratulations @hiveio! You have completed the following achievement on the Hive blockchain and have been rewarded with new badge(s) :
You can view your badges on your board and compare yourself to others in the Ranking
If you no longer want to receive notifications, reply to this comment with the word
STOPIt's nice read some news about it!
Thank you for the update, last I had heard was the 8th was going to be shot for, guess that did not happen, hopefully the Dapps will be able to do some efficient testing over the weekend and we will be standing as our own block chain on a very solid foundation.
After being away from Hive for a few months I didn’t really know what this fork was all about. This makes it al a bit clearer, thanks :)
Thank you for the information and the clarification about the HF 24!
Thanks for the great update. Stability is far more important than an under-delivered hard fork. No need to rush it all, the community is under control
Well alright! Whatever you need to do. I am curious though, does this hardfork change anything for the casual user or is it only going to affect developers experience?
Many users thought that the HF24 was done last October 8th, because that day we had problems to enter Hive, to vote, to comment or to make transactions in our wallet. It was not done, then? Will it be for October 14th?
Great update - holding off until the problems are sorted is confidence inspiring - after watching Steemit totally screw up nearly every hardfork for four years, all I want to see is one go smoothly
i didnt know how Hardforks Work worked thanks for letting me know about hf24
nice
Waiting for eclipse 😎
Shared on Twitter... so far I have been liking the way the fork update/communication is happening. Way better compared with previous ones.
It's always right to delay if not ready. People need to understand that this is sort of normal in continuous development and especially in blockchain technology.
On behalf of the @adiwathrive team I am grateful for this detailed explanation. It's really hard sometimes to keep up and understand will all the innovations and upgrades happening here on the HIVE blockchain space.
Your post is wonderful and that's why it has been manually curated for #adiwathrive by @acurewa
Our project seeks to motivate our community to develop content in different branches of life. It doesn't matter if you speak English or Spanish, our foundation is based on the principles of balance, harmony and consciousness. Click here if you want to know more here
Our account is supported by LOTUS, so we also reward with the lotus token.
DELEGATE to @adiwathrive and receive our support with upvotes, reblogs, mentions and contests where you can win in HIVE and more.
We also recommend you to follow @naturalmedicine and @tribesteemup communities that inspire personal growth.
as @hivio isn't a witness let alone the top 20 witnesses, could we get the top 20 to comment on these types of announcements so we get signatures on chain that witnesses are planning a HF?
or would it be better to have each witness post on their own? It's hard to tell the difference between one or two people saying something and 20 witnesses committing to something