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 block producer assumes that the txs being passed to it in PrepareProposal have signatures for whatever square size that it picks. This is particularly problematic when there are only a few transaction in the mempool that are only signed over large square sizes. This results in those txs not being included until a larger block is created, which will not occur until their are enough transactions passed to PrepareProposal.
The easiest way to prevent this is to sign over all relevant block sizes by default #239, but we might want to consider also checking the txs that are passed to PrepareProposal before we estimate square size. If we do that, then we can check for this exact situation. We would end up producing a less efficient block, as there would be a lot of tail padding shares added, but at least the users txs wouldn't get stuck in the mempool until a larger block is created.
The text was updated successfully, but these errors were encountered:
Currently the block producer assumes that the txs being passed to it in
PrepareProposal
have signatures for whatever square size that it picks. This is particularly problematic when there are only a few transaction in the mempool that are only signed over large square sizes. This results in those txs not being included until a larger block is created, which will not occur until their are enough transactions passed toPrepareProposal
.The easiest way to prevent this is to sign over all relevant block sizes by default #239, but we might want to consider also checking the txs that are passed to
PrepareProposal
before we estimate square size. If we do that, then we can check for this exact situation. We would end up producing a less efficient block, as there would be a lot of tail padding shares added, but at least the users txs wouldn't get stuck in the mempool until a larger block is created.The text was updated successfully, but these errors were encountered: