George Knee

``` === RUN TestOPStackGenesis /Users/georgeknee/code/ethereum-optimism/op-geth/core/superchain_test.go:16: chainID=1740: produced genesis with hash 0x71d15fcf37d911d63f8738f1fde1b03cc7ff5b06ccd9331deb322aee76f35f38 but expected 0xd24cf8e46b189b0c128dab4e46168520e3a4cdd390b239e8cc1e5abd22a629ae /Users/georgeknee/code/ethereum-optimism/op-geth/core/superchain_test.go:16: chainID=8866: produced genesis with hash 0x3428b729cf29e0ef5e94c681ea63d6e65fb80a733e705b6e0dbf06561c0bc939 but expected 0x01711dc53a82967a34f4b38f7dff3ae8fa760882bb1e2ace50bb01e9ff420a9b ``` These are chains which currently...

Also related to https://github.com/ethereum-optimism/superchain-registry/issues/78. The check is duplicated in superchain-registry, only there it has exclusions and here it does not.

If we do this, let's not forget to update the docs also.

@NiloCK keen for your feedback on this.

Thanks for this input @nksazonov! Case 1 is absolutely the intended application of `checkpoint`. Case 2 was not anticipated, so I would like to hear more about that. It may...

Another timeout, but in a different test https://github.com/statechannels/go-nitro/actions/runs/6456255456/job/17525371741

@bitwiseguy I think we can close this?

This is looking good so far @NiloCK ! I think we probably want: - [ ] an ADR to accompany these changes, explaining how LN-compatible multi hop payments can be...

> The stored data for channel `0x123` should update whenever a chain event is observed for `0x123` This poses a bit of a challenge for our current architecture. I believe...

Whenever we use a durable store, this issue extends beyond "memory bloat" to disk bloat. We may also be able to save some additional space in the voucher store by...