[RPC][Backport] JSON-RPC 2.0 when Client requests #2937
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Liquid369
force-pushed
the
2024_json_rpc_2_0
branch
from
694ad6f to
beebb56
Compare
Liquid369
force-pushed
the
2024_json_rpc_2_0
branch
from
0ef99ef to
ca2ba91
Compare
Liquid369
force-pushed
the
2024_json_rpc_2_0
branch
from
ca2ba91 to
f792c31
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PIVX Core is currently working with a mix of 1.0, 1.1 and 2.0 behaviors for the JSON RPC server.
@Duddino was having issues with a rust json rpc library interfacing with our daemon because of the responses not aligning to the JSON-RPC 2.0 standard behaviors. This backport was identified and has been applied to ensure JSON-RPC 2.0 compatibility.
Behavior changes:
"error"or"result"not both