Unable to broadcast sweep tx

[stridentbean]

Background

Lnd is crashing and restarting (because docker is set to restart). This user thinks he may have force closed a channel at the time this error started. There may have been some dust in the channel at that time.

Your environment

• lncli version 0.5.1-beta commit=v0.5.1-beta
• Linux lnd 4.14.70-v7+ Fixing some README typos #2 SMP Wed Sep 19 07:49:26 UTC 2018 armv7l Linux
• bitcoind: 0.17.0
• bitcoind and lnd are running in docker containers on a raspberry pi 3b+

Steps to reproduce

Unsure how to reproduce on other devices, but lnd logs on warn level produce the following snippet. We can turn up logging if that is helpful. I can also include the omitted txIn/txOut data if that helps.

2019-01-21T15:25:28Z lnd UNKNOWN[5919] 2019-01-21 15:25:28.941 [ERR] UTXN: unable to broadcast sweep tx: -26: dust (code 64), (*wire.MsgTx)(0x1863780)({
2019-01-21T15:25:28Z lnd UNKNOWN[5919] Version: (int32) 2,
2019-01-21T15:25:28Z lnd UNKNOWN[5919] TxIn: ([]*wire.TxIn) (len=1 cap=1) {
**OMITTED**
2019-01-21T15:25:28Z lnd UNKNOWN[5919] TxOut: ([]*wire.TxOut) (len=1 cap=1) {
**OMITTED**
2019-01-21T15:25:28Z lnd UNKNOWN[5919] LockTime: (uint32) 559041
2019-01-21T15:25:28Z lnd UNKNOWN[5919] })
2019-01-21T15:25:28Z lnd UNKNOWN[5919] 
2019-01-21T15:25:28Z lnd UNKNOWN[5919] 2019-01-21 15:25:28.941 [ERR] UTXN: Failed to re-register for kindergarten sweep transaction at height=559041: -26: dust (code 64)
2019-01-21T15:25:28Z lnd UNKNOWN[5919] 2019-01-21 15:25:28.957 [ERR] UTXN: Failed to regraduate outputs at height=559041: -26: dust (code 64)
2019-01-21T15:25:28Z lnd UNKNOWN[5919] 2019-01-21 15:25:28.958 [ERR] SRVR: unable to start server: -26: dust (code 64)

Expected behaviour

Lnd should boot up normally and not crash.

Actual behaviour

Lnd fails to start and reboots because docker is set to restart automatically.

[Roasbeef]

The output is too small to sweep (it's dust). If you upgrade to master, then the new sweeper sub-system will take care of this, and bundle it with larger outputs when it becomes economical to sweep.

[capacitynetwork]

bundle it with larger outputs when it becomes economical to sweep.

@Roasbeef I upgraded to master 4 days ago, it fixed this error, but tx still has not been bundled or swept. Dust tx for 104 after channel close.

I have closed and opened many channels since this time. Under what situation will this dust be put to transaction and confirmed?

[halseth]

When fees are low.

[capacitynetwork]

@halseth fees have been low, it's now 11-12 days later and still no change

[halseth]

It will try to bundle it with other transactions if it can gain anything from it.

[capacitynetwork]

and if it cannot, is there a way to force this dust to be utilized on some way?

[wpaulino]

No since the output you're attempting to sweep is not under control of your wallet yet.