--- Log opened Thu Jan 10 00:00:16 2019 00:28 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has joined #c-lightning 00:59 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 00:59 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 01:03 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 01:03 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 01:39 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 01:39 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 01:43 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 01:43 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 01:54 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 01:54 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 01:58 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 01:58 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 02:07 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 02:14 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 02:14 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 02:23 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 02:23 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 02:36 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 02:41 < bitonic-cjp> I have two channels I tried to close unilaterally, and they are stuck in 'status': ['AWAITING_UNILATERAL:Attempting to reconnect'] 02:41 < bitonic-cjp> At least one of them never had its funding tx confirmed though (the funding tx is invalid). 02:49 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 02:49 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 02:53 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 02:54 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 02:55 < bitonic-cjp> hmm, both 'funding_txid's aren't in the blockchain. Funny. 02:59 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 02:59 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 03:18 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 03:19 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 03:29 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 03:29 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 03:33 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 03:34 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 03:39 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 03:39 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 03:53 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 03:53 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 04:14 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 04:14 -!- deusexbeer [~deusexbee@093-092-176-030-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 04:14 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 04:23 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 04:23 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 04:49 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 04:49 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 04:58 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 04:59 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 05:34 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 05:34 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 05:34 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 05:38 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 05:38 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 05:44 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 05:44 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 05:53 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 05:54 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 06:19 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 06:19 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 06:23 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 06:24 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 06:34 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning 06:44 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 06:44 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 06:48 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 06:49 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 06:53 < bitonic-cjp> I managed to trace all my funds, there's just one bogus transaction. 06:54 < bitonic-cjp> I recently opened a new channel, and its funding tx doesn't confirm because one of its inputs is from a non-existing tx. 06:55 < bitonic-cjp> The incorrect TxID is 11da96f85c7bca4be94f9eb7a987dbd5a6a74c5278c04cfec2877b87a03d4852. 06:55 < bitonic-cjp> I believe it should have been 64c13b639391ae273915a2e902624f7c2a2d9ddbed046320a540a9bf2e72aea8. 06:57 < bitonic-cjp> The one I think it should have been (which is the only output with sufficient funds) is the change address of a previous funding tx. 06:58 < bitonic-cjp> I cannot find either txid in the transactions table of the node. 06:59 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 06:59 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 07:09 < bitonic-cjp> Other weirdness: it used two inputs for the funding tx, while one of them would have been big enough on its own to create the channel. Maybe a quirk from C-Lightning's utxo selection algo? 07:10 < bitonic-cjp> This is becoming too much effort. I'm about to throw away testBTC. 07:18 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 07:18 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 07:22 < bitonic-cjp> Hmm, the incorrect TxID is also listed as the funding tx of another channel (which is also in a dysfunctional state obviously). 07:26 < bitonic-cjp> ...but it's not in the transactions table. (why????) 07:27 < bitonic-cjp> So maybe it's not so much an incorrect TxID, it's just a tx in the chain that somehow got lost. 07:28 < bitonic-cjp> It never confirmed (for reasons I can't figure out since I don't have the tx itself) and it isn't in the transactions table. 07:30 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning 07:34 < bitonic-cjp> wow I found the old tx in the logs :-) 07:38 < bitonic-cjp> yay for putting raw transaction data in the logs, and yay for me never throwing away log data (this was from March 2018). 07:39 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 07:39 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 07:48 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 07:49 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 08:01 < ctrlbreak> Guys, how do I get into the slack channel for clightning? 08:02 < ctrlbreak> I need to speak with either cdecker or rusty? 08:03 < bitonic-cjp> So what seems to have happened: the previous channel fund tx never got confirmed because of too low fees. Still, the last channel fund tx used that fund tx's change as input, so it didn't confirm either. 08:04 < bitonic-cjp> I don't know why the previous channel's fund tx got lost from the database. It was in march 2018, so it was an old version anyway. 08:06 < bitonic-cjp> Lesson learned: at least *never accept* a situation where a channel is stuck. Always resolve the situation before creating other channels. 08:14 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 08:20 < bitonic-cjp> Other lesson learned (TAKE NOTE!): maybe C-Lightning shouldn't throw away data of transactions that are completely spent, if they aren't also confirmed. 08:23 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 08:29 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has quit [Quit: Leaving] 08:48 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 08:52 <@cdecker> bitonic-cjp: we want to keep all transactions we generate in the `transactions` table so we can replay them if necessary. If there is a transaction that doesn't get saved there we should definitely do so 08:55 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 08:59 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 08:59 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 09:03 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 09:04 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 09:50 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning 09:54 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 09:54 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 09:58 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 09:58 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 10:00 -!- deusexbeer [~deusexbee@093-092-176-030-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 268 seconds] 10:18 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection] 10:20 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning 11:04 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 11:04 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 11:08 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 11:09 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 11:21 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection] 11:22 < blockstream_bot> [George Vaccaro, Blockstream] @rusty thank you, will do. 11:22 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning 11:27 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection] 11:28 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning 11:36 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection] 11:37 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning 11:44 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 11:44 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 11:48 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 11:48 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 11:49 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Remote host closed the connection] 11:54 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning 11:54 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 11:54 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 11:55 -!- grubles_ [~grubles_@unaffiliated/grubles] has quit [Client Quit] 11:58 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 11:58 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 12:04 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 12:04 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 12:08 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 12:09 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 12:28 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 12:32 -!- billybigpotatoes [~billybigp@2a02:c7f:c21f:8100:1c08:34e:f30b:3b06] has joined #c-lightning 12:49 < ctrlbreak> oh oh... speghettios. 12:49 < ctrlbreak> So, a little while ago, I opened a new channel on my CL node. 12:49 < ctrlbreak> It now has 5 confirmations. 12:50 < ctrlbreak> listfunds is empty and not showing my change balance? 12:53 < ctrlbreak> dev-listaddrs does indeed have the change address at index 265... and the address has my balance. 12:54 < ctrlbreak> However.... I appear to have two additional keyidx after that one? I do recall attempting to open 2 additional channels after the first, and they failed, and I THEN remembered, well duh, your other channel needs to confirm on chain first before you can spend the balance :-S 12:55 < ctrlbreak> So... any idea how I can correct this situation where CL thinks I'm broke :-P 12:55 < ctrlbreak> ? 13:00 < ctrlbreak> Hmmm... think I found the issue. CL let me attempt to open the 2nd channel where I probably wouldn't have been able to? 1st channel was still pending 1st confirmation and would have chewed up all my UTXO.... but it looks like it attempted to anyway? 13:00 < ctrlbreak> "Funding channel: offered, now waiting for accept_channel" 13:01 < ctrlbreak> Anyone know how to... umm.. safely... abort this proposed channel opening such that CL fixes it's accounting and recognizes I have funds? 13:02 < billybigpotatoes> I wish I could help, but I'm quite certain I know less than you. It was nothing short of a miracle that I actually managed to get everything up and running. 13:03 < ctrlbreak> Hehe... no worries. All of this is quite complicated at the moment! 13:04 < billybigpotatoes> Yes it certainly is! Good fun learning though, I like little challenges at the end of the day. 13:05 < ctrlbreak> You on testnet, mainnet, or both Billy? 13:05 < billybigpotatoes> Mainnet. I've probably got about £5 left in my wallets somewhere, but when I try and withdraw all it tells me insufficient funds. But I'm pretty sure I haven't miscounted. Maybe I have. I don't really understand the listfunds output. 13:06 < ctrlbreak> ahhh. 13:07 < billybigpotatoes> Glad I've done it all though. Lightning was just the motivation I needed to set up my own bitcoin node at last. 13:07 < ctrlbreak> hehehe... 13:07 < ctrlbreak> I'll help ya. 13:07 < ctrlbreak> So, you have a balance in your CL wallet you want to withdraw? 13:08 < billybigpotatoes> I'll happily post the listfunds output here if you think you can help. I presume it is safe to do so. God knows I've tried to find where the private keys are. hsm_secret>? what is that.... 13:09 < ctrlbreak> also, the listfunds output will show you funds available in the wallet, as well as your balances for any active channels you have open. 13:09 < ctrlbreak> Send me the listfunds output privately so as to not flood the channel. 13:09 < billybigpotatoes> So here is a tiny snippet of my listfunds output - will send it privately sure - I'm a novice on irc too so give me a few moments. 13:10 < ctrlbreak> no worryes. 13:39 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Quit: farmerwampum] 13:39 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 13:43 -!- farmerwampum [~farmerwam@162.219.178.186] has quit [Client Quit] 13:43 -!- farmerwampum [~farmerwam@162.219.178.186] has joined #c-lightning 14:05 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection] 14:15 <@niftynei> this feels like a dumb question but how do you see the manpage entries for the cli commands? 14:15 <@niftynei> like i know where they are, but how do you invoke `man` to display them? 14:25 < ctrlbreak> I don't *think* there are man pages.. 14:25 < ctrlbreak> ./lightning-cli help 14:30 < ctrlbreak> Ahhh... resolved my issue from earlier it appears. My peer with the hung channel state: "Funding channel: offered, now waiting for accept_channel" ?? 14:31 < ctrlbreak> Yeah... just calling a CLOSE with their pubkey immediately resolved the accounting issue and my wallet change address and balance is now reflected as confirmed in the LISTFUNDS output. 14:31 < ctrlbreak> (for anyone wondering) 14:31 -!- billybigpotatoes [~billybigp@2a02:c7f:c21f:8100:1c08:34e:f30b:3b06] has quit [Quit: Leaving] 14:33 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 14:38 < nothingmuch> niftynei: IIRC the ppa package installs manpages for the subcommands which will bring up 14:39 < nothingmuch> niftynei: looking at the code, lightning-cli seems to exec 14:39 < nothingmuch> https://github.com/ElementsProject/lightning/blob/master/cli/lightning-cli.c#L258 15:08 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 15:12 < molz> interesting, thanks, nothingmuch 15:13 < molz> man lightning-listfunds 15:14 < molz> SEE ALSO 15:14 < molz> lightning-newaddr(7), lightning-fundchannel(7), lightning-withdraw(7) 15:15 < molz> but that's it, it's not complete 15:16 < ctrlbreak> wow... thanks for letting me know about that! 15:18 <@niftynei> hmm `man lightning-listfunds` doesn't work for me, i get `No manual entry for lightning-listfunds` 15:18 <@niftynei> seems like a problem on my end tho 15:25 <@niftynei> ok so you have to run `make install` to get them registered which makes sense 15:26 <@niftynei> (only relevant if you build from source) 15:33 < nothingmuch> yeah i never did make install or installed from ppa, i just remembered cdecker mentioned it in one of his talks 15:33 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 15:37 < rusty> ctrlbreak: pong... 15:37 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Ping timeout: 244 seconds] 15:37 < rusty> niftynei: man -l FTW 15:38 < rusty> niftynei: so, have you fixed our reconnect logic yet? :) 15:40 < rusty> niftynei, cdecker: once Travis is happy with https://github.com/ElementsProject/lightning/pull/2244 I'll merge and tag the release... 15:51 < jb55> niftynei: I was considering hacks for lightning-cli help to get manpages relative to its location in the case it hasn't been installed yet... might be useful for people building from source locally? 15:53 < jb55> right now `lightning-cli help` assumes they're installed by just calling out to `man lightning-` 15:53 < jb55> otherwise it falls back to documentation from the api 15:54 <@niftynei> rusty: nope. working on reproducing it atm. :'( 15:55 < rusty> jb55: yea, we could try man -l if man fails? 15:56 < rusty> niftynei: if you run our own test suite it fails on test_restart_many_payments IIRC... 15:56 <@niftynei> the dataloss reconnect thing? that is very helpful 15:56 * niftynei chucks lnd install out the window ;) 15:57 <@niftynei> jk 15:57 < molz> lmao ... 15:57 < molz> there's no 'lnd install' :P 16:23 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 16:24 -!- booyah [~bb@193.25.1.157] has joined #c-lightning 16:43 < jb55> rusty: https://github.com/ElementsProject/lightning/pull/2245 16:44 < jb55> if anyone wants to test `lightning-cli help listpeers` etc. it should now show the manpage even if clightning isn't installed 17:35 < rusty> molz: still around? 17:36 < rusty> I think under the circumstances, molz and ctrlbreak should name the release, if they're around 17:37 < molz> hi rusty :) i'm still waiting to buy you a beer 17:37 < molz> for helping me with my tx last time 17:42 < rusty> molz: ping? 17:43 < molz> oh sorry sec 18:43 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 18:44 < ctrlbreak> 11PM here, so I'm calling it a night :-) Catch you all tomorrow hopefully. 18:47 < rusty> ctrlbreak: 'night, and thanks! 18:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #c-lightning [] 19:02 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 19:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 20:12 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 20:14 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 250 seconds] 20:15 -!- niftynei changed the topic of #c-lightning to: Chat about the C-lightning implementation: https://github.com/ElementsProject/lightning https://lists.ozlabs.org/listinfo/c-lightning Current Version: https://github.com/ElementsProject/lightning/releases/tag/v0.6.3 ~~UPDATE NOW~~ Logs at http://gnusha.org/c-lightning/ 20:24 -!- roasbeef [~root@104.131.26.124] has joined #c-lightning 20:24 < roasbeef> is y 20:25 < roasbeef> is y'all's github irc bot gone also? 20:26 < roasbeef> there's this individual that's gonna port over the now borked github irc bot, can let em know if y'all are interested in it 20:26 < roasbeef> not sure if they're gonna host it tho 20:28 < rusty> roasbeef: hmm, good q, haven't seen it in a while :( 20:29 < roasbeef> yeh seems the old infra it was based on will be gone at the end of this month https://developer.github.com/changes/2018-04-25-github-services-deprecation/ 20:29 < roasbeef> > Note: We no longer support GitHub Services as of October 1, 2018, and GitHub Services will stop working on January 31, 2019. 20:35 < rusty> roasbeef: Damn. 20:38 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning 20:40 < roasbeef> someone's making a replacement tho, will get em to point it at #lightning-dev so we can have the stream from the rfc repo in there again 20:41 < rusty> roasbeef: thanks! 21:00 < rusty> FCK. 21:02 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has left #c-lightning [] 21:03 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-evztbxqdurfwpjrm] has joined #c-lightning 21:15 < jb55> rusty: just notice my git sanity check caught the zip version issue, will 0.6.3 get re-tagged? 21:16 < rusty> jb55: no... that wasn't the only problem with the zip anyway. 21:16 < rusty> (The zip didn't include the submodules, either) 21:17 < rusty> Which predates 0.6.2 21:17 < jb55> ah yeah that's why I wasn't using those for nixos releases... 21:18 < jb55> https://github.com/ElementsProject/lightning/issues/1625 can close this when fixed 21:43 < rusty> jb55: noted, thanks! 21:47 -!- grubles_ [~grubles_@unaffiliated/grubles] has joined #c-lightning 22:39 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 23:07 -!- booyah_ [~bb@193.25.1.157] has joined #c-lightning 23:08 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 23:24 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds] --- Log closed Fri Jan 11 00:00:18 2019