mirror of
https://github.com/lightningnetwork/lnd.git
synced 2025-01-19 05:45:21 +01:00
e1e9de24df
Before this commit, we we were trying to sweep an anchor output, and that output was spent by someone else (not the sweeper), then we would report this back to the original resolver (allowing it to be cleaned up), and also remove the set of inputs spent by that transaction from the set we need to sweep. However, it's possible that if a user is spending unconfirmed outputs, then the wallet is holding onto an invalid transaction, as the outputs that were used as inputs have been double spent elsewhere. In this commit, we fix this issue by recursively removing all descendant transactions of our past sweeps that have an intersecting input set as the spending transaction. In cases where a user spent an unconfirmed output to funding a channel, and that output was a descendant of the now swept anchor output, the funds will now properly be marked as available. Fixes #6241 |
||
|---|---|---|
| .. | ||
| backend_mock_test.go | ||
| bucket_list.go | ||
| defaults_rpctest.go | ||
| defaults.go | ||
| fee_estimator_mock_test.go | ||
| interface.go | ||
| log.go | ||
| setup_test.go | ||
| store_mock.go | ||
| store_test.go | ||
| store.go | ||
| sweeper_test.go | ||
| sweeper.go | ||
| test_utils.go | ||
| tx_input_set_test.go | ||
| tx_input_set.go | ||
| txgenerator_test.go | ||
| txgenerator.go | ||
| walletsweep_test.go | ||
| walletsweep.go | ||
| weight_estimator_test.go | ||
| weight_estimator.go | ||