Handle user running lumina-wasm in multiple tabs

[fl0rek]

Lumina-wasm running in multiple tabs all hit the same store. Since inserting ExtendedHeader is idempotent and atomic, this works, but it basically results in all the running instances racing to get and add the next header.

Should we support running separate lumina instances in separate tabs? Is it beneficial for celestia to have a guy running lumina in 3 tabs on the same browser instead of just a single instance?

If we want to support separate instances, each one should probably have its own separate data store (headers and any future data).

If we want to support single instance, how do we enforce it. There's Broadcast Channel API, that allows inter-tab communication.
In the first pass we could just error, if there's another instance running.
Ultimately, we could have it so each new opened tab, connects to the same lumina-wasm node started previously (running in a web worker?)