It's like pushing everyone in to the face who wants to use it and saying "No, don't use an existing JSON-RPC implementation. No, build your own..."
Yeah, im referring to the "jsonrpc": "2.0" parameter.
That's the specs from the year 2010: http://jsonrpc.org/historical/json-rpc-2-0.html
The first stratum commit is dated at 19/Dec/2011. So the specs were changed without obvious reasons (at least not for me).
Why is this "based" on JSON-RPC 2.0 but does some changes to the protocol and renders all existing implementations useless: https://en.wikipedia.org/wiki/JSON-RPC#Implementations
It's like pushing everyone in to the face who wants to use it and saying "No, don't use an existing JSON-RPC implementation. No, build your own..." Yeah, im referring to the
"jsonrpc": "2.0"parameter.That's the specs from the year 2010: http://jsonrpc.org/historical/json-rpc-2-0.html The first stratum commit is dated at 19/Dec/2011. So the specs were changed without obvious reasons (at least not for me).