Dealing with mesh reorgs

[lrettig]

It's not an issue on a per-node basis but how do we handle this at the top level in the explorer (#68) and dashboard (#64)?

[avive]

I think this is addressed with our proposed layer-based stream - after reorg, updated layers will be streamed to clients. Can I close?

[lrettig]

Are there any UIUX implications for the user? Is a reorg really 100% transparent to the user, or does a user (of the dashboard or explorer) need to know when a reorg has happened? Are there issues around tx finality - e.g., where finality might be delayed because of a fork or reorg?

What about, e.g., after a network upgrade hard fork? This is probably when a fork/reorg is most likely to occur.

Just trying to think through all of the possibilities...