Handling non-confirmed funding transactions

[halseth]

Issue

During the current funding workflow, the responder should forget the channel if the funding transaction is not confirmed within a reasonable timeout. For lnd this timeout is currently set to 288 blocks.

The funder (initiator) of the channel cannot forget about the channel if the funding transaction is broadcast, since he has funded the transaction with coins. Therefore, we should make sure the money is returned to the funder's wallet.

Steps to completion:

• Prevent the funder from forgetting about the channel if the fundingManager gets restarted while waiting for the funding transaction to confirm. Currently, on restart it will launch a goroutine that will timeout after 288 blocks, but this should only be done for the channel responder.

• Determine how to reclaim the funds. We can either double spend the input to the funding transaction back into our wallet, or broadcast the commitment transaction and sweep the funds using CPFP.

Extra credits: We might also be able to bump the fee of the funding transaction to get it confirmed, but this would possibly need some more advanced scripting features, due to changing the amounts int the funding tx changes the txid, which the commitment tx relies on.

I'll try to resolve this issue.

[johng]

I've done the first part #514

[jemilsson]

It would be really neat to also be able to "cancel" the opening of a channel and reclaim the funds while the funding transaction is unconfirmed, even if the timout hasn't expired. This way you could avoid having to wait for the timeout.

[Roasbeef]

First portion fixed by #514.

[Crypt-iQ]

Hi if nobody is working on this, I'd like to take it

[Crypt-iQ]

Since I haven't gotten a reply I'll assume nobody is working on this and work on it myself

[halseth]

I believe @wpaulino has started on this one. On Wed, Jul 11, 2018 at 4:47pm, Eugene < notifications@github.com [notifications@github.com] > wrote: Since I haven't gotten a reply I'll assume nobody is working on this and work on it myself — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub [#386 (comment)] , or mute the thread [https://github.com/notifications/unsubscribe-auth/ADl15MEKau2-xao1LRCKVajwy9gAuqfyks5uFhAYgaJpZM4QBLco] .

[Crypt-iQ]

Ah ok I'll find a diff issue then

I'm really sorry I didn't give any news. I no longer work on this problem indeed.