--- Day changed Fri Jan 19 2018 00:21 -!- plankers [~plank@c-73-2-4-197.hsd1.ca.comcast.net] has quit [Quit: Leaving.] 01:16 -!- tomichec [~pi@ip-86-49-245-13.net.upcbroadband.cz] has quit [Ping timeout: 248 seconds] 01:32 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 01:35 -!- vicenteH [~user@195.235.96.150] has joined #c-lightning 02:10 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vNEpp 02:10 -githubby:#c-lightning- lightning/master 69260ad renepickhardt: quickfixing issue #662 to make CLI more userfriendly for inexperienced users (#663)... 02:11 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #646: Sync dependencies between README.md and doc/INSTALL.md. Add dependency consistency check. (master...sync-readme-and-install) https://git.io/vN0ut 02:17 -!- provoostenator [~vwDZ2BYsc@2a05:d014:5f:e100:fd30:8af7:2d6a:cbb1] has joined #c-lightning 02:18 < provoostenator> cdecker: I have a BotBot instance so can add logging if you like. Not sure how much is happening here. 02:18 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 02:19 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 02:22 <@cdecker> ianthius, it was a way to add funds to the client before we scanned the blockchain for incoming funds 02:22 <@cdecker> You had to getrawtransaction and then pass the hex encode tx to addfunds 02:22 <@cdecker> It's deprecated since we now grab all of our funds off of the chain 02:23 <@cdecker> provoostenator, thanks for offering, not sure we want to log this channel just yet, #lightning-dev may be more useful 02:24 < provoostenator> No problem. #lightning-dev is already logged, so no need there. 02:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 02:38 < provoostenator> Where does lightningd keep logs? 02:39 < provoostenator> I'm only seeing ~/.lightning/crash.log, but that's probably not what I need to debug a channel negotiation failure. 02:42 < provoostenator> That and stdout from lightningd, but that's pretty sparse. 02:46 < provoostenator> cli/lightning-cli getlog io 03:01 < provoostenator> Achievement unlocked: T-Shirt bought! 03:06 -!- kabaum [~kabaum@h-13-35.A163.priv.bahnhof.se] has joined #c-lightning 03:41 < kabaum> Hi! I use c-lightning on testnet and by mistake connected to a mainnet c-lightning node (blockstream store). Can I disconnect the network connection (state GOSSIPING) somehow? 03:42 < kabaum> { "state" : "GOSSIPING", "peerid" : "02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432", "netaddr" : 03:42 < kabaum> [ "104.198.32.198:9735" ], "connected" : true, "owner" : "lightning_gossipd" } ] } 03:54 < kabaum> Should it even be possible/desirable to be able to connect to a mainnet peer from a testnet node, or vice versa? 04:26 -!- mesh_ [meshcollid@gateway/shell/elitebnc/x-byequoycyezmedgp] has quit [Ping timeout: 248 seconds] 04:27 -!- moctost [~moctost@107.182.231.94] has quit [Ping timeout: 248 seconds] 04:27 -!- lio17 [~lio17@ns350827.ip-37-187-174.eu] has quit [Ping timeout: 248 seconds] 04:28 -!- lio17 [~lio17@ns350827.ip-37-187-174.eu] has joined #c-lightning 04:29 -!- llou [~textual@85.152.204.69] has quit [Ping timeout: 256 seconds] 04:29 -!- meshcoll- [meshcollid@gateway/shell/elitebnc/x-potiumxsikkfmqxw] has joined #c-lightning 04:30 -!- meshcoll- is now known as mesh_ 04:46 -githubby:#c-lightning- [lightning] ZmnSCPxj opened pull request #670: [0.6] wallet: Properly save `wallet_payment::path_secrets`. (master...path-secrets) https://git.io/vNumM 05:34 -githubby:#c-lightning- [lightning] cdecker closed pull request #670: [0.6] wallet: Properly save `wallet_payment::path_secrets`. (master...path-secrets) https://git.io/vNumM 05:34 -!- jenny56_ [506e4d46@gateway/web/freenode/ip.80.110.77.70] has joined #c-lightning 05:37 -!- jenny56_ [506e4d46@gateway/web/freenode/ip.80.110.77.70] has quit [Client Quit] 05:47 -!- qxt [~qxxt@unaffiliated/qxt] has quit [Ping timeout: 240 seconds] 06:32 -githubby:#c-lightning- [lightning] cdecker opened pull request #672: pytest: Fix test_fee_limits (master...issue-669) https://git.io/vNuWh 06:33 -!- moctost [~moctost@cpe-107-9-138-59.neo.res.rr.com] has joined #c-lightning 06:49 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-hpahirrgympoulzf] has quit [Quit: Connection closed for inactivity] 06:52 -!- moctost [~moctost@cpe-107-9-138-59.neo.res.rr.com] has quit [Ping timeout: 255 seconds] 07:03 -githubby:#c-lightning- [lightning] cdecker opened pull request #674: options: Dropping default base_fee for mainnet to 1 satoshi (master...issue-673) https://git.io/vNuR4 07:12 -githubby:#c-lightning- [lightning] cdecker closed pull request #658: channeld: don't consider shutdown complete if feechange pending. (master...shutdown-not-complete-if-feechange-pending) https://git.io/vNEaf 07:19 -!- kexkey [~kexkey@173.209.48.158] has quit [Ping timeout: 268 seconds] 07:55 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning 08:28 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 256 seconds] 08:30 < lio17> I have similar issue/question as kabaum. is there a list of channel states somewhere? 08:30 < lio17> I have a few that are stuck in CHANNELD_AWAITING_LOCKIN - what do I need to do there? 08:31 -!- f4t4l_ [c6d04811@gateway/web/freenode/ip.198.208.72.17] has joined #c-lightning 08:45 < provoostenator> lio17: getpeers shows channel states 08:45 -githubby:#c-lightning- [lightning] practicalswift opened pull request #676: Don't greet new users with an error message (master...welcome-new-user) https://git.io/vNu6Q 08:47 < ianthius> cdecker: where is the c-lightning wallet stored? e.g. where do addresses from newaddr come from? 08:47 < ianthius> cdecker: thanks for the answer on addfunds. that makes sense 08:55 -!- ruby32 [~ruby32@158.106.219.26] has joined #c-lightning 09:27 -!- jb55 [~jb55@208.98.200.100] has joined #c-lightning 09:29 -!- plankers [~plank@c-73-2-4-197.hsd1.ca.comcast.net] has joined #c-lightning 09:54 -!- f4t4l_ [c6d04811@gateway/web/freenode/ip.198.208.72.17] has quit [Ping timeout: 260 seconds] 10:03 < lio17> provoostenator: yes. I mean what means CHANNELD_AWAITING_LOCKIN ? and how do I deal with connections that are somehow stuck in that state? 10:37 < hop3y> how long has it been? 10:37 < hop3y> it might take atleast 10min 10:38 < hop3y> right? 10:40 -!- vicenteH [~user@195.235.96.150] has quit [Ping timeout: 240 seconds] 10:42 < lio17> it was pretty long. 10:42 < lio17> days 10:42 < lio17> shouldn't take days on testnet 10:42 < lio17> but I am also rather new to using c-lightning so I am not good at debugging it yet ;/ 10:46 < ianthius> anyone know how to set the alias on your node? Looking in the code looks like maybe '-alias=myAlias' on lightingd? 10:52 -!- HectorJ [58bed82b@gateway/web/freenode/ip.88.190.216.43] has joined #c-lightning 10:53 < HectorJ> Hi! 10:53 < HectorJ> I'm having a weird issue where after trying to connect to a node like this : 10:53 < HectorJ> lightning-cli connect 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 104.198.32.198 9735 10:54 < HectorJ> { "id" : "02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432" } 10:54 < HectorJ> I try to open fund a channel and get this : 10:54 -!- Hectorj_ [58bed82b@gateway/web/freenode/ip.88.190.216.43] has joined #c-lightning 10:55 < Hectorj_> arf, I got disconnected 10:55 < Hectorj_> lightning-cli fundchannel 02f6725f9c1c40333b67faea92fd211c183050f28df32cac3f9d69685fe9665432 250000 10:55 < Hectorj_> "Peer not connected" 10:55 < lio17> ianthius: yes --alias in lightningd 10:56 < lio17> I use a config file and specify --lightning-home 10:58 -!- HectorJ [58bed82b@gateway/web/freenode/ip.88.190.216.43] has quit [Ping timeout: 260 seconds] 11:00 -!- Hectorj_ [58bed82b@gateway/web/freenode/ip.88.190.216.43] has quit [Ping timeout: 260 seconds] 11:14 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wycsvmcfcgjhmsqq] has joined #c-lightning 11:21 < ianthius> ls 11:25 < hop3y> lio17: days is too long I would guess, next conf or so... 11:25 < hop3y> and I am total newb, this is just my experience 12:04 < hkjn0> hmm, with debug logs on I keep seeing "lightningd(112):jcon fd 14: Closing (Bad file descriptor)" when using lightning-cli commands 12:05 < hkjn0> nothing breaks, but perhaps the client isn't closing tcp sockets correctly? 12:07 -!- moctost [~moctost@209.95.51.98] has joined #c-lightning 12:14 -!- moctost_ [~moctost@107.182.231.98] has joined #c-lightning 12:18 -!- moctost [~moctost@209.95.51.98] has quit [Ping timeout: 260 seconds] 12:18 -!- moctost_ is now known as moctost 12:31 -!- vicenteH [~user@35.233.15.37.dynamic.jazztel.es] has joined #c-lightning 12:44 < ianthius> my lightningd is crashing because it can't authenticate to bitcoind RPC but as the same user i am easily able to RPC on bitcoin-cli with teh cookie auth.. and when I run bitcoind -testnet and do a testnet lightningd it finds the cookie just fine... Ideas? 12:47 < hkjn0> ianthius: I had the same issue earlier today, but turned out that root cause of crash (as seen in ~/.lightning/crash.log) was that lightningd couldn't discover its ip addr 12:48 < hkjn0> once I specified it explicitly on command line lightningd started fine 12:48 < hkjn0> (error message could definitely be better in this case) 12:49 < lio17> hop3y: any idea how to debug that situation? 12:51 < ianthius> hkjn0: so you pointed it to localhost? my bitcoind is on this machine 12:51 < ianthius> hkjn0: what did you specify on the command line exactly? 12:54 -!- moctost [~moctost@107.182.231.98] has quit [Quit: moctost] 12:55 < hop3y> lio17: nope :( 12:56 < hop3y> so you have funds in channel, but it doesn't get confirm, I guess that's the situation 12:56 < hop3y> maybe fee is too low? 12:57 < hop3y> just guessing, no idea how to increase the fee, how to check it etc 13:02 < hkjn0> ianthius: my environment is not very standard so ymmw, but my full commandline was './lightningd --network=bitcoin --ipaddr=163.172.162.18 --log-level=debug --alias=hkjn' 13:03 < ianthius> the --network=bitcoin may be what i was missing, do you need to do that explicitly to get on mainnet? 13:03 < hkjn0> without the --ipaddr set explicitly, symptom was that lightningd failed to start with 'lightningd(98): bitcoin-cli exited with code 1: error: Could not locate RPC credentials.`' 13:04 < hkjn0> yeah, I believe so 13:04 < ianthius> i was running --network=testnet previously and then just left it off to get to mainnet, but maybe I need to set it explicitly. I'll try that. thanks 13:07 < ianthius> hkjn0: thanks you! that was what I was missing. onward to mainnet! 13:08 < hkjn0> happy to help.. I think. don't lose money :ODODODODODOD) 13:09 < hkjn0> (er, no idea what happened at the end of the line there..) 13:11 < ianthius> yeah, don't worry. I'll be fine. has anyone moved thier node from tesnet to mainnet? I launched lightningd onto mainnet but getpeers and listfunds is still listing testnet info! 13:12 < hkjn0> myself and someone else doing mainnet testing noticed some really weird networking output.. first he (running lnd) reported that my node address showed up as 163.172.162.18:50736.. but I'm serving on the default, tcp/9735 13:12 < hkjn0> some minutes after that, getpeers for me showed his node with "netaddr" : [ "[::ffff:176.10.136.25]:52436" ] 13:13 < hkjn0> he is also on default port, plus.. what even is that addr? mangled half-ipv6, half-ipv4? 13:13 < hkjn0> I'll let you know if we can repro it (after restart of his node the expected addrs are reported), thought I should mention it 13:14 -!- hector_j [58bed82b@gateway/web/freenode/ip.88.190.216.43] has joined #c-lightning 13:28 < ianthius> --help claims that fundchannel uses satoshis, but i think it's been using millisatoshis, can someone clarify what the amount was using for them on mainnet? I dodn't want to be off by 3 orders of magnitude on mainnet 13:28 < ianthius> at least i think it used millisatoshi for me on testnet 13:30 < ianthius> or maybe it was payments that were mSatoshi and funding was satoshi. I don't think funding could be fractional the blockchain wouldn't allow that. Nevermind. Ignore me ;) 13:39 -!- DrOlmer [~DrOlmer@unaffiliated/drolmer] has joined #c-lightning 13:45 -!- TerminusAlamond4 [~TerminusA@sj0.logicfailed.com] has joined #c-lightning 13:49 < ianthius> cdecker: I ran a c-lightning instance as testnet, then i launched it mainnet, it's now running as some sort of hybrid. i was able to 'newaddr' for a mainnet segwit address and send to it succesfully, then i connected to the node you posted on twitter, but when I went to fund the channel it created a testnet channel, what do i do to force the lightningd to use mainnet coins and why is lightningd 13:49 < ianthius> reporting both mainnet and testnet coins in 'listfunds'? 13:52 < ianthius> now the lightningd is trying to broadcast raw transaction and it keep errorying out due to missing inputs. Can I cancel the channel open somehow? 13:54 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wycsvmcfcgjhmsqq] has quit [Quit: Connection closed for inactivity] 14:19 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 14:22 -!- jojeyh [~delphi@2602:306:b8b6:b970:e93c:6a30:fd51:e2c2] has quit [Ping timeout: 276 seconds] 14:23 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #c-lightning [] 14:24 -92AACQIDH:#c-lightning- [lightning] rustyrussell closed pull request #623: Json api cleanup (master...json-api-cleanup) https://git.io/vN4OO 14:24 -7GHABWOI3:#c-lightning- [lightning] rustyrussell pushed 30 new commits to master: https://git.io/vNzsh 14:24 -7GHABWOI3:#c-lightning- lightning/master 1f6392f Rusty Russell: lightningd: --deprecated-api option to turn off deprecated APIs.... 14:24 -7GHABWOI3:#c-lightning- lightning/master 6b740e7 Rusty Russell: json: more sanity checks on JSON output.... 14:24 -7GHABWOI3:#c-lightning- lightning/master 461207b Rusty Russell: getroute: document cltv argument.... 14:25 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vNzGL 14:25 -githubby:#c-lightning- lightning/master 97447dd Christian Decker: options: Dropping default base_fee for mainnet to 1 satoshi... 14:27 -githubby:#c-lightning- [lightning] rustyrussell closed pull request #672: pytest: Fix test_fee_limits (master...issue-669) https://git.io/vNuWh 14:28 -githubby:#c-lightning- [lightning] rustyrussell pushed 1 new commit to master: https://git.io/vNzG1 14:28 -githubby:#c-lightning- lightning/master e2d6613 Tomas Stary: adding the bash completition script for the client 14:29 < lio17> hop3y: ok, thanks. will report if I find something 14:30 -!- Xanthin [ad26d108@gateway/web/freenode/ip.173.38.209.8] has joined #c-lightning 14:34 -!- jojeyh [~delphi@2602:306:b8b6:b970:99a5:d356:f613:adc5] has joined #c-lightning 14:39 < Xanthin> anyone around? 14:43 < ianthius> Xanthin: not really. :) 14:44 < ianthius> cdecker: I filed a github issue for the mainnet, testnet thing.. 14:44 < ianthius> https://github.com/ElementsProject/lightning/issues/678 14:44 < ianthius> have all the logs in case they are useful, but should be pretty easy to repro 14:47 < Xanthin> I'm trying to play around with a c-lightning node. But have a few questions 14:48 < Xanthin> Is it possible to export the private key of the newaddr that is created? 14:50 < ianthius> Xanthin: i need that exact thing right now actually 14:51 < ianthius> i don't know how either. i am stucjk with a bug and my mainnet stash i had to play around with is now 'stuck' in the wallet, i don't know how to dump that private key or withdraw the funds given my situation. 14:52 < Xanthin> Ok, I assume it must be stored somewhere, but can't find it. Want to open some mainnet channels but reluctant to send funds if I don't have the privkey 14:53 < Xanthin> heh, you are braver than me 14:54 < ianthius> my guess is that it's in that database in the .lightning directory 14:58 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 15:02 < Xanthin> These are the tables in that database: sqlite> .tables channel_configs invoices peers vars channel_htlcs outputs shachain_known version channels payments shachains 15:03 < Xanthin> no wallet table 15:03 < ianthius> Xanthin: it's like a treasure hunt! :) 15:04 < ianthius> there is an outputs table but not inputs? 15:04 < Xanthin> Well it's fun 15:04 < ianthius> open my issue in github. 15:05 < Xanthin> But I just did another " cli/lightning-cli newaddr" and the database file in .lightning gets updated. 15:05 < Xanthin> So it must he in there then. 15:05 < ianthius> the interesting thing is that it's comingling everything, so since i have funds both in testnet and mainnet I can't safely move or withdraw or open channels 15:06 < ianthius> i don't know how it chooses inputs, but it's definelty using testnet inputs for my mainnet node. i think withdraw will do the same.. 15:07 -!- plankers [~plank@c-73-2-4-197.hsd1.ca.comcast.net] has quit [Quit: Leaving.] 15:10 < Xanthin> So it's better to run testnet and mainnet in different environments then 15:10 < Xanthin> I just went straight to mainnet ;-) 15:11 < ianthius> i thought i was being safer by learning first lol 15:12 < ianthius> but i think you could delete that data dir or move it and then go mainnet 15:12 < ianthius> how did you launch your node into mainnet? 15:17 < Xanthin> had mainnet bitcoind running 15:18 < Xanthin> then " ./lightningd/lightningd --network=bitcoin --log-level=debug" 15:19 -!- hector_j [58bed82b@gateway/web/freenode/ip.88.190.216.43] has quit [Ping timeout: 260 seconds] 15:20 < Xanthin> Do you know sql? 15:20 < Xanthin> The keys are in the vars table 15:20 < Xanthin> sqlite> select * from vars; 15:20 < Xanthin> next_pay_index|1 15:20 < Xanthin> bip32_max_index|6 15:20 < Xanthin> I did a "newaddr" 6 times 15:20 < Xanthin> but how do I look into the 'bip32_max_index' column with sql? 15:27 < Xanthin> Not sure now, don't think it is stored there, just shows there are 6 keys. But where are they? 15:35 < ianthius> could be encrypted with teh HSM secret in the data dir? 15:35 < ianthius> i have no idea. I moved my data directory and I am going to find more bitcoin 15:35 < ianthius> i'll have to try and recover my satoshis later 15:35 < Xanthin> I just dumped the whole database, it's not in there 15:36 < ianthius> if you end up finding them let me know 15:37 < ianthius> i'd like to use those coins instead of adding new ones :) 15:37 < Xanthin> of course.. I hope there is a way. Did you already shut the node down? 15:37 < ianthius> yes 15:37 < Xanthin> I hope it is not just stored in memory 15:37 < ianthius> i restarted it though now with a new data directory 15:38 < ianthius> Xanthin: lol! that would be crazy 15:38 < ianthius> i know it's not since i have restarted a testnet node multiple times and the funds were always there 15:39 < Xanthin> ok, that's good to know 15:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 15:42 -!- ruby32 [~ruby32@158.106.219.26] has quit [Remote host closed the connection] 15:54 < ianthius> https://github.com/ElementsProject/lightning/blob/879715982546ed79eec9d25c042d26ea6b7df9d2/wallet/db.c 15:59 < ianthius> there is a 256 bit key called secret 15:59 < ianthius> and a secrets column in the DB.... 16:04 < ianthius> then in pubkey.c all the public keys are generated off of this secret 16:04 < ianthius> so i think this is the private key, still not sure where it is stored 16:07 < Xanthin> no, I can't find it either 16:08 -!- jb55 [~jb55@208.98.200.100] has quit [Ping timeout: 256 seconds] 16:21 < ianthius> getting closer :) 16:21 < ianthius> https://github.com/ElementsProject/lightning/blob/7ece90038b4fd078ad8b320855fe65d4995ba2a7/common/derive_basepoints.c 16:30 < Xanthin> https://github.com/ElementsProject/lightning/blob/7ece90038b4fd078ad8b320855fe65d4995ba2a7/common/key_derive.c 16:31 < Xanthin> The corresponding private keys can be derived similarly if the basepoint * secrets are known (i.e., `localkey`, `local_htlckey` and `local_delayedkey` * only): 16:31 < Xanthin> secretkey = basepoint_secret + SHA256(per_commitment_point || basepoint) 16:33 -githubby:#c-lightning- [lightning] cdecker pushed 1 new commit to master: https://git.io/vNzEV 16:33 -githubby:#c-lightning- lightning/master 2f179fb practicalswift: Don't greet new users with an error message... 16:54 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:11 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 256 seconds] 17:13 -!- Xanthin [ad26d108@gateway/web/freenode/ip.173.38.209.8] has quit [Ping timeout: 260 seconds] 18:00 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has joined #c-lightning 18:09 -!- jb55 [~jb55@70-36-49-138.dyn.novuscom.net] has quit [Ping timeout: 248 seconds] 18:37 -!- plankers [~plank@c-73-2-4-197.hsd1.ca.comcast.net] has joined #c-lightning 18:39 < ianthius> i might be able to delete the entries in the database for the testnet funds and then do a 'withdraw' on the mainnet funds.. 18:42 -!- plankers [~plank@c-73-2-4-197.hsd1.ca.comcast.net] has quit [Client Quit] 19:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 20:33 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-avmmqdugmytlxuod] has joined #c-lightning 20:40 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #679: Speed up cli (master...speed-up-cli) https://git.io/vNzKb 20:40 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 21:59 < ianthius> hey guys estimated fees have dropped below the feerate in the client ATM, how do we address this? I am getting na error about feerate being below the mininum of 27770.. 22:08 < ianthius> okay so there is dev-setfees, I have so many questions about fees. lol 22:09 < ianthius> biggest question is if we use dev-setfees, is that turning off the (what seems like) awesome fee estamation going on in the node? 22:10 < ianthius> also when it complains that the feerate is below the minumum whose minimum is that the requestors? 23:47 -!- danielaof [~danielaof@45.32.248.113] has joined #c-lightning 23:52 -!- danielaof [~danielaof@45.32.248.113] has quit [Quit: This computer has gone to sleep]