Allow me to introduce to you some of the dynamics of how the Helios Protocol network operates. Helios Protocol aims to solve some of the problems such as scalability and transaction speed; hurdles that blockchains, like Ethereum, face today. The Helios Protocol network is a combination of both blockchain technology and the utilization of a Directed Acyclic Graph (DAG), which is a topological sorting of nodes.

Instead of the serialized blockchain process, like Ethereum, Helios uses a parallel blockchain process that is infinitely scalable. Every wallet address has its own blockchain! When a transaction is made, the only wallets that are interacting are the sending and receiving wallets. Transactions will not have to wait for the next block to be processed on a single blockchain like it would on a bogged down, serialized blockchain. Essentially, in terms of transaction speed, it doesn’t matter how many transactions are being made on the Helios platform at the same time. Other simultaneous transactions will not slow down your transaction speeds. The blockchain count continues to grow as wallets continue to be added. As a result, this produces no bottlenecking and infinite scalability.

The Tech Behind the Protocol

Helios has spent a lot of time deciding on the most precise and effective consensus mechanism to utilize within the protocol. A consensus mechanism is used to verify that any data added to the network is valid and in agreement. The consensus mechanism that was chosen for Helios is the Magnetization Dynamics of Magnetic Dipoles. To make it simple, each magnetic dipole represents a node in the network. A node is a point of intersection/connection within a network. The direction of the magnetic dipole represents the state of a blockchain in the blockchain database. All the dipoles are parallel to each other, which means the nodes are in agreement and the blockchain has reached consensus. If any of the dipoles (nodes) are pointed in a different direction, then the consensus mechanism will realign the dipoles to reach agreement. For example, wallet A sent wallet B 100 HLS. Next, wallet A attempts to send wallet C the same 100 HLS ( aka Double Spending). This will, in effect, create a misaligned dipole, and expose the discrepancy in the network. All nodes in the network are constantly recalculating. This would cause some dipoles to change their position (they would point in a different direction compared to the majority). These misaligned nodes will then be corrected, and lined back up in accordance with the consensus. This results in a runaway effect that runs through the entire network until all nodes are in the same state (All dipoles are back to parallel with each other in agreement). Dipoles will always align themselves with the majority in close proximity. The network will always choose the majority and ignore any node that tries to alter the blockchain, which provides immutability. This simply means that the transactions added to the network cannot be altered or changed. Seeing how the dipoles are in close proximity to one another, this allows for fast and reliable communication. These communication properties are the same between the magnetic dipole consensus mechanism and a fast and highly efficient decentralized network.

Conclusion

Helios Protocol aims to solve scalability issues that blockchain infrastructures are facing today by implementing both PoS and magnetism as a consensus by giving each wallet address its own blockchain. The more wallets, the more blockchains. The more blockchains, the more nodes, hence infinite scalability.

Written by Casey Linsenbigler

Website: https://heliosprotocol.io/

Discord: https://discord.gg/baUak26

Facebook: https://www.facebook.com/HeliosProtocolPlatform/

Twitter: https://twitter.com/HeliosPlatform

Instagram: https://www.instagram.com/heliosprotocol/

Telegram: https://t.me/joinchat/GSuKeBGme_EoTjHCiGmupQ

Github: https://github.com/Helios-Protocol/py-helios-node

4 votes, average: 5.00 out of 54 votes, average: 5.00 out of 54 votes, average: 5.00 out of 54 votes, average: 5.00 out of 54 votes, average: 5.00 out of 5 (4 votes, average: 5.00 out of 5)
You need to be a registered member to rate this.
(493 total tokens earned)
Loading...

Responses