HardFork 24 Set For Sept 8th?

avatar

There has been no official announcement that I could see. However, looking at Gitlab, it appears that the new date was set.

hf24.png

https://gitlab.syncad.com/hive/hive/-/commit/488e6db2efe4b55ef82a75c0f29b1169d1bd3f20

Over the past few months, @blocktrades was keeping everyone up to date with the progress. It now appears the date is set to go live with the new updates.

Of course, it is vital to remember, when it comes to coding, nothing can be considered "set in stone". This is a tentative date which will occur if everything goes smoothly.

There are still a few details to work out as posted by Blocktrades in the latest article.

The release candidate is going to be up, hopefully, today. It was delayed because a replay had to be done, something that takes about 18 hours, after more bugs were found.

Here is the article explaining the details.

https://peakd.com/hive-139531/@blocktrades/weekly-update-on-hive-hf24

It does appear that Hard Fork 24 is getting very close. We will see the first Hive fork occurring within 6 months of going live.

What does Hard Fork 24 do?

I will not even try to go into the detail of all that is taking place. Anyone trying interested can read through the different post by the Blocktrades account over the last two months which really delves into what is being done.

However, to hit upon some of the highlights, I guess we can call this an efficiency fork. The main focus is to upgrade the back end to improve the efficiency of front end interfaces. As they say, a system is only as good as its weakest link. Having superior front end interfaces operating on a crappy backend results in a flawed system.

It is vital to remember that little was done to the code over the past 4 years. In the technology world, 4 years is a lifetime. There seems to be better software available now that can handle the way data is structured and processed. This should help the operation of the front ends.

I think the one major "feature" change is the altering of Witness Voting when powering up. The original discussion was to have a 30 day delay from when a HIVE is powered up until it affects Witness Voting. This is a security feature in response to Sun's actions on Steem. Having this in place provides a window for the community to respond if there is an outside threat similar to what took place earlier in the year.

Blocktrades also discussed the personal blacklist feature. I am not sure this is really operating at the base layer as much as being a front end decision. However, from what I could garner, the base coding will now make it possible for front ends to establish the ability for individuals to have their own blacklists, follow those they desire, and offer an alternative to global blacklists.

As much as many of us are awaiting a "feature rich" hard fork, sometimes it is best to build from the ground up. Back end efficiency is often overlooked, that is until it becomes a problem. The fact that Steemit Inc followed the bi-polar behavior of its leader meant that some basic upgrades were ignored.

Hive can handle a lot more traffic than it presently has. However, as we see with other blockchains, the time to address the efficiency problem and overall operation of the chain is when there are no problems. Trying to provide solutions when the system is bogged down with transactions is a bad time to be addressing things.

Once this takes place, the focus can turn to Hard Fork 25. Hopeful, fingers crossed, attention will be paid to SMTs (HMTs) and finally bring them to life. This might not be a quick turnaround to another hard fork since there could be a great deal of community discussion that is required. Adding and altering base features is something that necessitates community consensus. For example, there was talk of lowering the power down from 13 to 4 weeks. If that is to be addressed in the next hard fork, discussion is going to have to take place.

As discussed the other day in a post, the development keeps moving forward. Obviously, coding never goes as quickly as any of us would like. However, the advantage to Hive is there are plenty of people focusing upon different areas. Collectively, if we step back, we see a great deal of progress being made.

If you found this article informative, please give an upvote and rehive.

gif by @doze

image.png

If you found this article informative, please give an upvote and rehive.

gif by @doze

image.png

Posted Using LeoFinance

hive hardfork coding blockchain leofinance archon neoxian mancave palnet
0
0
0.000
13 comments
avatar

Your current Rank (35) in the battle Arena of Holybread has granted you an Upvote of 21%

0
0
0.000
Reply
avatar

Thankyou, to talk about this hardfork. It is good that it will improve the efficacy of the HIVE chain.

0
0
0.000
Reply
avatar

pixresteemer_incognito_angel_mini.png
Bang, I did it again... I just rehived your post!
Week 19 of my contest just started...you can now check the winners of the previous week!
11

0
0
0.000
Reply
avatar

pixresteemer_incognito_angel_mini.png
Bang, I did it again... I just rehived your post!
Week 19 of my contest just started...you can now check the winners of the previous week!
!BEER
1

0
0
0.000
Reply
avatar

Well it's actually going to be exciting I feel hive's next fork is a next step in the right direction, I'm thinking the SMTs might still be in the making for about a year interval and then we wouldn't see instant impact slowly things will work out well with hive.

0
0
0.000
Reply
avatar

I simple words the new HF explained; Thanks for that. And I agree, the foundation for scalability shall be set right before trying to expand its features. Worked with software development houses I saw often an application being build up from the ground, two times. The first time was more to show case the services, concentrated on features lacking scalability features and usually with poor performance. Whenever the service was to stay and needed a setup for growth, the architects would go back to the drawing board and designed a solid framework set for speed, scalability, reliability and availability with as much as possible a modular setup of the different process in the software. Only then coding happened. I’ve been working with applications that was designed so well, the software architectuur didn’t need a change in more than 20 years. Hope this will be the case for HIVE chain as well, so we can concentrate on the so needed SMT and more from coming HF onwards.

0
0
0.000
Reply
avatar

Powerdown timing, author/curator split, quadratic/linear posting rewards; all of these can be experiments undertaken by different SMT projects.
SMTs should be our absolute next priority.
It's the reason many of us are here, and if we don't do it soon, somebody else will, and we'll lose, and we'll deserve to.

0
0
0.000
Reply
avatar

@blocktrades update has been very timely and keeps the community informed ! liking the changes which are coming and 8th Sept !! looking forward to it.

0
0
0.000
Reply
avatar

Let's hope for the best in the next level.

0
0
0.000
Reply
avatar

Once this takes place, the focus can turn to Hard Fork 25. Hopeful, fingers crossed, attention will be paid to SMTs (HMTs) and finally bring them to life.

This would be quite an exciting aspect of the next Hardfork. The wait for HMTs is climaxing already.

Posted Using LeoFinance

0
0
0.000
Reply