Since currently Sumeragi::round_start_time updates only on block commit (or view change) and the block timer keeps ringing under situation of no transactions, the next transaction arrival meets the condition and a new block can be immediately created for that single transaction, which might be a waste of resources
Since currently
Sumeragi::round_start_timeupdates only on block commit (or view change) and the block timer keeps ringing under situation of no transactions, the next transaction arrival meets the condition and a new block can be immediately created for that single transaction, which might be a waste of resources