--- Log opened Sun Sep 20 00:00:23 2020 00:20 -!- az0re [~az0re@gateway/tor-sasl/az0re] has quit [Remote host closed the connection] 00:49 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection] 00:49 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning 00:51 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning 01:01 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 02:04 -!- kexkey [~kexkey@89.36.78.166] has quit [Ping timeout: 240 seconds] 03:08 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 265 seconds] 03:10 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 03:16 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 03:59 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 04:00 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 04:13 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 246 seconds] 05:06 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 05:54 -!- DeanWeen [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning 05:56 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds] 06:07 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 260 seconds] 06:34 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has quit [Ping timeout: 240 seconds] 06:38 -!- reallll is now known as belcher 06:40 -!- k3tan [~pi@gateway/tor-sasl/k3tan] has joined #c-lightning 06:56 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has joined #c-lightning 07:12 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer] 07:12 -!- sr_gi [~sr_gi@static-80-160-230-77.ipcom.comunitel.net] has joined #c-lightning 07:18 -!- liberliver [~Thunderbi@144.49.211.130.bc.googleusercontent.com] has quit [Ping timeout: 260 seconds] 07:38 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning 07:48 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 07:52 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 07:52 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 08:55 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has joined #c-lightning 09:14 -!- Victor_sueca is now known as Victorsueca 10:43 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has quit [Remote host closed the connection] 10:45 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 11:36 < az0re> I'm trying to fund a channel to another node, and get "local/remote feerates are too different: remoteFeeratePerKw=253 localFeeratePerKw=11493". I know this is for #lnd, but it's possible (probable?) the other end is running lnd. Is this a known issue? Is there a known workaround? 11:37 < az0re> Oops, s/I know this is for #lnd, but i/I/ 11:43 < darosior> hmm looks like it's a testnet node 11:44 < az0re> It's definitely a mainnet node; at least I can connect to it on the mainnet 11:44 < az0re> and it's on 1ml and graph.lndexplorer.com 11:44 < az0re> And it has a bunch of public channels 11:46 < az0re> Do you which part of the source is relevant to the feerate negotiation that's failing here? 11:46 < az0re> Do you know* 11:54 < darosior> Then you should definitely try to reach the operator (don't paste the id here): their fee estimator is broken and that could be bad 11:54 < az0re> Good to know 11:54 < darosior> Which part of the source ? Do you mean the source code ? Our or LND's ? 11:54 < az0re> c-lightning's 11:55 < darosior> Sure, but don't modify it you can just use --ignore-fee-limits for this usecase (you should not though :p) 11:55 < az0re> I'd still like to better understand how it works and what exactly failed 11:55 < az0re> What are the implications? 11:56 < az0re> I'm still not clear on precisely which fee is being negotiated here--the fee that will be paid for the commitment transaction? 11:56 < az0re> (the implications of ignoring fee limits, that is) 12:05 < darosior> Oh. Just realized that's actually LND's log. *You* have the broken estimator 12:06 < az0re> Orly? 12:06 < darosior> Are you using bitcoind as your backend 12:06 < az0re> Yes 12:06 < darosior> does estimatesmartfee errors ? 12:07 < az0re> "message": "Unknown command 'estimatesmartfee'" 12:07 < darosior> wtf 12:07 < darosior> Ah 12:07 < az0re> Using c-lightning from git 12:08 < az0re> Followed all instructions 12:08 < darosior> I mean on bitcoind 12:08 < az0re> Oh 12:08 < az0re> :) 12:08 < darosior> bitcoin-cli estimatesmartfee 3 12:08 < darosior> "What are the implications?" => Not being able to get a transaction confirmed in a timely manner, you may lose funds if that's an HTLC claim or worse a punishment 12:09 < darosior> "I'm still not clear on precisely which fee is being negotiated here--the fee that will be paid for the commitment transaction?" => Yep 12:09 < az0re> I get: 12:09 < az0re> { 12:09 < az0re> "feerate": 0.00043980, 12:09 < az0re> "blocks": 3 12:09 < az0re> } 12:09 < az0re> No errors... 12:09 < darosior> Ok, weird that they tell you that then 12:09 < darosior> Maybe you run with anchors ? I don't have looked at our implem yet but maybe we advertise 253perkw in this case 12:10 < az0re> FYI I have no trouble opening or receiving channels with any other nodes I've tried so far 12:10 < darosior> Ah 12:10 < az0re> Re: implications -- I see. Thanks. 12:11 < az0re> I don't know what anchors are; I've definitely not taken any positive action to run with anchors. 12:11 < darosior> Ok, yeah so as you pointed out they probably are broken somehow 12:11 < az0re> BTW, I'm sure it's in one of the BOLTs and I should just RTFM but who pays for the commitment transaction fee? 12:11 < darosior> Opener 12:12 < az0re> In the case of a mutual close 12:12 < az0re> OK 12:12 < az0re> I will try to contact the operators of that node and encourage them to investigate 12:13 < az0re> Thanks for the advice 12:38 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 260 seconds] 13:49 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 14:09 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 15:09 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds] 15:11 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning 15:16 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has joined #c-lightning 15:17 < polydin> hey y'all can anybody explain line 654 in lightningd/subd.c of the codebase? 15:18 < polydin> is it referencing a function? 15:18 < polydin> function named subd(..)? 15:19 < polydin> is it a constructor for 'struct subd' ? 15:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 260 seconds] 16:00 -!- polydin [~george@rrcs-71-78-170-67.sw.biz.rr.com] has quit [Quit: Leaving] 16:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning [] 16:12 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning 16:14 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds] 16:41 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:43 < zmnscpxj_> polydin: function at line 139 in lightningd/subd.c 17:44 < zmnscpxj_> it is a launcher for a subdaemon, and returns the pid. 17:44 < zmnscpxj_> the `struct subd` is constructed by `new_global_subd` or `new_channel_subd`. 17:45 < zmnscpxj_> which uses the basic `new_subd`. 19:50 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds] 20:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds] 20:38 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 22:39 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 23:39 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning 23:43 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds] 23:46 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning 23:54 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning --- Log closed Mon Sep 21 00:00:24 2020