--- Log opened Fri Nov 08 00:00:03 2019 01:27 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 240 seconds] 01:30 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 01:39 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 01:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit] 01:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 01:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Client Quit] 02:08 -!- lxer [~lx@ip5f5bd65f.dynamic.kabel-deutschland.de] has joined #c-lightning 02:18 < lxer> what is the best place to comment on BOLT-12? 02:19 < willcl_ark> Is C-Lightning _always_ using the legacy hop_data payload format, or does it depend on which type of peer we are connecting to? 02:49 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection] 02:49 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection] 02:49 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning 02:49 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning 02:55 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 268 seconds] 02:59 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 03:09 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 268 seconds] 03:14 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 03:59 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e8f4:48b5:f75a:b75f] has joined #c-lightning 04:05 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e8f4:48b5:f75a:b75f] has quit [Quit: Sleep mode] 04:08 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e8f4:48b5:f75a:b75f] has joined #c-lightning 04:10 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 240 seconds] 04:17 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 05:00 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e8f4:48b5:f75a:b75f] has quit [Quit: Sleep mode] 05:04 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning [] 05:04 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning 05:52 < fiatjaf> lxer, mailing list 05:53 < fiatjaf> willcl_ark, I think it always creates invoices with route hints, if that's what you're asking. it chooses one channel randomly to include in the route hints as far as I know. 05:53 < fiatjaf> lxer, reply to rusty's email there 05:54 < fiatjaf> darosior, is it possible for plugins to be able to send arbitrary messages to peers? using "odd" message types? 05:54 < fiatjaf> (it should be ok to be odd) 05:54 < willcl_ark> Thanks fiatjaf. I am actually wodnering as I am fiddling with the onion, and I just noticed that we are using 'legacy' vs 'TLV' type payload, and if that was always going to be the case for C-Lightning, or whether I might need to make two decoders... 05:55 <@cdecker> willcl_ark: working on a `createonion` and `sendonion` PR that allows users to specify the payload they'd like. In combination with the `htlc_accepted` hook in plugins you could then start doing some magic trickery using TLVs 05:55 < fiatjaf> willcl_ark, it's using legacy for now, but TLV will be implemented 05:55 < willcl_ark> cdecker: very exciting! Richard had to make some changes to the onion tool, but we now have it working too! 05:55 <@cdecker> willcl_ark: we're slowly migrating away from legacy since TLV is way more flexible 05:56 < willcl_ark> oh nooooo! :) oh well, I will stick with legacy for now, but makeing a TLV decoder will not be difficult. 05:57 < fiatjaf> cdecker, what do you mean? how am I going to replace the onion when forwarding an HTLC? 06:01 <@cdecker> fiatjaf: no, intermediate nodes will likely not have the ability to replace the onion (they don't know where the original onion was going), the `htlc_accepted` remark was mostly meant for the recipient receiving some custom payload 06:02 < fiatjaf> hmmm, right 06:04 <@cdecker> Though we could also start defining some extra stuff in the 12 bytes payload padding on the legacy format 06:05 <@cdecker> We can do some really interesting things once we have TLV support in payments we forward as well 06:24 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 06:34 < m-schmoock> cdecker: darosior: I finally finished PR https://github.com/lightningd/plugins/pull/22 drain/fill/setbalance from my side 06:35 < m-schmoock> sorry for the hard delay, i now have a bit more time also frequently 07:02 < darosior> m-schmoock: great ! Happy to see that you finally stuff the stuff ! 07:04 < darosior> Will stuff soon 07:04 < darosior> test* 07:09 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning 07:14 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 07:17 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning 07:19 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 07:40 <@cdecker> That's great news m-schmoock, I'll take a look asap 08:18 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 08:22 < willcl_ark> fiatjaf: thank you for extract_private_key_from_hsm_secret.py ! 08:34 < m-schmoock> darosior: walk the walk or talk the talk ... or stuff the stuff? :D 08:35 < m-schmoock> cdecker: the drain plugin supports auto chunking and other features the make the rebalance more reliable. is it possible for a plugin to use another plugin (i.e. the JIT rebalance to use drain?) 08:45 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e8f4:48b5:f75a:b75f] has joined #c-lightning 08:46 -!- shesek [~shesek@unaffiliated/shesek] has joined #c-lightning 08:51 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has quit [Ping timeout: 276 seconds] 08:55 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 08:57 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 09:25 -!- shesek [~shesek@unaffiliated/shesek] has quit [Ping timeout: 240 seconds] 09:56 <@cdecker> m-schmoock: sure, plugins have access to the JSON-RPC, and plugins can expose JSON-RPC commands, so plugins can use plugins 09:57 <@cdecker> The major downside is that we currently don't have any concept of a dependency between plugins 10:55 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has joined #c-lightning 10:56 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning 11:12 < m-schmoock> yes, i was thinking about the same thing 11:13 < m-schmoock> because as this plugin library grows, we will see to have more and more common functionality that we dont want to be duplicated and maintained in different states 11:13 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Remote host closed the connection] 11:15 < darosior> The dependency could be a try: RPC call except: ... in the @init 11:29 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e8f4:48b5:f75a:b75f] has quit [Quit: Sleep mode] 11:32 < m-schmoock> hm, yes for an optional plugin dependency thats okay 12:07 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 240 seconds] 12:08 < darosior> Yeah or execpt: raise("Dependency not satisfied") 12:08 < darosior> for a mandatory one 12:12 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning 12:20 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 12:29 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning 12:36 < darosior> Did anyone experience a way lower rate of forwards after upgrading to v0.7.3 ? 12:36 < darosior> `for i in $(lightning-cli listforwards |jq -r .forwards[].resolved_time);do date -d @$i;done` 12:40 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning 12:44 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds] 12:59 -!- reallll is now known as belcher 13:09 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning [] 13:10 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning 13:44 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 14:16 -!- jtimon [~quassel@22.133.134.37.dynamic.jazztel.es] has joined #c-lightning 14:54 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 14:55 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning 14:56 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 15:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 15:52 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 16:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 18:08 -!- lxer [~lx@ip5f5bd65f.dynamic.kabel-deutschland.de] has quit [Ping timeout: 265 seconds] 19:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 19:31 -!- m-schmoock [~will@schmoock.net] has quit [Remote host closed the connection] 19:48 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 20:17 -!- jtimon [~quassel@22.133.134.37.dynamic.jazztel.es] has quit [Ping timeout: 240 seconds] 20:30 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 260 seconds] 21:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has left #c-lightning [] 21:24 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-nfufoseoysnzgsxq] has joined #c-lightning 21:25 -!- lowentropy [~lowentrop@gateway/tor-sasl/lowentropy] has quit [Ping timeout: 260 seconds] 21:27 -!- lowentropy [~lowentrop@gateway/tor-sasl/lowentropy] has joined #c-lightning 21:45 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e8f4:48b5:f75a:b75f] has joined #c-lightning 22:00 -!- michaelfolkson [~textual@2a00:23c5:be04:e501:e8f4:48b5:f75a:b75f] has quit [Quit: Sleep mode] 22:24 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit] 22:36 -!- qubenix [~qubenix@66.172.11.228] has joined #c-lightning 22:50 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit] 23:06 -!- qubenix [~qubenix@66.172.11.228] has joined #c-lightning 23:41 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning --- Log closed Sat Nov 09 00:00:03 2019