The layer systems one isn't related, I've also been getting them for some reason.

What's actually happening is that state is updated by the engine (golang).

Nostrocket is designed to allow state machines to run in different places, e.g. heavy computation and rebuilding version control systems like git would be done using the golang client, and lighter stuff can be done in the browser.

But right now for PoC it's all in golang and this publishes stage updates that the browser consumes. To request state to be updated, the browser client sends events to the 688 relay.

Clients do not assume any particular order of events from relays, they figure out the correct event order, this happens in eventconductor.go in the engine (have a look at the engine repo in nostrocket org)