diff options
| author | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-03-22 21:14:34 +0100 |
|---|---|---|
| committer | Wladimir J. van der Laan <laanwj@gmail.com> | 2018-03-22 21:27:53 +0100 |
| commit | cead84b72d27517338ac3c49eaaed4db07352f41 (patch) | |
| tree | 58c224f38a14e6530d068ef86f01ce7f7888e3b7 /doc | |
| parent | 9552dfb1f6326b97ae05efb8af503eb7776a2d59 (diff) | |
| parent | d2527bd54e994747d9e24043c91d46c7219d46ac (diff) | |
| download | bitcoin-cead84b72d27517338ac3c49eaaed4db07352f41.tar.xz | |
Merge #11536: Rename account to label where appropriate
d2527bd Rename wallet_accounts.py test (Russell Yanofsky)
045eeb8 Rename account to label where appropriate (Russell Yanofsky)
Pull request description:
Rename account to label where appropriate
This change only updates strings and adds RPC aliases, but should simplify the implementation of address labels in https://github.com/bitcoin/bitcoin/pull/7729, by getting renaming out of the way and letting that change focus on semantics.
The difference between accounts and labels is that labels apply only to addresses, while accounts apply to both addresses and transactions (transactions have "from" and "to" accounts). The code associating accounts with transactions is clumsy and unreliable so we would like get rid of it.
---
There is a rebased version of #7729 atop this PR at https://github.com/ryanofsky/bitcoin/commits/pr/label, see https://github.com/bitcoin/bitcoin/pull/7729#issuecomment-338417139.
Tree-SHA512: b3f934e612922d6290f50137f8ba71ddfaea4485713c7d97e89400a8b73b09b254f9186dffa462c77f5847721f5af9852b5572ade5443d8ee95dd150b3edb7ff
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/release-notes.md | 10 |
1 files changed, 10 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md index a79012722f..b183ee0a59 100644 --- a/doc/release-notes.md +++ b/doc/release-notes.md @@ -63,6 +63,16 @@ RPC changes - The `createrawtransaction` RPC will now accept an array or dictionary (kept for compatibility) for the `outputs` parameter. This means the order of transaction outputs can be specified by the client. - The `fundrawtransaction` RPC will reject the previously deprecated `reserveChangeKey` option. +- Wallet `getnewaddress` and `addmultisigaddress` RPC `account` named + parameters have been renamed to `label` with no change in behavior. +- Wallet `getlabeladdress`, `getreceivedbylabel`, `listreceivedbylabel`, and + `setlabel` RPCs have been added to replace `getaccountaddress`, + `getreceivedbyaccount`, `listreceivedbyaccount`, and `setaccount` RPCs, + which are now deprecated. There is no change in behavior between the + new RPCs and deprecated RPCs. +- Wallet `listreceivedbylabel`, `listreceivedbyaccount` and `listunspent` RPCs + add `label` fields to returned JSON objects that previously only had + `account` fields. External wallet files --------------------- |