Dec 18, 2025

The above-mentioned integration of the json-rpc http body into the variant message is complete. So the variant message now detects json in the headers and selects the derived json-rpc reader (unless a flag is set to use its base body and return the plain parsed json model). Both plain json (explore) and json-rpc (bitcoind) are now flowing through the same pipeline. Next is to hook up the new json-rpc body as reader/writer for the non-http json-rpc interfaces (electrum/stratum_v1). These are slightly different because they are line terminated, and that's baked into the json-rpc body template. If the read/write is initiated in an http socket, it uses a different constructor so the body can distinguish. I hope to have this hooked up to the electrum channel and dispatching methods tomorrow.