One of the most important things about Asch



  • Check out the white paper, under "Bizantine Fault Tolerance" and you will understand why Asch is so different. The team introduced PBFT (Practical Byzantine Fault Tolerance)
    https://www.docdroid.net/VnfmpgX/asch-white-paper-102.pdf#page=10



  • Awesome.



  • @irinawo said in One of the most important things about Asch:

    Check out the white paper, under "Bizantine Fault Tolerance" and you will understand why Asch is so different. The team introduced PBFT (Practical Byzantine Fault Tolerance)
    https://www.docdroid.net/VnfmpgX/asch-white-paper-102.pdf#page=10

    Byzantine Fault Tolerance
    The major difference between Asch system and DPOS is reflected in the second part of the
    algorithm.
    What the DPOS applied is, first, randomly sorting the delegate list of current round (to make
    sure the delegate of next round cannot be predicted since the order of delegate of each
    round will be different), then let delegates create block in turn through a round-robin way.
    The main issue of this algorithm is that, if a delegate attempt to attack, he may broadcast
    many different blocks, which may contact double payment trades, to “fork” the whole
    network. It is no doubt that if only one delegate betrays, the fork will be solved by syncing
    with the next longest chain. However, it will take a much longer time to eliminate betrayed
    nodes as their amount is increasing. A few betrayed nodes are enough to have a serious
    impact on system security, which means even we can gain 6 confirmations, it still may not be
    sure that the network is safe.

    To deal with this problem, we introduced an algorithm known as PBFT (Practical Byzantine
    Fault Tolerance). Same as DPOS, PBFT also chooses delegates in the way of round-robin. The
    different part is there will not be a block generated after delegates are voted. In fact, there
    will be a piece of propose issued to determine the hash code of next block. Only when more
    than 2/3 of all nodes agree with this propose, next block will be generated. The hash of next
    block must be the same as that agreed with all delegates of current round. Essentially, the
    introduction of PBFT solved the issue of abusing the delegates’ right, and improved the
    control capability of ledgers.



  • thanks for sharing.



  • 看不懂全是英文啊!


Log in to reply
 

Looks like your connection to Asch was lost, please wait while we try to reconnect.