Skip to content

RPC Implementation Tracker #839

@luisschwab

Description

@luisschwab

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

  1. Documented means we have a documentation markdown file under doc/rpc.

  2. 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_hashes on getblockchaininfo)

Metadata

Metadata

Assignees

No one assigned

    Labels

    RPCChanges something with our JSON-RPC interface

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions