Exploration of the wave protocol
Blockchain development continues so far, trust and security brought by decentralization have been the cornerstone of ecological prosperity. From POW consensus algorithm to POS to AVAX protocol, they are constantly exploring and optimizing on the road of decentralization. To reduce energy consumption and the burden on the entire infrastructure, the requirements for consensus algorithms and protocols are also becoming increasingly lightweight. Let us deeply explore how the wave protocol is done.
The Wave Consensus protocol provides DO Network with superior performance, enabling the entire network from local to net wide to be quickly pushed through the Wave. And using lightweight algorithms to achieve net-wide consensus safely and efficiently. Waves form and gradually spread or cover the ocean. So named because the consensus process is very similar to waves. The network of DO is fully connected with 499 nodes. How to reach a consensus among 499 legitimate nodes is the only purpose of the wave protocol. Generally speaking, it is how to reach a consensus quickly without an oligarchic effect and in a relatively fair state under the number of 499 nodes, which makes the net-wide run efficiently and decentralized.
Qualified nodes running under the DO network are full nodes and are eligible to initiate data consensus and packing blocks. The wave protocol uses a random sampling method to achieve consensus. Each consensus process selects six groups of participants, each consisting of 5–6 nodes, which are randomly selected from the validation pool. If your node does not meet the requirements for entry into the verification pool, it will not be eligible for selection. The criterion for entering the verification pool depends on the synchronization state of the node and the primary network height. So have to keep the hardware configuration and network state in a sufficiently efficient state to have the entrance ticket to obtain DO benefits, which are related to the rights and interests of the physical node and all the clients.
The consensus process is lateral fault-tolerant and vertical not fault tolerance. The so-called transverse fault tolerance is six groups that do not need to complete all at one time. If a certain group has the highest computing efficiency, it will be qualified to initiate the whole network broadcast, the entire network node for final validation. Vertical fault tolerance refers to the 5–6 nodes of the first group of the whole network broadcast that must maintain an efficient and unified state; this guarantees the rigor of the whole consensus. When 60% of the leaders of the entire network reach a consensus on the legalized block, it will finally be confirmed on the chain. The above process takes 1–2 seconds, and the whole solid block time is about 10–15 seconds.
Of course this can be significantly improved and optimized and will continue to develop along with the ecology.
From the perspective of the design, the whole wave protocol is very friendly, which not only maintains the security fairness and rigor of decentralization but also gives the nodes in the horizontal plane fault-tolerant space. From the election of the verification pool to the selection of node groups for voting, can timely adjust the node status to obtain the qualification to participate in the consensus. The lightweight consensus protocol reduces the burden on the network while providing a scalable inflationary environment for physical nodes around the world, which is advanced enough to look forward to the opening of the test net.