When rescanning, if the scanned transaction is already in the wallet, it is skipped. However, if someone sends a transaction, does not wait for confirmation, switches wallets, waits for a block that contains his original transaction, and switches wallets again, a rescan will leave his wallet transaction (which has no merkle branch, so no confirmations) untouched.
Update transactions already in the wallet when rescanning. #255
pull sipa wants to merge 1 commits into bitcoin:master from sipa:rescanupdate changing 3 files +4 −4-
sipa commented at 3:17 PM on May 22, 2011: member
-
1c528eeee9
Update transactions already in the wallet when rescanning.
When rescanning, if the scanned transaction is already in the wallet, it is skipped. However, if someone sends a transaction, does not wait for confirmation, switches wallets, waits for a block that contains his original transaction, and switches wallets again, a rescan will leave his wallet transaction (which has no merkle branch, so no confirmations) untouched.
- jgarzik referenced this in commit 7a234cdae5 on Jun 5, 2011
- jgarzik merged this on Jun 5, 2011
- jgarzik closed this on Jun 5, 2011
- dexX7 referenced this in commit bbd64c3f6f on Dec 21, 2014
- ptschip referenced this in commit a8d47be130 on Feb 1, 2017
- deadalnix referenced this in commit 4f577ca85b on May 10, 2017
- classesjack referenced this in commit ce37a40ea7 on Jan 2, 2018
- attilaaf referenced this in commit 7733d79ad9 on Jan 13, 2020
- rajarshimaitra referenced this in commit 7834e6ae05 on Aug 5, 2021
- DrahtBot locked this on Sep 8, 2021
Contributors