Open nondiremanuel opened 1 week ago
Looking into this, a send-to-self (multipath 0) output is also shown as unconfirmed (w/ a bitcoind/liana_connect backend, not tested on electrum), but should not if we follow the same idea i guess
Note: anyway only confirmed coins are added to the confirmed balance
sparrow behaviour when sending to self:
Looking into this, a send-to-self (multipath 0) output is also shown as unconfirmed (w/ a bitcoind/liana_connect backend, not tested on electrum), but should not if we follow the same idea i guess
Yes, I too believe the send to self should be consistent with the change management.
sparrow behaviour when sending to self:
* Balance is updated * Fee amount is unconfirmed unconfirmed
Electrum has the same behavior. It seems reasonable to me, we could replicate it.
Update after offline chat: let's keep this issue focused on the change management. We will tackle how to show the balance of self-transfers separately (see: https://github.com/wizardsardine/liana/issues/1378#issuecomment-2413350570)
During the testing phase of v7, we realized that using Liana Connect as backend, when sending a tx that doesn't spend the whole coin, the change is shown in the home screen as "Unconfirmed" until the tx is mined. This is not the expected behavior for change, since it should be considered already confirmed.
A first analysis was already performed. Quoting from the discussion we had: