--- Log opened Sat Aug 14 00:00:38 2021
02:28 -!- max302 [~max302@128.127.205.227] has joined #c-lightning
02:29 < max302> hello all, i've been having an extremely weird issue following a restore from backup and I would need a bit of dev assistance,  not sure if my extreme edge case deserves an issue on github, does anybody have a few minutes?
02:33 < cdecker[m]> What's the issue?
02:38 < max302> I have two channels marked AWAITING_UNILATERAL, both of which the peers for are not connected and will not reconnect if I try it manually. For one of those peers, the funding TX has gone through and the other side (1ML) is still showing the channel as open, for the other, the tx has not going through. I read about similar cases on github where
02:38 < max302> dev-forget-channel was recommended for cases where the funding tx has not gone through, but obviously I am very reticent to try this on a channel that has been properly funded
02:38 < max302> I can provide log output, but I don't want to spam the chat with this. Do you mind if I send it in a DM?
02:41 < cdecker[m]> Both states are pretty normal, if you share the funding txid we can likely check what the current status is. For the unconfirmed channel I'd recommend double spending the funding tx first before forgetting it
02:43 < max302> Keep in mind the channels have been in this state for like 6 months... following my recovery from backup, most channels closed out relatively quickly due to inconsistent state. 
02:43 < max302> The one that is still considered open: 9605917133fa99c5a3c6b7459c2cba562bb775410f0c731e217ee899d14d85ba
02:43 < max302> The one that never went through: 358d48ad8ce4d677111c40fe274a122562b02206e975b70280c58d4cf0ef016c
02:43 < cdecker[m]> Wait, why should the channels close after recovery? Did you restore an old backup?
02:44 < max302> yes, this is what what cause this mess in the first place. This is entirely on me, it was a last ditch effort to recover funds after a major fuckup. 
02:45 < cdecker[m]> Ok, just making sure :-) Hope the peers where well-behaved and returned most of your funds
02:48 < max302> most, yes, but the 1ML channel is the one that I find weird, it is still properly monitoring my node and accord to the website the channel with them is still open: https://1ml.com/channel/737619470234157057
02:54 < max302> So I guess if I can boil it down, right now I have two concerns, first is finding a way to close out the channel with 1ML that should be closed, and the other is forgetting the other channel while making sure that I am not screwing up c-lightning's internal wallet and losing funds in the process.
02:54 < cdecker[m]> Yeah, the first one is still active (no closing TX yet), while the second one is still unconfirmed.
02:54 < cdecker[m]> Can you share `lightning-cli listtransactions` in a paste? That allows us to see if the second one has any chance of ever confirming
02:58 < max302> I will send in a DM just to not dox myself further if you don't mind :P
02:59 < max302> too lazy to log in... watch out its a burn after reading paste
02:59 < max302> https://pastebin.com/w8VNTTih
03:00 < cdecker[m]> Hehe, seems some autoomated bot scraped that before I could click
03:00 < max302> doh
03:04 < max302> https://pastebin.com/tek8NjcM
03:05 < cdecker[m]> Yeah, no. Some IRC clients will scrape links as soon as they are posted. DM is probably the way to go
03:05 < max302> ok give me a moment
03:12 < max302> sent
03:15 < cdecker[m]> Am I correct in thinking that 358d48 was opened by the peer? (you don't have the funding transactons for some reason)
03:17 < max302> nope, this was an attempt at an outbound
03:19 < max302> no funding transaction = safe to dev-forget, correct?
03:20 < cdecker[m]> Sort of, still a bit unsure why we don't have a copy of the tx in the DB
03:21 < cdecker[m]> Do a dev-rescan-outputs, then a `withdraw [another_address] all` and that should double spend any pending funding txs, just for safety
03:25 < max302> {
03:25 < max302>    "code": 301,
03:25 < max302>    "message": "Could not afford all using all 0 available UTXOs: all 
03:26 < cdecker[m]> That is after a dev-rescan-outputs? Ok, then the 358d48 can never confirm since the funding was already double-spent
03:27 < max302> yes, dev-rescan-outputs gave me a list of txids, but non with a change from oldstate to newstate
03:28 < cdecker[m]> Which leaves us with 96059, which we should likely wait for the peer to close, since otherwise we wouldn't have moved into awaiting unilateral
03:28 < cdecker[m]> It's not safe to force close that one, since we obviously have had dataloss, and the peer told us about it before disconnecting from us
03:28 < max302>  it's been a few months now... likely a problem on their end means that its unlikely to close unless they force it
03:29 < cdecker[m]> Yep, lemme check who the peer is
03:30 < max302> 1ML, I can try sending them a message
03:30 < cdecker[m]> Yeah, that's 1ml itself, so they'll definitely retaliate if you cheat by force-closing after dataloss
03:30 < cdecker[m]> Best thing to do is to reach out to them and ask to close
03:31 < max302> ok, alright! So I'll reload my docker image with dev tools, forget the first one and contact 1ML. Christian you are a godsend. When I finally get my stuff sorted out I'd love to send you some sats for your help.
03:32 < cdecker[m]> Glad we could solve at least some of the issues, no need for sats, just happy to help ^^
03:34 < max302> on a weekend no less! Really appreciated!
03:35 < cdecker[m]> No problem, keep us posted on your progress ^^
03:43 -!- max302 [~max302@128.127.205.227] has quit [Quit: Ping timeout (120 seconds)]
03:44 -!- max302 [~max302@128.127.205.227] has joined #c-lightning
03:45 < max302> oh no
03:46 < max302> just had a major bruh moment and forgot the wrong channel lmao
03:48 < max302> "we will not track the funds in the channel" means that if the other party closes and there is a on-chain tx lightningd won't track it, correct? Even after a scan?
03:54 < max302> what a disaster lol... this is why I should never try to fix things before eating breakfast lol
03:55 < cdecker[m]> Hm, depends on the channel options, if it had a static close key it'll go to your on-chain wallet
03:58 < max302> sent them a message, we will see how it goes... thanks again!
04:00 -!- max302 [~max302@128.127.205.227] has quit [Quit: Client closed]
11:54 -!- FelixWeis [sid154231@id-154231.stonehaven.irccloud.com] has quit [Ping timeout: 252 seconds]
12:07 -!- FelixWeis [sid154231@id-154231.stonehaven.irccloud.com] has joined #c-lightning
16:43 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
17:46 -!- jarthur [~jarthur@2603-8080-1540-002d-b485-c402-7731-8036.res6.spectrum.com] has quit [Quit: jarthur]
18:17 -!- reallll [~belcher@user/belcher] has joined #c-lightning
18:21 -!- belcher_ [~belcher@user/belcher] has quit [Ping timeout: 248 seconds]
19:15 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
19:37 -!- jarthur [~jarthur@cpe-70-114-198-37.austin.res.rr.com] has joined #c-lightning
19:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
20:02 -!- aechu [~major@gateway/tor-sasl/major] has quit [Ping timeout: 244 seconds]
20:06 -!- aechu [~major@gateway/tor-sasl/major] has joined #c-lightning
21:29 -!- jarthur [~jarthur@cpe-70-114-198-37.austin.res.rr.com] has quit [Ping timeout: 248 seconds]
21:31 -!- jarthur [~jarthur@2603-8080-1540-002d-519b-3f89-f896-0f8f.res6.spectrum.com] has joined #c-lightning
23:56 -!- reallll is now known as belcher
--- Log closed Sun Aug 15 00:00:39 2021