WIP: Add JSON-RPC interface documentation#14458
WIP: Add JSON-RPC interface documentation#14458promag wants to merge 1 commit intobitcoin:masterfrom
Conversation
|
Concept ACK |
|
Concept ACK 👍 |
|
Concept ACK |
jnewbery
left a comment
There was a problem hiding this comment.
Concept ACK. Looks good so far!
doc/JSON-RPC-interface.md
Outdated
doc/JSON-RPC-interface.md
Outdated
There was a problem hiding this comment.
Please rename this file json-rpc-interface.md to make it consistent with the other files.
There was a problem hiding this comment.
I think matching REST-interface.md is the intention - should it be lowercase too?
doc/JSON-RPC-interface.md
Outdated
There was a problem hiding this comment.
Increment header levels one level at a time. You might want to use mdl to check the Markdown formatting :-)
Reviewers, this pull request conflicts with the following ones:
If you consider this pull request important, please also help to review the conflicting pull requests. Ideally, start with the one that should be merged first. |
|
@harding might want to have a look here as this adds technical documentation |
880be1c to
29eb75d
Compare
|
Rebased, still WIP though. One way to move this forward is to improve in smaller PR's. |
|
Concept ACK on general documentation of how to use the RPC, as well as maybe providing more context for specific issues. However, I'm worried that maintaining this list of |
|
Suggestion: the document could mention that Bitcoin Core allows money values to be passed as either a float or a string. That's an unexpected feature, but one that can be quite nice for users of JSON implementations that aren't good at high-precision. |
5a5ea93 Doc: add information about security to the JSON-RPC doc (David A. Harding) Pull request description: This documents some information about using the RPC interface securely, as suggested in bitcoin-core/bitcoincore.org#637 by @luke-jr and @TheBlueMatt. I think it should fit in well with #14458, but is not dependent on it (and shouldn't have any significant merge conflicts with it). Tree-SHA512: e09d82c3029ed17a8bcf50722ea25a8c6c514731f3bce01908cbb6fe48bc96a3068a025beabebc602d18e1bc0dc3f2602848abc05dca1d3efe2a988ee50068c0
Sjors
left a comment
There was a problem hiding this comment.
ACK. I suggest we remove the "todo" comments, merge this and improve it after the 0.18 release.
29eb75d to
fa90c0c
Compare
|
Rebased and removed configurations section, kind of agree with @Sjors #14458 (comment). What left isn't worth I think, so closing. |
…RPC doc 5a5ea93 Doc: add information about security to the JSON-RPC doc (David A. Harding) Pull request description: This documents some information about using the RPC interface securely, as suggested in bitcoin-core/bitcoincore.org#637 by @luke-jr and @TheBlueMatt. I think it should fit in well with bitcoin#14458, but is not dependent on it (and shouldn't have any significant merge conflicts with it). Tree-SHA512: e09d82c3029ed17a8bcf50722ea25a8c6c514731f3bce01908cbb6fe48bc96a3068a025beabebc602d18e1bc0dc3f2602848abc05dca1d3efe2a988ee50068c0
…RPC doc 5a5ea93 Doc: add information about security to the JSON-RPC doc (David A. Harding) Pull request description: This documents some information about using the RPC interface securely, as suggested in bitcoin-core/bitcoincore.org#637 by @luke-jr and @TheBlueMatt. I think it should fit in well with bitcoin#14458, but is not dependent on it (and shouldn't have any significant merge conflicts with it). Tree-SHA512: e09d82c3029ed17a8bcf50722ea25a8c6c514731f3bce01908cbb6fe48bc96a3068a025beabebc602d18e1bc0dc3f2602848abc05dca1d3efe2a988ee50068c0
…RPC doc 5a5ea93 Doc: add information about security to the JSON-RPC doc (David A. Harding) Pull request description: This documents some information about using the RPC interface securely, as suggested in bitcoin-core/bitcoincore.org#637 by @luke-jr and @TheBlueMatt. I think it should fit in well with bitcoin#14458, but is not dependent on it (and shouldn't have any significant merge conflicts with it). Tree-SHA512: e09d82c3029ed17a8bcf50722ea25a8c6c514731f3bce01908cbb6fe48bc96a3068a025beabebc602d18e1bc0dc3f2602848abc05dca1d3efe2a988ee50068c0
This is poorly written and structured but I want to know if it makes sense.
The idea is not to copy
-helpoutputs.Closes #14448.
Follow ups: