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
When a block is produced or imported, the associated txs need to be removed from the pool. However, our current removal method assumes that the tx and all it's dependencies should be removed. This is problematic as the dependent txs may be unnecessarily removed from the txpool.
Expected behavior:
when a block is imported
the txs that were successfully process should be removed and their dependencies should be kept
txs that were skipped should be removed along with any dependencies
when transactions are selected for block production
they should be removed without removing dependencies, but the depth of the dependencies should be updated
any skipped transactions from block production should also remove dependents in the txpool, although this should be handled by the same mechanism as block import
The text was updated successfully, but these errors were encountered:
When a block is produced or imported, the associated txs need to be removed from the pool. However, our current removal method assumes that the tx and all it's dependencies should be removed. This is problematic as the dependent txs may be unnecessarily removed from the txpool.
Expected behavior:
The text was updated successfully, but these errors were encountered: