Oct 17, 2025

It looks like we'll want to multiplex websockets onto the same ip:port bindings as the RESTful block explore service, to avoid routing of non-standard ports. This means that there ultimately won't be config for the current [socket] interface, it will just be incorporated into the [explore] interface. This does imply however that the admin [web] interface will still end up on independent bindings, which I think is important for default security config. Integrating the two sites ([web] and [explore]) will be feasible, but either on distinct IP addresses, or on distinct ports. Distinct IP addresses is ideal if you want public routing (using default ports), but locally (or over a VPN) the use of non-standards ports wouldn't matter.