Jan 20, 2026

After a fix to the wolfssl embed, I was finally able to move on to socket integration of the ssl context. The socket is now fully able to support tls over tcp (for electrum/stratum-v1 json-rpc), http (bitcoind json-rpc, rest, admin web, rest API), and websockets (fully implemented but currently not used). The remaining work is all connecting the dots between configuration, construction/retention of the ssl context for a given endpoint, and passage of the context via session->acceptor for accept, and acceptor->socket upon tcp connect (at socket construct). Nothing complicated here, so expect to have this all hooked up tomorrow, and be able to start configuring and testing it. The implementation is able to support packet level privacy, server auth, and client auth, based on context config for a given endpoint, with independent context for each endpoint. It will also support secure and non-secure endpoints for the same service, if enabled by configuration. Finally, the socket can accept other types of configuration context (variant), and other types of socket streams (also variant), so this will allow drop-in support for zmq::context and p2p::context security. And of course we will need stream types for zmq to implement that framing, as well as for stratum-v2. But now the implementation will allow these to drop right in to config, context, stream, and security.