There are a couple major changes upcoming to Hive base coding that is going to add a couple features that address bottlenecks. One focuses upon users while the other is tied to infrastructure.
The information for this article came from the reports posted by @blocktrades that can be found HERE and HERE.
Lite Nodes
Scaling is crucial to any network. The ability to grow is essential. In the digital world, that is often summarized by the word "bandwidth". Basically this means enough throughput to process whatever it required.
When it comes to blockchain-based networks, the ability to decentralize is also crucial. This means having enough nodes in operation so that there is no only redundancy, but also unrelated parties operating the software.
As the amount of data grows, challenges are encountered. The size of the nodes required to ensure proper "bandwidth" gets larger. If left unchecked, this could get to the point where the database exceeds the technology on the market.
Fortunately, Hive is not at this point. The last hard fork saw new compression that reduced the size by around 50%.
Evidently, the next phase in the evolution is Lite nodes.
What is a lite node?
It is a node that runs only a certain portion of the database, opting against maintaining all blocks. This is a way for applications to run their own infrastructure without having to keep everything. Naturally, you cannot have all lite nodes some many have to maintain all since the genesis block. However, this will provide another option for developers.
Here is how it was phrased:
Ideally, hived nodes should retain the entire blockchain history, as this provides more redundant storage to any node that is not yet in sync with the current Hive head block, allowing such nodes to get the old blocks they don’t have from their peers.
But at some point, such storage becomes overkill, and it also increases the costs to run services that require a hived node becomes of the associated storage costs. Currently, even with the new features for compressing block storage that cuts storage costs in half, the block_log file is 486GB in size (almost ½ a terabyte).
For those who do not require the entire blockchain, this could be a viable options.
Here is how it essentially works:
Setting the block-log-split option to any larger value tells hived to maintain at least that many million recent blocks. For example, setting `block-log-split=2’ means keep at least the last 2 million blocks. In this mode, the block log is stored in multiple files (e.g. block_log_part.0084 contains blocks up to 84M, block_log_part.0085 contains blocks up to block 85M, and the “top” file block_log_part.0086 contains blocks from 85,000,001 to the current head block), each 1 million blocks long and split at 1 million byte boundaries (except for the currently “top” file which will only contain blocks up to the current head block).
The node operators consider how many blocks they want to store. We also see, in the articles, different ways to store the legacy data if switching to this setup.
Hence, technical teams will have the choice of running a scaled down node if this is all that is required.
Lite Accounts
This is something that was discussed over the years and is now being developed.
Lite accounts will provide the ability for people to engage with applications while not requiring a full Hive account. Notice how it says "sign second layer transactions".
We are creating a new HAF app to manage the creation and maintenance of “Lite” accounts that can be used by any 2nd layer app to sign 2nd layer transactions. The specification for this also includes documentation for how we plan to support 2nd layer transactions.
This is a problem that Hive has battled. We know it is not easy to get a Hive account and some applications looked to build their own. The results, so far, are varied.
Here we are seeing this tied to HAF, a server system any application can tap into. This is a way for any layer 2 application to provide people with Lite accounts in a manner that allows engagement and interaction without having to have a full account.
This is going to expand in the future:
We also have a plan for how to create namespaces for other blockchains and also non-blockchain apps such as google/facebook, etc, but I’ll go into that more in a later report.
This means allowing access from accounts people already have.
Next Hard Fork
There also appears to be a date on the next hard fork. In fact, we are going to get a couple in a small window.
We’re planning to release 1.27.7 sometime in July (probably near the end of July). As part of this release, we’re also setting what we expect will be the final “trigger date” for hardfork 28: September 24, 2024 at 14:00 UTC (to allow a little time after the upcoming HiveFest in Croatia).
September 24 seems to be the date that was selected.
We also get this:
We plan to first implement support for BLS in the new WAX API library, where it will initially be useful for 2nd layer apps, then assuming we find no problems, add support for BLS in the 1st layer (in HF 29, which is scheduled for a relatively quick release after HF 28).
For full details of the check back to the two articles linked at the top.
Posted Using InLeo Alpha
Reading this article reminded me that I don't really know much, from my understanding of this technical terms which are quite limited still sounds awesome. The lite node idea sounds like a specific focus storage tool for blockchain technology which will enhance the platform speed and effectiveness overall, which is something I look forward to although I might not even notice it unless reading the announcement post.
The second update is of great importance as I have tried inviting people but due to how hard it is to get an account they give up it's going to be a game changer once it will be released, we will be looking forward to an influx of new members and talents which is very good for the platform as more owners may be identified.
There are a few initiatives designed to address that issue. This is another one. Hopefully they will be cleared up soon.
BLS support on the L1 is critical towards ensuring VSC is safe and secure. This is a great effort by the core team to get our suggested changes implemented!
I listened to the call when you proposed it. Glad to see it being integrated.
Lite accounts that is awesome! It is so hard for me to onboard people at Hive specially here (Philippines). This is a huge change for Hive Blockchain! Thank you to all the people involved in this, more Hive Power to you guys!
It is a message the developers heard and are working on.
Thank you devs!
Fortunately, Hive is not at this point. The last hard fork saw new compression that reduced the size by around 50%. not sure I have heard of this before friend, can you help throw more highlights? Post links will also be vital. Thanks for the update.
Search blocktrades account. He does a 9-12 posts per year so it is easy to scroll back and see what he wrote leading up to that.
ok, i'll do that. Thanks friend. It's always good to stay updated.
Could Lite nodes present some kind of security issue to #hive? Because if you're not going through all blocks that could be an issue down the road... But maybe not...
Nodes still process all the blocks. But when configured as a lite node, they don't need to keep them around afterwards.
Thanks for the answer, I think I've understood it, but Could have any problems when a Lite node updates the blocks to the Nodes?
The only reason nodes normally keep blocks around is to give them to other nodes that haven't seen them (i.e. new nodes being setup for the first time). In the case of lite nodes, they won't have the older blocks, so nodes will need to get them from non-lite nodes.
Got it. The "older blocks" from hive will be kept as it's doing now, but Lite Nodes will do parallel transactions and then upload it to the "main" Nodes, right? That way they'll be faster because they don't need to keep all the chain of blocks updates only what they are focused doing... 🤔
Great news, storage was the reason i didn't setup a hive node yet. Maybe a lite node will be a good Option for many.
Depends upon the utility but, yes, it does have applications that will appeal to certain initiatives or developers.
These are exciting updates. I really like the lite accounts since it can entice more people to try Hive out without having to pay for anything. I do wonder about its limitations and difference with full accounts. Will the lite accounts still be able to work and earn with all the Hive apps/games?
The idea behind lite accounts was basically to send and receive HIVE, similar to what a Litecoin wallet does. I do not know how they changed in the programming.
They are going to be layer 2 according to the info which means they will not have access to most of the base layer features. I am sure they can engage but things such as governance are not included.
I see. I guess it's much more limited that I imagined. Thanks.
We will have to wait and see what rolls out. There might be more info in the gitlab. I dont know.
Wow brother, Lite nodes and Lite accounts are great developments for Hive. Yes Lite nodes may streamline operations but I wonder about potential security implications for Hive as well
There's no security implications: lite nodes do all the cryptographic checking that a regular node does. They just don't keep all the original block data around after they process it.
Oh wow brother You just explained it so perfectly with one statement I get it now wow I'm super excited for this. Thanks for the explanation.. here's some !PIZZA !WINE and !BEER
No need for me to answer since Blocktrades took care of this.
Yes brother, he did justice to it perfectly well I understand it now hehehe
Congratulations @taskmaster4450! You have completed the following achievement on the Hive blockchain And have been rewarded with New badge(s)
Your next target is to reach 2210000 upvotes.
Your next target is to reach 75000 replies.
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
STOP$PIZZA slices delivered:
@theringmaster(2/5) tipped @blocktrades