Transaction included in two different blocks
gballet opened this issue · comments
Guillaume Ballet commented
After the rebase (see #237), syncing is broken because a transaction that was included in a much earlier block, is included again.
Since the transaction has nonce 0, my guess is that the state that generated it is partially invalid, and checking for the existence of an account returns 0 (when it is, in fact, present).
Guillaume Ballet commented
the bug is no longer reproducible after fixing other issues.