You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, the miner has a timeout when waiting for a block to be approved or rejected. When that timeout is reached, it essentially gives up on that block and proposes a new block. This new proposal will be guaranteed to be rejected by any signers that accepted the block initially proposed, so this is not helpful. It would be better for the miner to simply re-proposed the same block, just in case that somehow helps reach a signer which did not respond to the previous proposal.
The scenarios where this is necessary also highlight the need to begin punishing non-responsive signers so that they are incentivized to remain responsive. This scenario is happening more often than it should.
Currently, the miner has a timeout when waiting for a block to be approved or rejected. When that timeout is reached, it essentially gives up on that block and proposes a new block. This new proposal will be guaranteed to be rejected by any signers that accepted the block initially proposed, so this is not helpful. It would be better for the miner to simply re-proposed the same block, just in case that somehow helps reach a signer which did not respond to the previous proposal.
See #5847 for background discussion.
The text was updated successfully, but these errors were encountered: