Update README for gRPC changes.
While here, remove mention of btcgui and add a disclaimer that total compatibility with the JSON-RPC server cannot be achieved.
This commit is contained in:
parent
102cd553c5
commit
97963b47ce
1 changed files with 19 additions and 17 deletions
36
README.md
36
README.md
|
@ -34,11 +34,25 @@ can be found [here](https://github.com/btcsuite/btcd). An alternative
|
||||||
SPV mode that is compatible with btcd and Bitcoin Core is planned for
|
SPV mode that is compatible with btcd and Bitcoin Core is planned for
|
||||||
a future release.
|
a future release.
|
||||||
|
|
||||||
No release-ready graphical frontends currently exist, however the
|
Wallet clients can use one of two RPC servers:
|
||||||
proof-of-concept [btcgui](https://github.com/btcsuite/btcgui) project
|
|
||||||
shows some of the possibilities of btcwallet. In the coming months a
|
1. A legacy JSON-RPC server mostly compatible with Bitcoin Core
|
||||||
new stable RPC API is planned, at which point a high quality graphical
|
|
||||||
frontend can be finished.
|
The JSON-RPC server exists to ease the migration of wallet applications
|
||||||
|
from Core, but complete compatibility is not guaranteed. Some portions of
|
||||||
|
the API (and especially accounts) have to work differently due to other
|
||||||
|
design decisions (mostly due to BIP0044). However, if you find a
|
||||||
|
compatibility issue and feel that it could be reasonably supported, please
|
||||||
|
report an issue. This server is enabled by default.
|
||||||
|
|
||||||
|
2. An experimental gRPC server
|
||||||
|
|
||||||
|
The gRPC server uses a new API built for btcwallet, but the API is not
|
||||||
|
stabilized and the server is feature gated behind a config option
|
||||||
|
(`--experimentalrpclisten`). If you don't mind applications breaking due
|
||||||
|
to API changes, don't want to deal with issues of the legacy API, or need
|
||||||
|
notifications for changes to the wallet, this is the RPC server to use.
|
||||||
|
The gRPC server is documented [here](./rpc/documentation/README.md).
|
||||||
|
|
||||||
Mainnet support is currently disabled by default. Use of btcwallet on
|
Mainnet support is currently disabled by default. Use of btcwallet on
|
||||||
mainnet requires passing the `--mainnet` flag on the command line or
|
mainnet requires passing the `--mainnet` flag on the command line or
|
||||||
|
@ -121,18 +135,6 @@ $ $EDITOR ~/.btcd/btcd.conf
|
||||||
$ $EDITOR ~/.btcwallet/btcwallet.conf
|
$ $EDITOR ~/.btcwallet/btcwallet.conf
|
||||||
```
|
```
|
||||||
|
|
||||||
## Client Usage
|
|
||||||
|
|
||||||
Clients wishing to use btcwallet are recommended to connect to the
|
|
||||||
`ws` endpoint over a websocket connection. Messages sent to btcwallet
|
|
||||||
over this websocket are expected to follow the standard Bitcoin JSON
|
|
||||||
API (partially documented
|
|
||||||
[here](https://en.bitcoin.it/wiki/Original_Bitcoin_client/API_Calls_list)).
|
|
||||||
Websocket connections also enable additional API extensions and
|
|
||||||
JSON-RPC notifications (currently undocumented). The btcd packages
|
|
||||||
`btcjson` and `btcws` provide types and functions for creating and
|
|
||||||
JSON (un)marshaling these requests and notifications.
|
|
||||||
|
|
||||||
## Issue Tracker
|
## Issue Tracker
|
||||||
|
|
||||||
The [integrated github issue tracker](https://github.com/btcsuite/btcwallet/issues)
|
The [integrated github issue tracker](https://github.com/btcsuite/btcwallet/issues)
|
||||||
|
|
Loading…
Reference in a new issue