-
Notifications
You must be signed in to change notification settings - Fork 406
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Bug: Addresses affected by descendant transactions are not notified on transaction replacement #1028
Labels
bug
Something isn't working
Comments
Many thanks for reporting this issue! |
I tried to reproduce the issue on Regtest with Sparrow 1.8.5 (built from source), but it seems to fail to start - with the following exception:
@craigraw could you please take a look? |
I'll try to reproduce on testnet. |
See sparrowwallet/sparrow#1385. You can simply run latest HEAD to avoid this. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
If you watch https://www.youtube.com/watch?v=pWmgu5eA4y4 to 9m 51s, you will see Sparrow reflects an incorrect state of the wallet. This is caused by the lack of all the correct notifications from Electrs - all addresses affected by the replacement of a transaction (removing it from this wallet) are not notified. The addresses that are not notified relate to child transactions that spend the (now removed) output of the replaced transaction.
I've reproduced the scenario using DEBUG logging in Sparrow, which funded address
/0/2
in the Alice wallet with the first transaction, and then spent from/0/2
and/1/0
addresses to create the child transaction to the third (Bob) wallet. On broadcasting the RBF transaction from the first (Evil RBFer) wallet, the Alice wallet was notified of changes to/0/1
and/0/2
, but not/1/0
.The text was updated successfully, but these errors were encountered: