Spike: see how we to test rollbacks and their consequences on the head lifecycle.

[KtorZ]

Why & What

In the pursuit of #184, we'll need to find a proper way to test the effect of rollbacks. There are several approaches to this, some more reliable than other. We could for example replace our single-BFT node setup in the end-to-end by a cluster of pools; this approach however isn't fully reliable as the presence of rollbacks will heavily depends on the random leader election procedure. Plus, it is a pain to work with when it comes to fixtures (e.g. getting funds from a faucet).

Another approach could be perhaps to use a mock-server which would simulate rollbacks events in a deterministic manner. This would not replace a full end-to-end scenarios but it may be sufficient to already try out various complex scenarios involving rollbacks.

Product requirements (optional)

N/A

Technical requirements (optional)

• We define a micro-test-framework for injecting rollbacks in our tests to see their effect and reliably build features that accommodate rollbacks.