-
Notifications
You must be signed in to change notification settings - Fork 85
Open
Labels
RPCChanges something with our JSON-RPC interfaceChanges something with our JSON-RPC interface
Description
I've made this issue so we can keep track of implemented and missing RPCs.
Whenever a new RPC is implemented, documented1 and/or we verify it is compliant2 with Bitcoin Core, ping me or Davidson so this can be updated.
I'll split the different RPC groups into separate comments.
Let's keep any discussion outside of this issue. This is here just so we can keep track of what needs to be done.
Footnotes
-
Documented means we have a documentation markdown file under
doc/rpc. ↩ -
Compliant means that Floresta's RPC is a superset of Bitcoin Core's RPC. It can be a superset because Floresta can return extra information on the RPC in addition to what Bitcoin Core returns (e.g. Floresta returns
root_hashesongetblockchaininfo) ↩
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
RPCChanges something with our JSON-RPC interfaceChanges something with our JSON-RPC interface