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 all transactions in a failed block are reverted in their entirety. Though blocks should not fail, the likely cause would be a bug in the processing of some transaction(s).
Probably most transactions in the block are fine, and we only need to weed out the couple that are causing issues. Right now our strategy just nukes the entire set.
We could improve this by allowing transactions to be part of failing proofs x number of times before reverting them. e.g. a transaction is only reverted entirely once it has been part of x batch and/or block failures.
The text was updated successfully, but these errors were encountered:
Currently all transactions in a failed block are reverted in their entirety. Though blocks should not fail, the likely cause would be a bug in the processing of some transaction(s).
Probably most transactions in the block are fine, and we only need to weed out the couple that are causing issues. Right now our strategy just nukes the entire set.
We could improve this by allowing transactions to be part of failing proofs
x
number of times before reverting them. e.g. a transaction is only reverted entirely once it has been part ofx
batch and/or block failures.The text was updated successfully, but these errors were encountered: