You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We might want to restore that support. We already replace requests with jsonrpc = "1.0" (which is nonsensical, since the field did not exist in 1.0, but some tools like lightwalletd use it) to jsonrpc = "2.0" using a middleware; it might be simple to make it addjsonrpc = "2.0" if the jsonrpc field is missing.
Specifications
No response
Complex Code or Requirements
No response
Testing
No response
Related Work
No response
The text was updated successfully, but these errors were encountered:
I have this working in zallet. I based my JSON-RPC handler on zebrad and zebra-rpc (but couldn't depend on either), and in addition to fixing this bug I enhanced it to correctly map responses back to whatever the client expects in responses. I'll try find time to port my patch to zebra.
Motivation
Zebra used to support both JSON-RPC 1.0 or 2.0 in respect to the
jsonrpc
field (non-existent in 1.0, mandatory with the2.0
value in 2.0).However, after the migration to jsonrpsee, this does not work anymore, and tools like
zcash-cli
stopped working withWe might want to restore that support. We already replace requests with
jsonrpc = "1.0"
(which is nonsensical, since the field did not exist in 1.0, but some tools like lightwalletd use it) tojsonrpc = "2.0"
using a middleware; it might be simple to make it addjsonrpc = "2.0"
if thejsonrpc
field is missing.Specifications
No response
Complex Code or Requirements
No response
Testing
No response
Related Work
No response
The text was updated successfully, but these errors were encountered: