You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Watchonly forces to add a change address, even when consolidating funds (i.e. when sending out the MAX amount). This makes transaction have an one output with 0 sats. Therefore they are dropped as dust by the mempool.
Expected behaviour:
When max amount is selected, no change address are created and transactions have only one output.
Running watchonly 0.22 with LNbits 0.12
The text was updated successfully, but these errors were encountered:
jr21M
changed the title
[bug] When sending out MAX amount (consolidation), a 0 sats change output is always created. Therefore txs are dropped as dust!
[bug] When sending out MAX amount (consolidation), a 0 sats change output is created.
Feb 9, 2024
jr21M
changed the title
[bug] When sending out MAX amount (consolidation), a 0 sats change output is created.
[bug] When sending out MAX amount (consolidation), an undesired 0 sats change output is created.
Feb 9, 2024
I think there is something wrong with this bit in the payment.js. There should never be an outputs when the diffAmount is 0. But for some reason it nonetheless gets created.
if (!excludeChange) { const change = this.createChangeOutput() const diffAmount = this.selectedAmount - this.totalPayedAmount if (diffAmount >= this.DUST_LIMIT) { tx.outputs.push(change) }
Watchonly forces to add a change address, even when consolidating funds (i.e. when sending out the MAX amount). This makes transaction have an one output with 0 sats. Therefore they are dropped as dust by the mempool.
Expected behaviour:
When max amount is selected, no change address are created and transactions have only one output.
Running watchonly 0.22 with LNbits 0.12
The text was updated successfully, but these errors were encountered: