You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Merge bitcoin#23065: Allow UTXO locks to be written to wallet DB
d96b000 Make GUI UTXO lock/unlock persistent (Samuel Dobson)
077154f Add release note for lockunspent change (Samuel Dobson)
719ae92 Update lockunspent tests for lock persistence (Samuel Dobson)
f13fc16 Allow lockunspent to store the lock in the wallet DB (Samuel Dobson)
c527893 Allow locked UTXOs to be store in the wallet database (Samuel Dobson)
Pull request description:
Addresses and closesbitcoin#22368
As per that issue (and its predecessor bitcoin#14907), there seems to be some interest in allowing unspent outputs to be locked persistently. This PR does so by adding a flag to lockunspent to store the change in the wallet database. Defaults to false, so there is no change in default behaviour.
Edit: GUI commit changes default behaviour. UTXOs locked/unlocked via the GUI are now persistent.
ACKs for top commit:
achow101:
ACK d96b000
kristapsk:
ACK d96b000
lsilva01:
Tested ACK bitcoin@d96b000 on Ubuntu 20.04
prayank23:
ACK bitcoin@d96b000
Tree-SHA512: 957a5bbfe7f763036796906ccb1598feb6c14c5975838be1ba24a198840bf59e83233165cb112cebae909b6b25bf27275a4d7fa425923ef6c788ff671d7a89a8
{"vout", RPCArg::Type::NUM, RPCArg::Optional::NO, "The output number"},
2218
2219
},
2219
2220
},
2221
+
{"persistent", RPCArg::Type::BOOL, RPCArg::Default{false}, "Whether to write/erase this lock in the wallet database, or keep the change in memory only. Ignored for unlocking."},
0 commit comments