Tracking Issue for RPC integration

[hinto-janai]

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter.

What

This is the 3rd tracking issue surrounding the initial RPC implementation in cuprated.

The scope is:

• Practical input/output compatibility with monerod
• Compatibility with existing wallets
• Request/response call stack for each method
• Integration into cuprated i.e. RPC server on 18081/18089

Steps

• Internal changes
  • cuprated: CupratedRpcHandler, enable certain endpoints #450
• cuprated <-> monerod RPC input/output testing harness: /tests #357
• Method enabling
  • Required for wallet compatibility
    • TODO
  • Useful but optional
    • TODO
  • Everything else
    • TODO
• RPC server: cuprated: integrate RpcServer #423
• Documentation
  • user-book: add RPC section #451

Related

• Tracking Issue for RPC interface #183
• Tracking Issue for RPC handlers #244