Currently, if a transaction is included in a block but one of the transaction hooks fails, we skip the transaction in that block, but it won't get removed from the mempool. This leads to the transaction being applied (and failing) again and again, for some users that is unwanted behaviour.

We need to figure out how to deal with that, especially also in the context that transaction might become valid in the future. For example, the nonce might be too large for a particular account, but if another transaction with the right nonce comes along, the transaction might become valid again.
For this case, we might keep them in the mempool for the future, but we need to distinguish them from transactions that will never be valid, or ones that we want to throw out regardless.