parent
4e1de1fc59
commit
fad5a18548
@ -1,8 +0,0 @@
|
|||||||
Notable changes
|
|
||||||
===============
|
|
||||||
|
|
||||||
Updated RPCs
|
|
||||||
------------
|
|
||||||
|
|
||||||
- `listunspent` now includes `ancestorcount`, `ancestorsize`, and
|
|
||||||
`ancestorfees` for each transaction output that is still in the mempool.
|
|
@ -1,15 +0,0 @@
|
|||||||
Notable changes
|
|
||||||
===============
|
|
||||||
|
|
||||||
Updated RPCs
|
|
||||||
------------
|
|
||||||
|
|
||||||
- `lockunspent` now optionally takes a third parameter, `persistent`, which
|
|
||||||
causes the lock to be written persistently to the wallet database. This
|
|
||||||
allows UTXOs to remain locked even after node restarts or crashes.
|
|
||||||
|
|
||||||
GUI changes
|
|
||||||
-----------
|
|
||||||
|
|
||||||
- UTXOs which are locked via the GUI are now stored persistently in the
|
|
||||||
wallet database, so are not lost on node shutdown or crash.
|
|
@ -1,9 +0,0 @@
|
|||||||
Notable changes
|
|
||||||
===============
|
|
||||||
|
|
||||||
Rescan startup parameter removed
|
|
||||||
--------------------------------
|
|
||||||
|
|
||||||
The `-rescan` startup parameter has been removed. Wallets which require
|
|
||||||
rescanning due to corruption will still be rescanned on startup.
|
|
||||||
Otherwise, please use the `rescanblockchain` RPC to trigger a rescan.
|
|
Loading…
Reference in new issue