--- Log opened Fri Sep 11 00:00:15 2020
00:00 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
00:08 < rusty> cdecker, zmnscpxj: https://github.com/ElementsProject/lightning/pull/4039
00:14 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
00:28 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
00:29 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
00:32 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds]
00:50 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
00:54 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit]
01:34 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 240 seconds]
01:52 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
01:52 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
02:37 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
02:49 -!- jonatack [~jon@192.113.14.109.rev.sfr.net] has joined #c-lightning
02:50 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
02:50 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
02:59 -!- vincenzopalazzo [~vincent@host-82-60-201-14.retail.telecomitalia.it] has joined #c-lightning
03:19 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
03:23 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds]
03:45 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
03:51 < rusty> darosior: OK, test fixed up. And since you and cdecker complained, reduced timeout to 1 minute
03:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
04:04 < rusty> OK, now I have added a proxy to reach those Tor nodes, and the 1 minute timeout PR. Let's try again!
04:06 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
04:14 < rusty> It's slow to connect to all of them, but it's not making my machine sweat at all.
04:39 -!- jonatack [~jon@192.113.14.109.rev.sfr.net] has quit [Ping timeout: 240 seconds]
04:41 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
04:44 -!- jasan [~jasan@dynamic-bband-83.194-212-253.telekom.sk] has quit [Ping timeout: 256 seconds]
04:52 -!- vincenzopalazzo [~vincent@host-82-60-201-14.retail.telecomitalia.it] has quit [Quit: Leaving]
05:01 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
05:14 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
05:17 -!- sr_gi [~sr_gi@static-240-45-224-77.ipcom.comunitel.net] has quit [Read error: Connection reset by peer]
05:17 -!- sr_gi [~sr_gi@static-240-45-224-77.ipcom.comunitel.net] has joined #c-lightning
05:28 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
05:32 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
07:00 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
07:02 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
07:02 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
07:06 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning
07:07 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 256 seconds]
07:17 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
07:29 -!- nothingmuch [~nothingmu@unaffiliated/nothingmuch] has joined #c-lightning
08:38 -!- dr-orlovsky [~dr-orlovs@31.14.40.19] has joined #c-lightning
10:00 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
10:01 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
10:01 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection]
10:02 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
12:33 -!- reallll is now known as belcher
12:41 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
14:05 -!- az0re [~az0re@gateway/tor-sasl/az0re] has joined #c-lightning
14:13 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
14:14 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
15:36 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds]
15:37 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
15:59 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
16:01 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
16:05 -!- grubles [~unknown@unaffiliated/grubles] has quit [Ping timeout: 256 seconds]
16:19 < az0re> So I have two nodes, A and B. A has open channels and only announces an onion address. Node B has bootstrapped successfully, but `lightning-cli ping ` returns "Unknown peer". Why?
16:21 < az0re> Announcing only an onion address doesn't seem to be the issue. BirdIsTheWord seems to work fine that way.
16:27 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
16:41 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
16:43 < az0re> Re-asking for zmnscpxj: So I have two nodes, A and B. A has open channels and only announces an onion address. Node B has bootstrapped successfully, but `lightning-cli ping ` returns "Unknown peer". Do you know why that might be?
16:43 < zmnscpxj> you got disconnected from A. check `listpeers` and see if it is "connected": true
16:44 < az0re> Do I have to explicitly connect to A first?
16:44 < zmnscpxj> yes
16:44 < zmnscpxj> haha
16:44 < az0re> I am trying to test that people can route payments through me; i.e. that I am reachable
16:44 < zmnscpxj> you have Tor
16:44 < zmnscpxj> when others are routing through you, they do not have to connect directly
16:44 < az0re> I guess that is not the right way to test it
16:45 < zmnscpxj> they just have to connect to whoever they have channels with
16:45 < az0re> Oh that makes sense
16:45 < zmnscpxj> the right way to test it is to go enjoy the weekend, then on Monday try `listforwards`
16:46 < az0re> There is otherwise no way to test that I am reachable? :)
16:46 < zmnscpxj> if you are online and your peers are online and you can connect to them, you *Are* reachable
16:46 < zmnscpxj> now you have to compete in the LN fee market wahaha
16:47 < az0re> Oh, so it doesn't even matter if I can be reached through my announce address? As long as I have an open connection to my peers I am reachable?
16:47 < zmnscpxj> Yes
16:47 < az0re> Got it
16:47 < zmnscpxj> Some routing nodes do not even announce
16:47 < az0re> Yes, I am thinking that might be an option for me
16:48 < az0re> What's odd is that when I do `listchannels` on node B I do not find node A's pubkey
16:48 < zmnscpxj> A and B have a channel?
16:49 < zmnscpxj> You did `listchannels `?
16:49 < az0re> Oh, nevermind
16:49 < az0re> It appears now
16:50 < az0re> It must have still been downloading the channel list when I was checking last
16:50 < zmnscpxj> if the channel is fairly new then it might not be announced yet
16:50 < zmnscpxj> yes
16:50 < zmnscpxj> could be
16:50 < az0re> No, no channel between A and B; the point was just to test that node A is reachable
16:50 < az0re> Thanks a lot, zmnscpxj
16:50 < az0re> Send me a /msg with a donation invoice
16:51 < az0re> You've been super helpful these last few days
16:51 < zmnscpxj> if you want to check it is reachable over payment channels, you could try `getroute` to A and then `sendpay` with a random hash
16:51 -!- grubles [~unknown@unaffiliated/grubles] has joined #c-lightning
16:52 < zmnscpxj> if it errors at A then it reached it, A just did not know the hash
16:52 < az0re> With a random hash, meaning, that it is not actually a valid payment
16:52 < zmnscpxj> though that is a bit low-level
16:52 < zmnscpxj> yes
16:52 < az0re> Right
16:52 < az0re> Good idea
16:52 < zmnscpxj> A will respond with INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS, though you might have to look up the exact number on BOLT spec
16:52 < zmnscpxj> bit low-level
16:53 < az0re> Cool, that's fine; it's easy to tell if it failed to get a route or some more arcane error message
16:53 < zmnscpxj> `sendpay` is a lot more low-level than `pay`, though
16:53 < az0re> Understood
16:56 < az0re> BTW, two more questions: 1) What sort of infrastructure/scripts around lightning-cli do you have? Anything you can share that is relevant to operating a node? 2) is there a way to set a scaling fee? I mean that I would generally like my channels balanced. If a payment would bring my channels more in balance, I want to offer them zero fees. Otherwise, I would like the fee to scale according to how much more unbalanced the payment would make
16:56 < az0re> my channels. Is this possible?
16:57 < zmnscpxj> try looking in the lightningd/plugins repo https://github.com/lightningd/plugins
16:57 < zmnscpxj> You want jitrebalance in particular
16:58 < az0re> Awesome, I'll check it out. Thanks.
16:59 < zmnscpxj> scaling fees is theoretically possible but I do not know if it is actually implemented by any plugins yet
17:00 < az0re> I see
17:01 < zmnscpxj> I think the issue with scaling fees is that if done incorrectly, it leaks that your channel state has changed
17:01 < zmnscpxj> and you spam the network with lots of channel_updates
17:32 < az0re> I see. Probably better to split the fee schedule into bins and limit fee updates to when the balance goes into a new bin
17:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:47 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
17:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:57 -!- mode/#c-lightning [+o rusty] by ChanServ
17:58 -!- rusty changed the topic of #c-lightning to: Next meeting here @8PM UTC Monday 21 Sep! Chat about the C-lightning implementation: https://github.com/ElementsProject/lightning https://lists.ozlabs.org/listinfo/c-lightning Current Version: https://github.com/ElementsProject/lightning/releases/tag/v0.9.1rc2 Logs at http://gnusha.org/c-lightning/
18:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
18:05 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
18:06 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Read error: Connection reset by peer]
18:08 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
18:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has left #c-lightning []
18:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zzgbwiizjmpgirfq] has joined #c-lightning
18:37 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
18:44 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
20:35 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Read error: Connection reset by peer]
20:36 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
20:46 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 244 seconds]
20:53 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Read error: Connection reset by peer]
20:54 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
22:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
22:27 < rusty> grubles: thanks for openbsd test, can you check fix?
22:30 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
22:31 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
23:17 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
--- Log closed Sat Sep 12 00:00:16 2020