In our version of Simplex, a node only builds a block in one of two cases:
- Transactions exist in the mempool of the VM and a block should be built to contain them
- The block builder detects that an epoch change should occur, or is ongoing, so it builds a block to initiate or drive forward the epoch change.
This means that a block is not built if there is nothing in the mempool or there is no need to initiate an epoch change.
For (1), if a node that is not designated as the leader of the current round detects that transactions exist in the mempool for too long without a block being built and disseminated, it starts lobbying to notarize an empty block, which should make the nodes move to the next round and this will designate a new leader.
For (2), #514 introduces a mechanism in which a node that is not the leader of the round also starts lobbying to notarize an empty block if a block isn't being built and disseminated for too long and the previous block indicates that there is an ongoing epoch change, or that the previous block doesn't indicate that, but an epoch change should be initiated.
Completing the epoch change requires gathering approvals from at least a quorum of nodes of the next epoch.
However, if there are not enough approvals to collect because the nodes of the next epoch are not available yet (e.g they are still syncing the P-chain) it would mean that blocks will be built indefinitely until then.
We could make the epoch change and the mechanism introduced in (2) smarter and only build a block or expect one to be build in case we know that we can drive forward the approval collection, but that's a problem for the future.
In our version of Simplex, a node only builds a block in one of two cases:
This means that a block is not built if there is nothing in the mempool or there is no need to initiate an epoch change.
For (1), if a node that is not designated as the leader of the current round detects that transactions exist in the mempool for too long without a block being built and disseminated, it starts lobbying to notarize an empty block, which should make the nodes move to the next round and this will designate a new leader.
For (2), #514 introduces a mechanism in which a node that is not the leader of the round also starts lobbying to notarize an empty block if a block isn't being built and disseminated for too long and the previous block indicates that there is an ongoing epoch change, or that the previous block doesn't indicate that, but an epoch change should be initiated.
Completing the epoch change requires gathering approvals from at least a quorum of nodes of the next epoch.
However, if there are not enough approvals to collect because the nodes of the next epoch are not available yet (e.g they are still syncing the P-chain) it would mean that blocks will be built indefinitely until then.
We could make the epoch change and the mechanism introduced in (2) smarter and only build a block or expect one to be build in case we know that we can drive forward the approval collection, but that's a problem for the future.