It prevents reverted liquidations being sent for parsing (since the classified trace for a reverted transaction will be incomplete and this will cause block processing to fail). Reverted transactions do not result in extraction of MEV and should not be included.
I've added an additional test to test_compound.py this test supplies a block which contains a reverted liquidation transaction and verifies that the transaction does not get included in the set of liquidation traces (and the fact that this block is now processed successfully - it previously didn't - demonstrates the problem has been solved).
I've also successfully run ./mev inspect on blocks which previously failed due to reverted liquidations.
What does this PR do?
It prevents reverted liquidations being sent for parsing (since the classified trace for a reverted transaction will be incomplete and this will cause block processing to fail). Reverted transactions do not result in extraction of MEV and should not be included.
Related issue
issue 315
Testing
I've added an additional test to
test_compound.pythis test supplies a block which contains a reverted liquidation transaction and verifies that the transaction does not get included in the set of liquidation traces (and the fact that this block is now processed successfully - it previously didn't - demonstrates the problem has been solved).I've also successfully run
./mev inspecton blocks which previously failed due to reverted liquidations.Checklist before merging
./mev test