Consider using other library then openssl #2
Description
The Client uses openssl. I was able to run the example with an old version of openssl (1.1.1) that performs better tree shaking during linking, but for the newer version (>=3) the binary got really big although the openssl library was used only for SHA256. I would probably suggest using mbedtls instead of openssl, as this is a more lightweight library. Or maybe the user can provide a callback for computing SHA256 (I don't know if that is a good design, but maybe worth considering)? In my setting of the example I was using openssl only as the dependency of the Client and curl with mbedtls (as the example uses curl).