61e96a69e4
Remove the addresses field from TransactionDetails.Output. It is assumed that the caller is able to deserialize the transaction and encode the output scripts to addresses, so this is unnecessary server overhead and conflicts with the current API philosophy of not duplicating data already included in another field. Since there is no additional data included for outputs not controlled by the wallet, remove the `mine` specifier from the Output message and replace it with an output index. Only include messages for controlled outputs, rather than creating messages for both controlled and uncontrolled outputs. Rename the repeated field from `outputs` to `credits` to be consistent with the `debits` field. Bump major API version as this is a breaking change. Closes #408. |
||
|---|---|---|
| .. | ||
| api.md | ||
| clientusage.md | ||
| README.md | ||
| serverchanges.md | ||
RPC Documentation
This project provides a gRPC server for Remote Procedure Call (RPC) access from other processes. This is intended to be the primary means by which users, through other client programs, interact with the wallet.
These documents cover the documentation for both consumers of the server and developers who must make changes or additions to the API and server implementation:
A legacy RPC server based on the JSON-RPC API of Bitcoin Core's wallet is also available, but documenting its usage is out of scope for these documents.