As most are aware, [HiveFest](https://hivefe.st/) is taking place now.  We see many presentations focusing upon development and the future focus of Hive.

Yesterday's activities kicked off with the core development team, represented by @howo and @blocktrades.  This was one of the most important presentations in my view simply because it deals with the [base layer](https://leofinance.io/@leoglossary/leoglossary-base-layer-blockchain).  Since that affects everything on top of it, we can logically see how massive improvements there translate to everything else.  

It is interesting that we got The Merge this week from Ethereum.  This upgrade switched that blockchain from the [Proof-of-Work (Pow)](https://leofinance.io/@leoglossary/leoglossary-proof-of-work-pow) to Proof-of-Stake (PoS) [consensus](https://leofinance.io/@leoglossary/leoglossary-consensus) mechanism.  The primaty goal is to allow more transactions.  We know that PoW has limitations when it comes to [on-chain](https://leofinance.io/@leoglossary/leoglossary-on-chain) transactions.  The switch should allow Ethereum to scale a great deal more.

Once again, we see an area where Hive excels.  This is going unnoticed since the traffic is not present at this time.  However, it is vital to note that we are seeing massive progress in this area.

This is a vital point going forward.

![image.png](https://images.hive.blog/DQmPdX9ttzSrYHMx4oGysBCGTo9uHXxaAPYEYznykoovu3V/image.png)

## Half The Size

According to Howo, the [blockchain](https://leofinance.io/@leoglossary/blockchain) is now somewhere around 700 GBs.  This is starting to become a problem because this requires larger servers to run on.  Naturally, it is a situation that translates into more [money](https://leofinance.io/@leoglossary/leoglossary-money).  In short, it makes the blockchain more expensive to run.

One of the major steps with the next hard [fork](https://leofinance.io/@leoglossary/leoglossary-fork) is to reduce this by 50%.  That means this can be run on smaller [nodes](https://leofinance.io/@leoglossary/leoglossary-node), helping to reduce the financial commitment a great deal.

While a 50% reduction might not seem like a lot, if we apply some numbers to it, we can see how massive a change this is.

For the sake of discussion, let us say the size of the [data](https://leofinance.io/@leoglossary/leoglossary-data) grows by 50 GB per year.  So, without this move, in one year, the total would be 750 GB.  Now, if the drop back is to 350 GB, we effectively have 7 years before we get back to where we are today.

This is a major step forward.

Again, the numbers might not be correct but you get the point.  The key here is to keep buying time.  In the [technology](https://leofinance.io/@leoglossary/leoglossary-technology) world, 5 years can see massive changes.  It is impossible to know what compression, storage, or data structure techniques will be available at that time.  We know the industry keeps addressing this problem since all companies that house data are confronted with the same issue.

This move is also vital for [decentralization](https://leofinance.io/@leoglossary/leoglossary-decentralization).  If nodes cost thousands of dollars per month, very few people will be able to afford that.  By continually working on reducing the size of the chain in terms of the size of the data, we open up the door for more people to run nodes.

## Web 2.0 Speed

Another interesting idea that was put out refers to the [One Block Irreversibility](https://peakd.com/hive-139531/@blocktrades/one-block-irreversibility-for-delegated-proof-of-stake-dpos).  We won't go into a full discussion on it since the link here describes what is taking place.

To give a quick summation, at present, it takes about 45 seconds from a [block](https://leofinance.io/@leoglossary/leoglossary-block) to become irreversible.  This means [applications](https://leofinance.io/@leoglossary/leoglossary-application) have to wait that time before some transactions are fully settled.  While this often happens on the back end, it can cause problems at times.

This is not going to be the case any longer.  When the next hard fork is complete, we will see the OBI drop to under 1 second.  As we can see, this is a huge improvement.

Essentially, we are bringing the speed of [Web 2.0](https://leofinance.io/@leoglossary/leoglossary-web-2-0) to [Web 3.0](https://leofinance.io/@leoglossary/leoglossary-web-3-0).

So while [Ethereum](https://leofinance.io/@crypto-guides/what-is-ethereum-eth) is trying to switch to a faster consensus model, Hive is plugging along trying to scale up even more.

## HAF - Getting Off Base Layer

The standard that [Hive](https://leofinance.io/@crypto-guides/what-is-hive-crypto-hive) operates from is to have as little on the base layer as possible.  More is being moved to [layer 2](https://leofinance.io/@leoglossary/leoglossary-layer-2) in an effort to maximize efficiency.

One of the big developments is the [Hive Application Framework](https://peakd.com/hive-139531/@blocktrades/first-update-of-2022-on-blocktrades-work-on-hive-software).  This is a solution that is going to make application development much easier on Hive.

Again, without going into all the details, there are a few points that should be stressed:

* developers can build without blockchain knowledge.  They can create in whatever languages (code) they prefer.

* optimization of HAF comes from server based technology.  This is around for decades so any future optimization will come from the same solutions major data centers are employing.

* HAF updated by blockchain [developers](https://leofinance.io/@leoglossary/leoglossary-developer); applications developers only have to tie into the HAF for the data.

Another benefit applies to the API nodes.  A lot of the calls will be eliminated since that will come from the HAF.  Things such as [account](https://leofinance.io/@leoglossary/leoglossary-account) history are built on HAF, meaning there will be less traffic on the API servers in this area.

## No More 3 Second Voting

This was something that I had not heard announcement.  Evidently, the 3 second wait time between votes is going away.

At present, if you upvote someone, say a comment, and immediately move to upvote the next one, the blockchain provides an error message.  This is against the rules.

That will not be the case post hard fork.  The feature is being removed so people will be able to vote as quickly as they can click their mouse.

The rule of 3 second voting never made much sense.  If one has an allotment of votes each day, who cares how quickly they burn through them.  That is up to the individual.

Whatever the reasoning, this is will not be a part of Hive much longer.

## Bringing A Ferrari To The Race

Hive is in the process of lapping the field.  When it comes to [scaling](https://leofinance.io/@leoglossary/leoglossary-scability-scaling), it is hard to see how others can match it.  We are basically looking at bringing a Ferrari to a race where everyone else is driving Toyota Corollas.

While it is true that the best technology does not always win, we can see how important scaling is.  Again, we just went through months (years) of watching Ethereum make the switch to [PoS](https://leofinance.io/@leoglossary/leoglossary-proof-of-stake-pos).  This was done primarily for scaling reasons.  Yet, in spite of all that effort, they still do not have much of what Hive is offering once this hard fork goes through.

At present, Splinterlands provides most of the traffic on Hive.  The goal with all the development is to be able to handle a dozen [Splinterlands](https://splinterlands.com/).  That is something that we do not see around the blockchain world.

Ethereum was bogged down by one game.  This caused a half-decade quest to ensure it doesn't happen again.  Hive is working to make sure a few dozen successful applications doesn't lock up the [network](https://leofinance.io/@leoglossary/leoglossary-network).

The development just keeps racing ahead.

By the way, the hard fork is tentatively scheduled for Oct. 11th.

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



https://images.hive.blog/0x0/https://files.peakd.com/file/peakd-hive/doze/MkkDNhyH-2020_04_13_16_57_48.gif

gif by @doze

![screen_vision2025_1.png](https://images.hive.blog/DQmXEv6MvKTCurBzSdbKjWzFadJwfJfJfmA2We9EwD5q5Vb/screen_vision2025_1.png)

logo by @st8z

Posted Using [LeoFinance <sup>Beta</sup>](https://leofinance.io/@taskmaster4450/hivefest-core-development)