--- Log opened Sun Apr 14 00:00:45 2019 00:08 -!- m-schmoock [~will@schmoock.net] has joined #c-lightning 00:47 < d3spwn> i've been running c-lightning for a while now but it seems a bit lacking in features compared to lnd. am i wrong or is c-lightning meant for a different purpose? 00:52 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds] 01:37 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 01:52 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 268 seconds] 02:37 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 03:34 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 03:46 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 03:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 250 seconds] 04:39 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 246 seconds] 05:54 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 07:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 08:21 <@cdecker> d3spwn: what features are you looking for specifically? We mostly overlap 08:22 <@cdecker> And we prioritize depending on what users are asking for 08:42 < d3spwn> i'm just exploring lighning so i cant tell yet, but lnd can tell my my wallet seed for example 08:42 < d3spwn> i'm just wondering if they're targeted at different users/uses 08:52 < d3spwn> also i was wondering if it is possible to open a channel with x balance and have clightning deduct the tx fee from x instead of taking it from the wallet so i can use 100% of the wallet and not be left with dust 08:56 <@cdecker> d3spwn: yeah, the seed question comes up quite often 08:57 <@cdecker> We decided to not expose the seed just yet since it'd give the false impression that all you need to remember is the seed, whereas the channel state is also important 08:58 <@cdecker> With the seed you can recover on-chain funds, but you will not be able to recover or interact with the channels, making all those funds inaccessible 08:58 <@cdecker> So having users write down the seed gives a false sense of security imho, when really users need to be very careful with their node 08:59 < d3spwn> thats a good point, i hadn't thought about it like that 08:59 <@cdecker> As for opening a channel with all available funds that's supported. Just use `all` as amount and it'll make sure to use the maximum available (confirmed) amount 10:38 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 10:49 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 12:57 -!- face [~face@80.72.82.160.coresnet.bg] has quit [Ping timeout: 246 seconds] 13:10 -!- t0mix [~t0mix@78-141-123-99.dynamic.orange.sk] has joined #c-lightning 13:17 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 13:50 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 15:06 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 268 seconds] 15:15 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 15:22 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 15:30 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning 15:57 -!- face [~face@80.72.82.160.coresnet.bg] has joined #c-lightning 16:33 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 246 seconds] 16:56 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:09 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 256 seconds] 17:11 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 18:06 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...] 18:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 256 seconds] 18:28 -!- spinza [~spin@155.93.246.187] has joined #c-lightning 18:45 -!- khs9ne [~xxwa@unaffiliated/mn3monic] has quit [Ping timeout: 252 seconds] 21:22 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 21:43 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection] 21:43 < molz> hm why can't i use 'pay' to pay an invoice anymore? 21:44 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 21:55 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #c-lightning 21:56 < molz> hm ok this is an old version when 'pay' command was missing 21:56 < molz> so im trying to update and now i'm getting more errors 21:57 < molz> cc1: all warnings being treated as errors 21:57 < molz> : recipe for target 'common/cryptomsg.o' failed 21:58 < molz> ok .. 'make clean' 22:00 < molz> hm still same errors 22:06 -!- face [~face@80.72.82.160.coresnet.bg] has quit [Ping timeout: 240 seconds] 22:14 < molz> ok i couldn't get v0.7.0 to compile without errors but i could get master compiled ok, but then the node crashed when i restarted it 22:20 < molz> oh hey, restarted again and it seems fine 22:41 -!- face [~face@80.72.82.160.coresnet.bg] has joined #c-lightning 23:00 -!- face [~face@80.72.82.160.coresnet.bg] has quit [Ping timeout: 264 seconds] 23:03 -!- StopAndDecrypt_ [~StopAndDe@129.232.161.66] has joined #c-lightning 23:04 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 257 seconds] 23:31 -!- StopAndDecrypt_ [~StopAndDe@129.232.161.66] has quit [Ping timeout: 268 seconds] --- Log closed Mon Apr 15 00:00:45 2019