zapunconfirmed RPC #3795

issue sipa opened this issue on March 4, 2014

sipa commented at 3:14 PM on March 4, 2014: member

Both salvagewallet and zapwallettxes are often much more rough than needed, when recovering from bad wallet state.

How about an RPC/option that only removes unconfirmed transactions from the wallet? Doing so wouldn't even require any rescan afterwards.
gmaxwell commented at 3:22 PM on March 4, 2014: contributor

Would we want to separate zapping unconfirmed spends and receives? They're fairly different cases.
sipa commented at 3:24 PM on March 4, 2014: member

May want to add that this is only feasible since we got rid of vfSpent in wallets. Before, you'd have to recompute all dependencies.
laanwj commented at 3:26 PM on March 4, 2014: member

@gmaxwell I suppose it would take a specific txid argument to zap, which could be either a spend or receive
laanwj commented at 10:36 AM on March 11, 2014: member

#3845 implements this functionality
laanwj added the label Wallet on May 13, 2014
laanwj commented at 11:13 AM on May 18, 2015: member

Following the discussion in #3845 there doesn't actually seem to be any demand for this feature, and implementing it correctly is difficult, there are lots of edge cases with regard to updating internal bookkeeping. Closing.
laanwj closed this on May 18, 2015
MarcoFalke locked this on Sep 8, 2021

Contributors

Labels