Changeset View
Changeset View
Standalone View
Standalone View
doc/release-notes.md
Show All 10 Lines | - Bare multisig outputs to our keys are no longer automatically treated as | ||||
incoming payments. As this feature was only available for multisig outputs for | incoming payments. As this feature was only available for multisig outputs for | ||||
which you had all private keys in your wallet, there was generally no use for | which you had all private keys in your wallet, there was generally no use for | ||||
them compared to single-key schemes. Furthermore, no address format for such | them compared to single-key schemes. Furthermore, no address format for such | ||||
outputs is defined, and wallet software can't easily send to it. These outputs | outputs is defined, and wallet software can't easily send to it. These outputs | ||||
will no longer show up in `listtransactions`, `listunspent`, or contribute to | will no longer show up in `listtransactions`, `listunspent`, or contribute to | ||||
your balance, unless they are explicitly watched (using `importaddress` or | your balance, unless they are explicitly watched (using `importaddress` or | ||||
`importmulti` with hex script argument). `signrawtransaction*` also still | `importmulti` with hex script argument). `signrawtransaction*` also still | ||||
works for them. | works for them. | ||||
- The RPC `createwallet` now has an optional `blank` argument that can be used | |||||
to create a blank wallet. Blank wallets do not have any keys or HD seed. | |||||
They cannot be opened in software older than 0.20.11 | |||||
Once a blank wallet has a HD seed set (by using `sethdseed`) or private keys, | |||||
scripts, addresses, and other watch only things have been imported, the wallet | |||||
is no longer blank and can be opened in 0.20.x. | |||||
Encrypting a blank wallet will also set a HD seed for it. |