Condition: A contract is created, and then modified, then self destructed in the same tx.
There are tests covering case where balance 0 -> x -> 0. And the last zero appear in the BAL balance changes.
- No test to cover nonce 0 -> x -> 0.
- No test to cover code hash EMPTY_CODEHASH -> x -> EMPTY_CODEHASH.
- Same with storage.
Regarding the balance change postBalance=0 appear in the BAL looks unnecessary, but the behavior is consistent with how the state journal works. It just weird a non existent account have BAL entries.
Condition: A contract is created, and then modified, then self destructed in the same tx.
There are tests covering case where balance 0 -> x -> 0. And the last zero appear in the BAL balance changes.
Regarding the balance change
postBalance=0appear in the BAL looks unnecessary, but the behavior is consistent with how the state journal works. It just weird a non existent account have BAL entries.