Join GitHub today
GitHub is home to over 31 million developers working together to host and review code, manage projects, and build software together.Sign up
Decrease the number of missed/deleted blocks #2080
Ensure Consenus stays or reaches high value when there is a delegate slot to forge. Provide the reliable overview of the network status by collecting the information about recent Peers broadhashes. The slots to forge blocks won't be missed then.
High Broadcast performance
Every data (block/transaction/signature) broadcast should reach all of the Peers. The probability of triggering the fork recovery mechanism will be relatively low - blocks won't be deleted.
The end-goal scenario should be possible based on algorithmic Peers selection, that will guarantee 100% coverage of the network while propagating data. By constainting the numbers of Peers to connect, the scalability of the solution will be kept.
Before forging a block, Broadhash Consensus is being checked. Delegate misses it's slot to forge when Consensus stays < 50 in every of 10 checks within his time slot. It can occur when:
Low Consensus increases missed blocks in the network.
Current data (block/transaction/signature) broadcasts are not reaching the network in the most efficient possible way as shown on studies presented in #2077. It:
If Consensus reaches the demanded value only at the last forging attempts or broadcasted blocks didn't reach the whole network, it is most likely that fork1 (broadcasting delays) recovery mechanism gets triggered on all of the Peers that will receive the block in next delegates slot. Block gets deleted - the next or the previous delegate loses a block.
Steps to reproduce
Investigate the number of slots missed by delegates/fork.
Which version(s) does this affect? (Environment, OS, etc...)