Walletwasabi: Queued amount of coins is not updating when using RBF to increase an unconfirmed queued UTXO's tx fee.

[omnifinn]

General Description

I sent a single UTXO from Bitcoin Core version v0.19.0.1 (64-bit) to Wasabi 1.1.10.0 directly using a very low fee (below 1sat/vb) resulting it not confirming. I then used RBF to increase the fee twice to get it confirmed faster which worked great apart from the fact that on the wasabiwallet GUI of the coinjoin tab the queued amount is now exactly tripled compared to the actual single UTXO I have queued.

How To Reproduce?

1. Go to 'Wasabi 1.1.10.0'
2. Click on 'receive, create a new address, copy address on clipboard'
3. Go to 'Bitcoin Core version v0.19.0.1 (64-bit)', click send and paste the address from clipboard
4. Set the fee to 0.00001000 per kilobyte (somehow this resulted in a lower fee than 1sat/b), enable RBF and click send
5. Go to transactions in Bitcoin Core and right click on the transaction you just made and click "increase transaction fee" and confirm the new transaction
6. Go to wasabi and queue the new transaction for a coinjoin
7. Repeat step 5
8. Repeat step 6
9. You should now see the amount queued tripled compared to what you have actually queued

[MaxHillebrand]

Thanks for the detailed report @omnifinn!
@omnifinn notice that you can only register an unconfirmed coin if it's parent is a wasabi coinjoin, I believe, but it might be segwit only.

@lontivero I believe you worked on that RBF logic, can you see what might cause the wrong handling?

[omnifinn]

That's a good point @MaxHillebrand ! I am aware of this. I normally use the queue anyway to be able to go on with my day. Queing for the registering if you will. That's why this behaviour struck me odd. I would assume it's not a critical bug but a good thing to fix to reduce UI confusion.

[lontivero]

@omnifinn thanks your this report. I suspect this is a UI problem, does the problem persist after you restart wasabi?

[omnifinn]

@lontivero After restart it works as it should, so looks like you are right about it being an UI issue.

[nopara73]

Thanks for the report, it's easily reproducible. While you cannot register non-Wasabi-cj unconfirmed coins, you should be able to enqueue it and RBF should not result in strange behavior, so there's definitely a bug there.

[stale[bot]]

This has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[nopara73]

bump

[stale[bot]]

This has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[nopara73]

bump

[stale[bot]]

This has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[nopara73]

bump