Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Funded a channel - txid for funding does not exists, causes issue when trying to close "channel" #19

Open
CaveRock opened this issue Apr 6, 2018 · 4 comments

Comments

@CaveRock
Copy link

CaveRock commented Apr 6, 2018

I have funded a channel, after not seeing any confirmations for quite a while, i tried to look at the funding tx on the main chain (or mempool) and it does not exist. Now the problem is that I cannot seem to close this "channel" and I doubt it will auto close after 144 blocks as there is no actual transaction.

Using rebroadcast did not make any difference, not sure what would happen when trying to rebroadcast a create channel tx when that same channel is now attempting to close itself.

Feels like if this could be resolved then the process would actually be straight forward, I reckon my app has now gotten itself into a weird state, should I re-install and use the previous seed?

@pm47
Copy link
Member

pm47 commented Apr 6, 2018

Can you paste the txid here?

Indeed the case where the tx never confirms isn't well handled currently, and channel will stay in CLOSING forever (but no funds are lost, your balance should be correct and your wallet should continue working ). Managing this is not trivial since the only way to be sure that it really will never confirm is to actually double spend it.

@CaveRock
Copy link
Author

CaveRock commented Apr 6, 2018

The channel ID: 0192d3d468d68fa3f30763ddbe108183d0bbf8fcf59e8e6227ab6c6e2
Funding txid: 1f638e296e6cab27628e9ef5fcf8bbd0838110bedd6307f3a38fd668d4d39201

Makes sense that there would be some trickyness to dealing with this scenario.

I think the main issue for my install right now is the validation rule that fires when I try create a new channel to the same node as the failed closing channel.
Is there a rule that removes that problematic channel after a set amount of time?

Thanks for your hard work, this is looking really cool. I am not too worried about the funds, just excited to get to play :)

@CaveRock
Copy link
Author

CaveRock commented Apr 6, 2018

In my case I don't think the tx ever went out onto the network, can't be found in mempool or on chain.

Seems like all records related to a funding tx whose txid never appears in the mempool need to be flushed, maybe there is a threshold of time without the txid appearing in mempool where this can happen? (sorry if my suggestion is over simplified, assume there is a lot of complexity going on under the hood)

@CaveRock
Copy link
Author

I've done the dns update and restarted as per the instructions in the thread relating to the non closing of a channel and the non return of funds.

My issue is a bit different, the channel funding transaction never hit the mempool, but the channel record was visible in the app. I tried to close the channel (Force) which changed the state to CLOSING (uncoop).
The problem for me I believe is that this channel will never close because it was never opened in the first place. My balance is correct, but I cannot create a new channel to the same node due to validation saying no duplicate channels allowed.

I just need to be able to flush these non channel records from the app, or do I need to re-install and re-initialize the seed?
Thanks

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants