Decentralized Proof-of-Authority Consensus </a></li><li><a href="/it/concepts/blockchain-layers.html" class="sidebar-link">The IBAX Network </a></li><li><a href="/it/concepts/consensus.html" aria-current="page" class="active sidebar-link">Decentralized Proof-of-Authority Consensus </a><ul class="sidebar-sub-headers"><li class="sidebar-sub-header"><a href="/it/concepts/consensus.html#what-is-decentralized-proof-of-authority-consensus" class="sidebar-link">What is Decentralized Proof-of-Authority consensus </a></li><li class="sidebar-sub-header"><a href="/it/concepts/consensus.html#advantages-of-dpoa-consensus" class="sidebar-link">Advantages of DPoA consensus </a></li><li class="sidebar-sub-header"><a href="/it/concepts/consensus.html#dpoa-consensus-and-common-means-of-attack" class="sidebar-link">DPoA consensus and common means of attack </a><ul class="sidebar-sub-headers"><li class="sidebar-sub-header"><a href="/it/concepts/consensus.html#dos" class="sidebar-link">DoS </a></li><li class="sidebar-sub-header"><a href="/it/concepts/consensus.html#percent-attack-51" class="sidebar-link">51 percent attack </a></li></ul></li><li class="sidebar-sub-header"><a href="/it/concepts/consensus.html#implementation-of-dpoa-consensus-in-ibax" class="sidebar-link">Implementation of DPoA consensus in IBAX </a><ul class="sidebar-sub-headers"><li class="sidebar-sub-header"><a href="/it/concepts/consensus.html#honor-node" class="sidebar-link">Honor node </a></li><li class="sidebar-sub-header"><a href="/it/concepts/consensus.html#leader-node" class="sidebar-link">Leader node </a></li><li class="sidebar-sub-header"><a href="/it/concepts/consensus.html#forks" class="sidebar-link">Forks </a></li></ul></li></ul></li><li><a href="/it/concepts/thesaurus.html" class="sidebar-link">Terms and Definitions </a></li></ul></section></li><li><section class="sidebar-group collapsable depth-0"><p class="sidebar-heading"><span>Problema comune</span> <span class="arrow right"></span></p> </section></li></ul> </aside> <main class="page"> <div class="theme-default-content content__default"><h1 id="decentralized-proof-of-authority-consensus"><a href="#decentralized-proof-of-authority-consensus" class="header-anchor">#</a> Decentralized Proof-of-Authority Consensus </h1> <ul><li><p>What is Decentralized Proof-of-Authority consensus</p></li> <li><p>Advantages of DPoA consensus</p></li> <li><p>DPoA consensus and common means of attack</p></li> <li><p>Implementation of DPoA consensus in IBAX</p></li></ul> <p>In this section, we will describe the Decentralized Proof-of-Authority consensus and its implementation in IBAX.</p> <ul><li><a href="#what-is-decentralized-proof-of-authority-consensus">What is Decentralized Proof-of-Authority consensus</a></li> <li><a href="#advantages-of-dpoa-consensus">Advantages of DPoA consensus</a></li> <li><a href="#dpoa-consensus-and-common-means-of-attack">DPoA consensus and common means of attack</a> <ul><li><a href="#dos">DoS</a></li> <li><a href="#percent-attack-51">51 percent attack</a></li></ul></li> <li><a href="#implementation-of-dpoa-consensus-in-ibax">Implementation of DPoA consensus in IBAX</a> <ul><li><a href="#honor-node">Honor node</a></li> <li><a href="#leader-node">Leader node</a></li> <li><a href="#generation-of-new-blocks">Generation of new blocks</a></li> <li><a href="#forks">Forks</a></li></ul></li></ul> <h2 id="what-is-decentralized-proof-of-authority-consensus"><a href="#what-is-decentralized-proof-of-authority-consensus" class="header-anchor">#</a> What is Decentralized Proof-of-Authority consensus </h2> <p>Considering commercial application scenarios and real-world environments, IBAX Network has built a new consensus mechanism, DPoA (Decentralized Proof of Authority).</p> <p>Decentralization has always been our firm belief. It refers not only to IBAX’s infrastructure network environment. Instead, we will let decentralization take root in each ecoLib created in IBAX Network and use technical solutions to achieve a high degree of self-governance in each of them. For the purpose of highly distributed self-governance, we have made many changes in the overall architecture and technical implementation. However, in practice, we cannot avoid the centralized management concept. In order to find a balance between centralization and decentralization, in addition to the DPoA consensus mechanism, we have also formulated certain reward and incentive programs.</p> <p>IBAX Network has created a new consensus mechanism that combines distribution, weak centralization, and a certification authority. We call it DPoA (Decentralized Proof of Authority). To ensure continuity for the entire IBAX Network, the consensus covers not only IBAX Public Network, but also ecoLibs created by each user and user group. This creates a truly self-governed, decentralized, fair, transparent, and fraud-proof Decentralized Autonomous Organization (DAO).</p> <p>DPoA has a prevention mechanism against network attacks and allows creation of Mint Nodes that guard the network and mint new IBXC coins. IBAXCoin holders can stake a part of their IBXC liquidity balance in Mint Nodes for Mint & Stake Emission Rewards. Minting and staking serve to increase the cost and difficulty of attacks and increase the total value of IBXC coins proportionally. With this mechanism, the probability and harm of any attack are infinitely close to zero.</p> <h2 id="advantages-of-dpoa-consensus"><a href="#advantages-of-dpoa-consensus" class="header-anchor">#</a> Advantages of DPoA consensus </h2> <p>Compared to Proof-of-Work (PoW) or Proof-of-Stake (PoS) consensus, DPoA consensus has the following advantages:</p> <ul><li><p>No need of high-performance hardware. Compared to PoW consensus, nodes implementing the DPoA consensus does not spend computational resources for solving complex mathematical logic tasks;</p></li> <li><p>The interval of time to generate new blocks is predictable, but that for PoW and PoS consensuses are different;</p></li> <li><p>High transaction rate. Blocks are generated in a sequence at specified time interval by authorized network nodes, which increases the speed of transaction verification.</p></li> <li><p>Tolerance to compromised and malicious nodes, as long as 51% of nodes are not compromised. IBAX implements a mechanism of banning nodes and revoking block generation rights.</p></li></ul> <h2 id="dpoa-consensus-and-common-means-of-attack"><a href="#dpoa-consensus-and-common-means-of-attack" class="header-anchor">#</a> DPoA consensus and common means of attack </h2> <h3 id="dos"><a href="#dos" class="header-anchor">#</a> DoS </h3> <p>An attacker may send large amount of transactions and blocks to a targeted node in the network, making an attempt to disrupt its operation and make its services unavailable.</p> <p>The DPoA mechanism is possible to defend against DoS attacks:</p> <ul><li><p>Because network nodes are pre-authenticated, block generation rights can be granted only to nodes that can withstand DoS attacks.</p></li> <li><p>If a honor node is unavailable for a certain period, it can be excluded from the list of honor nodes.</p></li></ul> <h3 id="percent-attack-51"><a href="#percent-attack-51" class="header-anchor">#</a> 51 percent attack </h3> <p>As to the scenario with the DPoA consensus, the 51% attack requires an attacker to obtain control over 51% of network nodes. But the scenario for the PoW consensus is different, which an attacker needs to obtain 51% of network computational power. Obtaining the control over nodes in a permissioned blockchain network is much harder than obtaining the computational power.</p> <p>For example, in a network implementing the PoW consensus, an attacker can increase computation power (performance) of the controlled network segment thus increasing the percentage of controlled nodes. This makes no sense for DPoA consensus, because the computational power of the node has no impact on the blockchain network decisions.</p> <h2 id="implementation-of-dpoa-consensus-in-ibax"><a href="#implementation-of-dpoa-consensus-in-ibax" class="header-anchor">#</a> Implementation of DPoA consensus in IBAX </h2> <h3 id="honor-node"><a href="#honor-node" class="header-anchor">#</a> Honor node </h3> <p>In IBAX, only honor nodes can generate new blocks, which maintain the blockchain network and the distributed ledger.</p> <p>The list of honor nodes is kept in the blockchain registry. The order of nodes determines the sequence in which nodes generate new blocks.</p> <h3 id="leader-node"><a href="#leader-node" class="header-anchor">#</a> Leader node </h3> <p>The leader node is the honor node that generates a new block at the current time. The following formula determines the leader node in the current honor node list:</p> <div class="language- extra-class"><pre class="language-text"><code>leader = ((time - first) / step) % nodes </code></pre></div><blockquote><p>leader</p></blockquote> <div class="language- extra-class"><pre><code>Current leader node. </code></pre></div><blockquote><p>time</p></blockquote> <div class="language- extra-class"><pre><code>Current time (UNIX). </code></pre></div><blockquote><p>first</p></blockquote> <div class="language- extra-class"><pre><code>First block generation time (UNIX). </code></pre></div><blockquote><p>step</p></blockquote> <div class="language- extra-class"><pre><code>Number of seconds in the block generation interval. </code></pre></div><blockquote><p>nodes</p></blockquote> <div class="language- extra-class"><pre><code>Total number of honor nodes. </code></pre></div><h4 id="generation-of-new-blocks"><a href="#generation-of-new-blocks" class="header-anchor">#</a> Generation of new blocks </h4> <p>New blocks are generated by a <a href="#leader-node">leader node</a> of the current time interval. At each time interval, the leader role is passed to the next honor node from the list of honor nodes.</p> <p><img src="/block-generation.png" alt="avatar"></p> <p>a) Steps for Generation of new blocks</p> <p>Main steps for generating a new block are as follows:</p> <ol><li><p>Collects all new transactions from the transaction queue of the node;</p></li> <li><p>Executes transactions one by one. Invalid or inexecutable transactions are rejected;</p></li> <li><p>Checks if the <a href="/it/reference/platform-parameters.html#configure-the-generation-of-blocks">block generation limits</a> is in compliance;</p></li> <li><p>Generates a block with valid transactions and signs it with the private key of the honor node through the ECDSA algorithm;</p></li> <li><p>Sends this block to other honor nodes.</p></li></ol> <p>b) Verification of new blocks</p> <p>Steps for verifying new blocks on other honor nodes:</p> <p>1.Receive a new block and verify:</p> <div class="language- extra-class"><pre><code>– whether the new block was generated by the leader node of a current interval; – whether there are no other blocks generated by the leader node of a current interval; – whether the new block is properly signed. </code></pre></div><ol start="2"><li><p>Execute transactions from the block one by one. Check whether the transactions are executed successfully and within the <a href="/it/reference/platform-parameters.html#configure-the-generation-of-blocks">block generation limits</a> .</p></li> <li><p>Add or reject the block, depending on the previous step:</p> <p>– If block validation is successful, add the new block to the blockchain of the current node;</p> <p>– If block validation failed, reject the block and send a <strong>bad block</strong> transaction;</p> <p>– If the honor node that created this invalid block continues to generate bad blocks, it can be banned or excluded from the list of honor nodes.</p></li></ol> <h3 id="forks"><a href="#forks" class="header-anchor">#</a> Forks </h3> <p>A <strong>fork</strong> is an alternative version of the blockchain, which contains one or more blocks that were generated independently from the rest of the blockchain.</p> <p>Forks usually occur when a part of the network becomes desynchronized. Factors that are probably result in forks are high network latency, intentional or unintentional time limits violation, time desynchronization at nodes. If network nodes have a significant geographic distribution, block generation interval must be increased.</p> <p>Forks are resolved by following the longest blockchain rule. When two blockchain versions are detected, honor nodes rollback the shorter one and accept the longer one.</p> <p><img src="/block-fork-resolution.png" alt="avatar"></p></div> <footer class="page-edit"><div class="edit-link"><a href="https://github.com/IBAX-io/documentation/edit/master/docs/it/concepts/consensus.md" target="_blank" rel="noopener noreferrer">Modifica questa pagina su GitHub</a> <span><svg xmlns="http://www.w3.org/2000/svg" aria-hidden="true" focusable="false" x="0px" y="0px" viewBox="0 0 100 100" width="15" height="15" class="icon outbound"><path fill="currentColor" d="M18.8,85.1h56l0,0c2.2,0,4-1.8,4-4v-32h-8v28h-48v-48h28v-8h-32l0,0c-2.2,0-4,1.8-4,4v56C14.8,83.3,16.6,85.1,18.8,85.1z"></path> <polygon fill="currentColor" points="45.7,48.7 51.3,54.3 77.2,28.5 77.2,37.2 85.2,37.2 85.2,14.9 62.8,14.9 62.8,22.9 71.5,22.9"></polygon></svg> <span class="sr-only">(opens new window)</span></span></div> <div class="last-updated"><span class="prefix">Ultimo aggiornamento:</span> <span class="time">25/6/2023, 15:46:02</span></div></footer> <div class="page-nav"><p class="inner"><span class="prev"> ← <a href="/it/concepts/blockchain-layers.html" class="prev"> The IBAX Network </a></span> <span class="next"><a href="/it/concepts/thesaurus.html"> Terms and Definitions </a> → </span></p></div> </main></div><div class="global-ui"></div></div> <script src="/assets/js/app.d049f7ab.js" defer></script><script src="/assets/js/2.8d94a0db.js" defer></script><script src="/assets/js/71.60bc2b12.js" defer></script> </body> </html>