--- Day changed Mon Aug 27 2018 00:59 -!- bitonic-cjp [~bitonic-c@2001:981:9573:1:9475:e1ff:fe44:6a7d] has joined #c-lightning 01:17 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-yhprawovioqnueze] has joined #c-lightning 01:40 -!- _bitonic-cjp [~bitonic-c@89.200.0.111] has joined #c-lightning 01:40 -!- _bitonic-cjp [~bitonic-c@89.200.0.111] has quit [Read error: Connection reset by peer] 01:41 -!- bitonic-cjp [~bitonic-c@2001:981:9573:1:9475:e1ff:fe44:6a7d] has quit [Remote host closed the connection] 01:41 -!- _bitonic-cjp [~bitonic-c@2001:981:9573:1:4c5:9aff:fe7c:24ab] has joined #c-lightning 01:41 -!- _bitonic-cjp [~bitonic-c@2001:981:9573:1:4c5:9aff:fe7c:24ab] has quit [Client Quit] 01:42 -!- bitonic-cjp [~bitonic-c@2001:981:9573:1:4c5:9aff:fe7c:24ab] has joined #c-lightning 01:42 < booyah> can LN server and BTC fullnode be used together sort-of trustless? 01:43 < booyah> how normally LN uses BTC fullnode, via RPC or ZMQ or both? can it be configured that if LN would become malicious (hacked) then it can not spent bitcoin core wallet funds or damage it? limit set of RPC to maybe announce raw tx (generated in LN) and so on? 01:44 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 01:45 -!- Zenton [~user@195.235.96.150] has joined #c-lightning 02:11 -!- Zenton [~user@195.235.96.150] has quit [Changing host] 02:11 -!- Zenton [~user@unaffiliated/vicenteh] has joined #c-lightning 02:11 -!- Zenton is now known as vicenteH 02:12 -!- vicenteH is now known as Zenton 02:13 -!- Guest26637 [~root@45.32.59.211] has joined #c-lightning 02:37 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Remote host closed the connection] 02:37 -!- Zenton [~user@unaffiliated/vicenteh] has joined #c-lightning 02:43 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 02:44 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 02:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 02:55 -!- bitonic-cjp [~bitonic-c@2001:981:9573:1:4c5:9aff:fe7c:24ab] has quit [Remote host closed the connection] 02:55 -!- _bitonic-cjp [~bitonic-c@2001:981:9573:1:4c5:9aff:fe7c:24ab] has joined #c-lightning 03:23 -!- _bitonic-cjp [~bitonic-c@2001:981:9573:1:4c5:9aff:fe7c:24ab] has quit [Remote host closed the connection] 03:23 -!- _bitonic-cjp [~bitonic-c@2001:981:9573:1:4c5:9aff:fe7c:24ab] has joined #c-lightning 05:03 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 256 seconds] 05:04 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 05:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 252 seconds] 05:23 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 05:46 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 06:01 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 06:33 < Chris_Stewart_5> So it seems if I run c-lightning log enough it inevitably ends up at a state where 06:33 < Chris_Stewart_5> 1.) I can connect and open a channel with an eclair node 06:33 < Chris_Stewart_5> 2.) That channel is immediately closed due to not being able to negotiate fees 06:54 < molz> Chris_Stewart_5, probably it also has something to do with "Data loss protection"? https://medium.com/@ACINQ/adding-data-loss-protection-to-eclair-598c62494096 06:54 < molz> which c-lightning doesn't have yet? 06:55 < molz> https://github.com/ElementsProject/lightning/issues/1634 07:32 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 07:42 < Chris_Stewart_5> molz: I don't think so. It seems that c-lightning is unilaterally closing immediately after my funding tx gets confirmed on chain https://pastebin.com/21HTDcTK 07:43 < Chris_Stewart_5> this is happening with the new RC and 0.6 as well 07:51 < Chris_Stewart_5> molz: Log from the eclair point of view : https://pastebin.com/4fH8zewg 07:53 <@cdecker> molz: dataloss_protection has been merged last week into `master` and will be rolled out in 0.6.1 :-) 08:00 < molz> cdecker, ah i see... so why's c-lightning still closing channels ? 08:13 < Chris_Stewart_5> ^ 08:17 -!- _bitonic-cjp [~bitonic-c@2001:981:9573:1:4c5:9aff:fe7c:24ab] has quit [Quit: Leaving] 08:27 -!- renepickhardt [577bc4c3@gateway/web/freenode/ip.87.123.196.195] has joined #c-lightning 08:39 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 08:40 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 08:52 < molz> Chris_Stewart_5, i updated my c-lightning node (testnet) to "version": "v0.6.1rc1", got my eclair mobile to open a channel to it, it seems fine 09:01 < Chris_Stewart_5> molz: So it seems that my node always just converges to this weird state, even if i blow away my c-lightning data dirs 09:01 < Chris_Stewart_5> it is just a matter of when, not if. The situation i am talking about is c-lightning funding a channel to eclair 09:02 < Chris_Stewart_5> if you want to try that, just connect to our testnet node: 0338f57e4e20abf4d5c86b71b59e995ce4378e373b021a7b6f41dabb42d3aad069@ln.test.suredbits.com 09:02 < Chris_Stewart_5> (it's an eclair node) 09:02 < molz> ok let me try 09:05 < Chris_Stewart_5> after awhile, if fundchannel fails, i cannot re-connect to my node. Maybe there is some ban logic I don't know about but we at least shouldn't try to connect forever: https://github.com/ElementsProject/lightning/issues/1883 09:17 < renepickhardt> is there a minimal channel balance in c-lightning? I remember 20k satoshi but I can't find it right now 09:26 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 09:33 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 09:33 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 09:34 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 09:37 < molz> renepickhardt, 20k sat is LND 09:41 < renepickhardt> c -lightning has no min? 09:42 < renepickhardt> if I open a channel from c-lightning with an lnd node and the capacity is smaller will this work? I need to take this in consideration for the c-lightning autopilot 09:47 < molz> we used to be able to open a channel with just 2k sat on mainnet :D 09:47 < molz> now i'm testing this and it hangs: ~$ lightning-cli fundchannel 03ac30186e1568957d98ba4aa459a7455c415c7e88b0ab8cb57dddbea839f970d1 5000 09:47 < molz> i think the min is probably 54600 sat 09:48 < molz> because the dust level is 546 sat 09:50 < molz> oh it's very weird, it still says a channel is opened with "msatoshi_total": 5000000 but there's no TXID 09:50 < molz> i think i've seen this error before 10:13 -!- renepickhardt [577bc4c3@gateway/web/freenode/ip.87.123.196.195] has quit [Ping timeout: 252 seconds] 10:40 -!- Zenton [~user@unaffiliated/vicenteh] has quit [Ping timeout: 272 seconds] 11:04 -!- renepickhardt [577bc4c3@gateway/web/freenode/ip.87.123.196.195] has joined #c-lightning 11:33 -!- renepickhardt [577bc4c3@gateway/web/freenode/ip.87.123.196.195] has quit [Ping timeout: 252 seconds] 11:40 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 11:41 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 12:33 -!- Zenton [~user@unaffiliated/vicenteh] has joined #c-lightning 13:03 -!- farmerwampum [~farmerwam@104.129.29.18] has quit [Ping timeout: 272 seconds] 13:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 244 seconds] 13:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 13:54 < Chris_Stewart_5> molz: Ooh how did you get the hanging error? 13:54 < Chris_Stewart_5> molz: Note, i've experienced that on a simple connect command, there is something weird going on with the hanging stuff 13:54 < molz> Chris_Stewart_5, it's in "listpeers" 13:55 < Chris_Stewart_5> molz: Hmm, the weird rpc client hanging doesn't happen to you on every subsequent rpc command after failing to fund a channel? 13:55 < molz> it's gone from my listpeers now, i think i had this before 13:56 < molz> Chris_Stewart_5, this only happens when i try to fund a channel with dust amounts 13:57 < Chris_Stewart_5> Interesting, i tried to fund with 100000 and got the same behavior. 13:57 < Chris_Stewart_5> molz: I pasted the logs over in the eclair gitter if you want to see what c-lightning saw: https://gitter.im/ACINQ/eclair 13:58 < Chris_Stewart_5> it's the last message, this line i believe: 13:58 < Chris_Stewart_5> 2018-08-27T13:51:30.421Z lightningd(3331): lightning_channeld-0338f57e4e20abf4d5c86b71b59e995ce4378e373b021a7b6f41dabb42d3aad069 chan #2: Setting REMOTE feerate to 313784 14:00 < Chris_Stewart_5> which seems ! 14:03 < molz> hm.. yea i think sstone is right, testnet fees have been crazy 14:37 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 244 seconds] 14:45 -!- renepickhardt [577bc4c3@gateway/web/freenode/ip.87.123.196.195] has joined #c-lightning 15:00 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning 15:01 -!- copumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Ping timeout: 240 seconds] 15:28 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 15:41 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 276 seconds] 15:44 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 16:00 -!- renepickhardt [577bc4c3@gateway/web/freenode/ip.87.123.196.195] has quit [Ping timeout: 252 seconds] 17:03 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 244 seconds] 17:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:05 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 17:40 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds] 17:55 -!- wraithm [~wraithm@unaffiliated/wraithm] has joined #c-lightning 21:49 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 244 seconds] 21:49 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 21:51 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 22:08 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 22:57 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 23:20 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 23:26 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 268 seconds]