Nov 19, 2025

The http interface above is really just for a generic directory/embedded server (e.g. admin) site. The block explore site will use a different interface (restful query). While it will also run over http/s and ws/s transports, as with all of the interfaces, it will be independent of transport, encoding, and serialization. The interface definitions above are about the message structure - supporting fully-generalized dispatch. I've previously completed most of the work to generalize transports (http/s, ws/s, p2p/s, tcp/s zmq/s, encodings (data, text, json, html), and serialization (json-rpc, peer, explore, web, sv2). The design is to use a single pair of proxy methods (send/receive), a single pair of messages (request/response), and a single interface (generic rpc dispatch of request), with multiple message bodies to provide parse/serialize from/to all encodings, multiple message headers to prove framing for all transports, including body selection on read, and two pairs of fundamental transports (tcp, tcp/s, ws, ws/s). Really that's just tcp and ws with tls added, though there are three forms of secure sockets (tls, CurveCP, and bitcoin p2p has its own special brand). Other transports like http, zmq, and p2p are just tcp from this perspective, as only ws and tls require socket integration (framing).