☂️ Reorg resistance of Ethereum backend about go-perun HOT 3 CLOSED

All done

from go-perun.

Biggest point missing: How to test this.
Currently we use the simulated block chain from go-ethereum. Im evaluating if it can do reorgs here.

from go-perun.

After adding a Reorg(depth) function to go-ethereum, i was able to get a legit reorg on the simulated backend.
It removed the previous events with a removed: true event.
It does seem, however, that the TX do not end up in the mempool again, and therefore needs to be resent by the user.
Im not sure if this is normal behaviour in a geth node or an incapability of the simulated chain.

Looking at chainlink, they periodically pull the mempool status to check that the TX is still in and resend if not.
We therefore probably need something similar to their BPTM (bullet proof TX manager).

from go-perun.