--- Day changed Wed Feb 07 2018 00:08 -!- lxer [~lx@ip5f5bd581.dynamic.kabel-deutschland.de] has joined #c-lightning 00:13 -!- plankers [~plank@c-98-238-141-78.hsd1.ca.comcast.net] has quit [Ping timeout: 256 seconds] 00:39 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection] 00:40 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 01:15 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has joined #c-lightning 01:36 -!- vicenteH [~user@195.235.96.150] has joined #c-lightning 01:43 < provoostenator> brianlockhart: I wasn't able to connect to SLEEPYARK a few days ago, so maybe it's just a bit overloaded. 03:20 < bitonic-cjp> 2018-02-07T11:12:54.290Z lightningd(2766): Server started with public key 029eb2e32dd8c10c34c60cbce660dbb74dd4700240ddb4629660773e636bbcc074, alias node2 (color #00ff00) and lightningd v0.5.2-2016-11-21-1830-gba24fe0b 03:20 < bitonic-cjp> 2018-02-07T11:12:54.290Z lightningd(2766): FATAL SIGNAL 6 RECEIVED 03:20 < bitonic-cjp> Interesting? 03:27 < bitonic-cjp> lightningd: lightningd/peer_control.c:2823: activate_peer: Assertion `!peer->owner' failed. 03:30 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has joined #c-lightning 03:34 < bitonic-cjp> What is peer->owner? 03:35 < bitonic-cjp> Apparently /* Is there a single subdaemon responsible for us? */ 03:48 < bitonic-cjp> Retry, and now it doesn't crash anymore :-( 03:58 < hkjn0> I have seen the same sporadic crash bitonic-cjp, there's an issue open at https://github.com/ElementsProject/lightning/issues/713 04:00 < bitonic-cjp> Note: it has a channel that is CHANNELD_AWAITING_LOCKIN, but its funding_txid already has 225 confirmations. 04:00 < bitonic-cjp> hkjn0: Thanks 04:22 -githubby:#c-lightning- [lightning] lvaccaro opened pull request #940: Add dev-listaddrs command (master...listaddr) https://git.io/vAfVP 04:47 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has quit [Remote host closed the connection] 04:59 < provoostenator> Mmm, just tried with and without wifi and it seems store.blockstream.com doesn't work from my IP. Maybe my (previous) node got itself IP banned somehow? 05:02 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:03 -githubby:#c-lightning- [lightning] ZmnSCPxj opened pull request #941: Recover from unparseable routing failure (master...unparseable-routing-failure) https://git.io/vAfKp 05:19 < bitonic-cjp> The same node now gets this: 05:19 < bitonic-cjp> 2018-02-07T13:18:06.656Z lightningd(17314): peer 0387d0ef27fa0abc8df3225ea97c5f85a7cafb945ec54e806152fe45008a45b226: Funding tx confirmed, but peer state CHANNELD_AWAITING_LOCKIN unowned 05:19 < bitonic-cjp> 2018-02-07T13:18:06.656Z lightningd(17314): peer 0387d0ef27fa0abc8df3225ea97c5f85a7cafb945ec54e806152fe45008a45b226: Funding tx announce ready, but peer state CHANNELD_AWAITING_LOCKIN owned by none 05:21 -githubby:#c-lightning- [lightning] ZmnSCPxj opened pull request #942: Add fee limit to `pay` command (master...pay-fee-limit) https://git.io/vAfiH 05:42 < bitonic-cjp> How can I see the channel balances? 05:51 < lxer> listpeers 05:56 < bitonic-cjp> Thanks, it works. Apparently it's the "msatoshi_to_us" element in the output of that command. 05:57 < lxer> Anyone been able to make a payment from c-lightning? I keep using the latest version, but not one succes since last week. 05:58 -githubby:#c-lightning- [lightning] lvaccaro opened pull request #944: Fix dev-rescan-outputs crash on 0 outputs (master...rescan-zero-outputs) https://git.io/vAfMH 06:02 < bitonic-cjp> I've just made a payment on a local testnet-based network. Need to check the commit I'm using. 06:02 < bitonic-cjp> That was a payment between direct peers though. With two intermediate nodes, it gives: 06:02 < bitonic-cjp> { "code" : -1, "message" : "Could not find a route" } 06:03 < bitonic-cjp> I'm currently on commit ba24fe0ba34434906167f00227c0178d2714166a (jan 23rd) 06:12 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 06:20 < hkjn0> wanted to say everything is working fine here lxer, but nope, getting 'first peer not ready: WIRE_TEMPORARY_CHANNEL_FAILURE' when attempting to tip https://lnmainnet.gaben.win/ 06:21 < hkjn0> on mainnet, commit bbdab02.. looks via earlier IRC logs like that might be https://github.com/ElementsProject/lightning/issues/552 06:22 < lxer> WIRE_UNKNOWN_NEXT_PEER, WIRE_TEMPORARY_CHANNEL_FAILURE , or no route (while i'm connected to a well connected node) 06:24 < hkjn0> my commit is way past the fix for #552 though, so something else going on.. first peer in that route is 03cbf2 (rompert.com), who is connected=false with my node atm 06:25 < hkjn0> https://github.com/ElementsProject/lightning/issues/751#issuecomment-360194395 also mentions this situation and is closed with an attempted fix, but I should have the commit purporting to fix it.. will reply there (and try to rebuild to a later commit) 06:27 < hkjn0> actually, #751 has symptom WIRE_UNKNOWN_NEXT_PEER, whereas my node gives WIRE_TEMPORARY_CHANNEL_FAILURE.. but situation is similar (attempting to route via offline peer) 06:32 < lxer> I have connected to so many nodes, and created many channels, but I have really no idea anymore what is going on. If someone wants me to some test/debug, just let me know 06:32 < hkjn0> okay, please disregard all the above; think I found the issue describing what I'm hitting, #893, and it was closed as fixed 5days ago with a8b789.. so I'd expect it to be fixed once I've rebuilt 06:33 < hkjn0> lxer: check out the issues above and make sure you're rebuilt at a recent commit past the fixes.. then open an issue or give more specific info here if you're still seeing problems 06:37 < lxer> so, tickets are closed without any testing/confirmation? hmmm.. 06:51 <@cdecker> bitonic-cjp, can you check that the node initiating the payment actually sees the second channel? `listchannels` will give you its view of the network 06:51 <@cdecker> Notice that for a channel to be publicly announced both ends need to opt in (default=true) and the funding tx needs 6 confirmations 06:53 < bitonic-cjp> On which node should I do 'listchannels'? On all 4 nodes? 06:55 < bitonic-cjp> On node 0 (the paying node), this is the output of listchannels and listpeers: 06:55 < bitonic-cjp> > listchannels 06:55 < bitonic-cjp> { "channels" : 06:55 < bitonic-cjp> [ ] } 06:55 < bitonic-cjp> > listpeers 06:55 < bitonic-cjp> { "peers" : 06:55 < bitonic-cjp> [ 06:55 < bitonic-cjp> { "id" : "0387d0ef27fa0abc8df3225ea97c5f85a7cafb945ec54e806152fe45008a45b226", "connected" : true, "netaddr" : 06:55 < bitonic-cjp> [ "127.0.0.1:9701" ], "channels" : 06:55 < bitonic-cjp> [ 06:55 < bitonic-cjp> { "state" : "CHANNELD_NORMAL", "owner" : "lightning_channeld", "short_channel_id" : "1278898:324:0", "funding_txid" : "74a35190cfdf6af071c4123b8ee01cd3398a20a4ce528b02a59f5926f8d14ec7", "msatoshi_to_us" : 9999999000, "msatoshi_total" : 10000000000, "dust_limit_satoshis" : 546, "max_htlc_value_in_flight_msat" : 18446744073709551615, "channel_reserve_satoshis" : 0, "htlc_minimum_msat" : 0, "to_self_delay" : 6, 06:55 < bitonic-cjp> "max_accepted_htlcs" : 483 } ] } ] } 06:55 < bitonic-cjp> Weird: why isn't at least its own channel listed in listchannels? 06:57 < bitonic-cjp> I vaguely remember listchannels giving me non-empty output in the past, but right now, its output is empty on all 4 nodes. 06:59 < bitonic-cjp> also: 06:59 < bitonic-cjp> > listnodes 06:59 < bitonic-cjp> { "nodes" : 06:59 < bitonic-cjp> [ ] } 07:02 < bitonic-cjp> Earlier, I successfully performed a 1-hop payment between node 0 and node 1 (direct neighbours). 07:06 < bitonic-cjp> Now, even that doesn't work anymore. 07:15 < bitonic-cjp> Might it depend on whether A connects to B or B connects to A? 07:26 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has quit [Remote host closed the connection] 07:32 <@cdecker> Please don't copy paste into IRC, the node used to initiate the payment will need to learn about the channel, so that's the only `listchannels` that is needed 07:32 <@cdecker> Have both nodes restarted? 07:33 <@cdecker> Then they might have forgotten about their channel 07:33 < bitonic-cjp> Restarted since when? 07:33 < bitonic-cjp> The channel is still in the listpeers output. 07:35 <@cdecker> Yeah, but the channel announcement is forgotten across restarts currently 07:35 < bitonic-cjp> so? 07:36 < bitonic-cjp> BTW, yes, the nodes have restarted several times already. 07:38 < bitonic-cjp> Should channel announcement somehow be re-initiated, and if so, how? 07:44 < devachandra> How can i spend whole output when funding channel? 07:54 -!- zib [zib@slick.hkt0.keff.org] has quit [Ping timeout: 264 seconds] 08:01 -!- zib [zib@slick.hkt0.keff.org] has joined #c-lightning 08:17 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has quit [Ping timeout: 265 seconds] 08:28 <@cdecker> bitonic-cjp, we just need to store them, which is part of a bigger task 08:28 <@cdecker> Currently there is no way to regenerate them without a new channel 08:29 < bitonic-cjp> wow, lots of work to do then. 08:29 <@cdecker> It's not a problem if you're connected to a larger network since other nodes will tell you about own channel :-) 08:29 <@cdecker> Yeah, there's a lot to do still 08:29 < bitonic-cjp> How many nodes is 'a larger network'? I have 4 C-lightning nodes. 08:32 -!- bitonic-cjp [~bitonic-c@92-111-70-106.cable.dynamic.v4.ziggo.nl] has quit [Quit: Leaving] 08:44 <@cdecker> Well all you need is one node that stays alive while the others restart, that node'll store the gossip messages and resync them to the restarted nodes 09:03 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 260 seconds] 09:05 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-imrtpbsdfyctnfgq] has joined #c-lightning 09:23 -githubby:#c-lightning- [lightning] cdecker opened pull request #947: master: Don't crash if peer reconnects before we activate it (master...issue-713) https://git.io/vAJnc 09:30 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has joined #c-lightning 09:43 -!- JSorel [~JSorel@207.96.226.25] has joined #c-lightning 09:54 -!- JSorel [~JSorel@207.96.226.25] has quit [Ping timeout: 256 seconds] 10:43 -!- vicenteH [~user@195.235.96.150] has quit [Ping timeout: 248 seconds] 10:56 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 11:10 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 11:20 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has quit [Remote host closed the connection] 11:43 -!- redstorm [cb56cc58@gateway/web/freenode/ip.203.86.204.88] has joined #c-lightning 11:43 < redstorm> Payments to Starblocks work but not to Y'alls, fails with WIRE_TEMPORARY_CHANNEL_FAILURE 11:44 < redstorm> decodepay and getroute returns 3hops to Y'alls with funds available. 12:29 < redstorm> Is this issue fixed in #638 12:30 -!- ebx [~ebx@unaffiliated/ebex] has quit [Read error: Connection reset by peer] 12:32 < lxer> ^^same here 12:34 -!- CubicEarths [~cubiceart@190.140.125.142] has joined #c-lightning 12:47 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has joined #c-lightning 13:20 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 13:44 -!- CubicEarths [~cubiceart@190.140.125.142] has quit [] 13:59 -!- jojeyh [~delphi@2602:306:b8b6:b970:d98b:b647:e8bb:7960] has quit [Ping timeout: 276 seconds] 14:07 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection] 14:08 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #c-lightning 14:13 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 256 seconds] 14:16 < redstorm> is their a workaround for WIRE_TEMPORARY_CHANNEL_FAILURE 14:30 -!- redstorm [cb56cc58@gateway/web/freenode/ip.203.86.204.88] has quit [Quit: Page closed] 14:41 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 14:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 15:06 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 264 seconds] 15:11 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 15:16 < grafcaps> anybody know the ID of the starblocks node? 15:17 < rusty> grafcaps: it's on their invoices... 15:18 < rusty> grafcaps: 035b55e3e08538afeef6ff9804e3830293eec1c4a6a9570f1e96a478dad1c86fed 15:19 < grafcaps> thanks 15:25 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer] 15:29 -!- jojeyh [~delphi@99-59-126-62.lightspeed.irvnca.sbcglobal.net] has joined #c-lightning 16:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:10 < jojeyh> Trying to get a channel working on testnet so I can start playing with the client. Successfully connected to the node listen on the testnet faucet, but how do I add funds to use once I am connected? 16:11 < jojeyh> Is it possible to get some testnet funds on the channel created using the faucet? I can't get it to work unless I input 0 satoshis for the initial amount. 16:11 -!- lxer [~lx@ip5f5bd581.dynamic.kabel-deutschland.de] has quit [Ping timeout: 248 seconds] 16:21 -!- jojeyh [~delphi@99-59-126-62.lightspeed.irvnca.sbcglobal.net] has quit [Ping timeout: 256 seconds] 16:21 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 16:26 -!- jojeyh [~delphi@99-59-126-62.lightspeed.irvnca.sbcglobal.net] has joined #c-lightning 16:26 < grafcaps> jojeyh: you have to make an on-chain payment to your c-lightning wallet before you can fund channels 16:26 < grafcaps> does it say anything if you `lightning-cli listfunds`? 16:26 < jojeyh> grafcaps, i did fund my wallet with an onchain tx 16:26 < jojeyh> yes i have funds listed 16:26 < grafcaps> cool, have you tried `lightning-cli fundchannel` yet? 16:27 < grafcaps> connecting and funding is separate in c-lightning 16:27 < jojeyh> yes `lightning-cli fundchannels` returns `channel already NORMALD 16:27 -!- aproc [~aproc@2605:6000:e503:8300:d0d1:d4e4:4c7d:9150] has quit [Ping timeout: 252 seconds] 16:28 < jojeyh> "Peer already CHANNELD_NORMAL" 16:28 < grafcaps> if you do `listpeers` and find that channel, does it have values for `msatoshi_total` or `msatoshi_to_us`? 16:29 < jojeyh> yes, msatoshi_total 1000000 16:29 < jojeyh> msatoshi_to_us 0 16:29 < jojeyh> i opened the channel using the lightning testnet faucet 16:29 < jojeyh> but was unable to get a channel created with any value other than 0 for 'inital amount' 16:30 < jojeyh> which i assume is the same as `msatoshi_to_us` in this initial case 16:30 < grafcaps> did you create the channel from your c-lightning node or from the faucet? 16:30 < grafcaps> to your node 16:30 < jojeyh> from the faucet 16:30 < jojeyh> from faucet to my node 16:30 < grafcaps> okay, I'm pretty sure you can only send payments to your node over that channel 16:31 < jojeyh> ok if i open a channel using my local client will the lightning testnet node accept the connection automatically? 16:31 < grafcaps> it should 16:31 < grafcaps> if you want to try to open a channel to my node, it's 0306854ac4441a52d41c23780c29b8103265f00006709d674f0ef23395d6e43904 104.137.194.255 16:32 < jojeyh> ok i'll try both, thanks! 16:32 < jojeyh> so i guess one can't fund a channel with more satoshis once the channel has been created? 16:32 < jojeyh> seems like a nice feature to work on 16:32 < jojeyh> in my free time 16:32 < grafcaps> it seems that way to me 16:33 < grafcaps> I'm still very new at this myself 16:33 < jojeyh> lol 16:33 < jojeyh> we'll figure it out 16:33 < jojeyh> i gotta go back and read the RFCs 16:33 < jojeyh> i've been lazy 16:37 < jojeyh> how long does it usually take for a channel to shutdown once it enters state 'CHANNELD_SHUTTING_DOWN' 16:38 < grafcaps> I think it depends on a few factors, including the parameters that were used to setup the channel 16:39 < grafcaps> not with c-lightning but with lnd I've had it take anywhere from 4 to 144 blocks to close a channel 16:39 < jojeyh> ouch lol 16:39 < jojeyh> testnet won't be too bad 16:39 < jojeyh> so basically there are two funding transactions, an inital one to the wallet and then another to fund a channel, both of which are onchain? 16:39 -!- aproc [~aproc@2605:6000:e503:8300:2828:d4f9:cb3f:f5fd] has joined #c-lightning 16:40 < grafcaps> yeah, you have to have BTC in your lightning wallet first, then you can open and fund channels 16:41 < jojeyh> thats interesting, i wonder if it could be done with just a single transaction to fund the channel 16:41 < jojeyh> or what the logic behind having two separate txs is 16:42 < grafcaps> well it's basically just like an on-chain wallet (or real life wallet), in that you have to have money in it in order to be able to spend 16:42 < jojeyh> but if you're always connected to your bitcoin wallet, its not necessary 16:42 < jojeyh> at least i think lol 16:43 < jojeyh> maybe its just cleaner 16:43 < jojeyh> and maybe almost everyone will be sending bitcoin to their lightning client onchain address 16:43 < jojeyh> so it won't matter 16:44 < jojeyh> seems extraneous though, just cause you have to have funds in a channel to use them anyways, and it requires an onchain tx to fund the channel 16:44 < grafcaps> you mean funds from your full node wallet? I'm fairly confident that c-lightning doesn't interact with the Bitcoin Core wallet, I'm not even sure you have to have the Core wallet enabled 16:44 < jojeyh> you have to be able to check the onchain txs 16:45 < grafcaps> right but the wallet is separate from the node, you can run bitcoind with -disablewallet 16:45 < jojeyh> you can't know that a wallet or channel has funds unless you are running a node and checking the ledger 16:45 < jojeyh> ah good point lol 16:45 < jojeyh> it all makes sense now 16:51 -07IACGJ88:#c-lightning- [lightning] rustyrussell closed pull request #941: Recover from unparseable routing failure (master...unparseable-routing-failure) https://git.io/vAfKp 16:51 -7GHAB2J58:#c-lightning- [lightning] rustyrussell pushed 2 new commits to master: https://git.io/vAUYn 16:51 -7GHAB2J58:#c-lightning- lightning/master 0d0ef2c ZmnSCPxj: gossipd: Implement gossip_mark_channel_unroutable.... 16:51 -7GHAB2J58:#c-lightning- lightning/master d666857 ZmnSCPxj: pay: Recover from unparseable routing failures by random disabling of channels.... 17:07 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vAUOg 17:07 -githubby:#c-lightning- lightning/master 7da942d luca vaccaro: Fix dev-rescan-outputs crash on 0 outputs (#944)... 17:08 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vAUOV 17:08 -githubby:#c-lightning- lightning/master e046194 Christian Decker: master: Don't crash if peer reconnects before we activate it... 17:11 -!- jojeyh [~delphi@99-59-126-62.lightspeed.irvnca.sbcglobal.net] has quit [Ping timeout: 240 seconds] 17:13 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 264 seconds] 17:26 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #949: test_lightningd: race fix for activation of channels in test_gossip_jsonprc (master...fix-another-spurious-timeout) https://git.io/vAU3y 17:27 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 17:28 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #950: wireaddr: rework port parsing for weird addresses. (master...fix-wireaddr-parsing) https://git.io/vAU3b 17:31 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 17:32 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has quit [Ping timeout: 268 seconds] 17:35 -!- mn3monic [~xxwa@host232-214-dynamic.251-95-r.retail.telecomitalia.it] has joined #c-lightning 17:35 -!- mn3monic [~xxwa@host232-214-dynamic.251-95-r.retail.telecomitalia.it] has quit [Changing host] 17:35 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has joined #c-lightning 17:37 -!- grafcaps [~haroldbr@50.90.83.229] has joined #c-lightning 17:45 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-imrtpbsdfyctnfgq] has quit [Quit: Connection closed for inactivity] 17:58 -!- jojeyh [~delphi@2602:306:b8b6:b970:e90a:7ac3:15b5:4a1d] has joined #c-lightning 18:13 -!- bryan_w [~is@2600:2108:9:8a90:5a69:d114:68b8:dae2] has joined #c-lightning 18:21 -!- CubicEarths [~cubiceart@190.140.125.142] has joined #c-lightning 18:34 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-tpodpocbiokuhvjo] has joined #c-lightning 18:57 -!- CubicEarths [~cubiceart@190.140.125.142] has quit [Remote host closed the connection] 18:57 -!- CubicEarths [~cubiceart@190.140.125.142] has joined #c-lightning 19:01 -!- CubicEarths [~cubiceart@190.140.125.142] has quit [Ping timeout: 240 seconds] 19:12 -!- CubicEarths [~cubiceart@190.140.125.142] has joined #c-lightning 19:13 < jojeyh> strang error, attempted to connect to a channel, returned id of peer as normal, then any subsequent call of lightning-cli results in 'lightning-cli: Connecting to 'lightning-rpc': Connection refused' 19:14 < grafcaps> sounds like your node crashed 19:14 < grafcaps> lightning-rpc is the socket that lightning-cli uses 19:14 < jojeyh> ah so it did 19:20 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has joined #c-lightning 19:24 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #951: gossipd: fix race where we can handoff peer with bad cryptostate. (master...fix-gossipd-handoff-race) https://git.io/vAUCS 19:25 -!- miklolFi [~miklolFi@78-27-126-165.bb.dnainternet.fi] has quit [Ping timeout: 248 seconds] 19:25 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 19:25 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 19:30 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 248 seconds] 19:33 -!- CubicEarths [~cubiceart@190.140.125.142] has quit [] 20:11 -!- CubicEarths [~cubiceart@190.140.125.142] has joined #c-lightning 20:23 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 20:40 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has quit [Ping timeout: 276 seconds] 20:51 -!- mn3monic [~xxwa@host232-214-dynamic.251-95-r.retail.telecomitalia.it] has joined #c-lightning 20:51 -!- mn3monic [~xxwa@host232-214-dynamic.251-95-r.retail.telecomitalia.it] has quit [Changing host] 20:51 -!- mn3monic [~xxwa@unaffiliated/mn3monic] has joined #c-lightning 21:41 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 21:55 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 260 seconds] 21:55 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 21:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 22:13 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Remote host closed the connection] 22:13 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has joined #c-lightning 22:15 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-tpodpocbiokuhvjo] has quit [Quit: Connection closed for inactivity] 22:22 -!- CubicEarths [~cubiceart@190.140.125.142] has quit [] 22:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 23:58 -!- sengehest [~sengehest@188.81-166-37.customer.lyse.net] has quit [Ping timeout: 248 seconds]