--- Log opened Tue Feb 18 00:00:44 2020
00:56 -!- mimmo [~user@2001:b07:ac9:6525:786a:8271:5201:35a8] has joined #c-lightning
00:57 -!- mimmo [~user@2001:b07:ac9:6525:786a:8271:5201:35a8] has quit [Client Quit]
01:06 -!- lxer [~lx@ip5f5bf497.dynamic.kabel-deutschland.de] has joined #c-lightning
02:01 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
02:01 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
02:31 -!- Amperture [~amp@65.79.129.113] has quit [Remote host closed the connection]
04:45 -!- Funky0x [~Funky0x@2a02:8070:a9e:8200:3c8e:16fc:a6dd:9f7f] has joined #c-lightning
04:45 -!- Funky0x [~Funky0x@2a02:8070:a9e:8200:3c8e:16fc:a6dd:9f7f] has quit [Client Quit]
05:05 -!- rafalcpp [~racalcppp@ip-178-211.ists.pl] has joined #c-lightning
05:13 -!- kexkey [~kexkey@37.120.205.238] has joined #c-lightning
05:29 < lxer> Is it possible to add plugins to the config file ? 
05:37 < zmnscpxj> it is possible to add a directory containing plugins to the config file
05:37 < zmnscpxj> which could be almost the same
05:38 < zmnscpxj> plugin-dir=/path/to/directory/
05:40 < lxer> thanks. So I guess the files should not be in a subdirectory then.  
05:41 < lxer> using symlinks could fix this.
05:44 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
06:30 < vasild> lxer: its also possible to add individual plugins: https://github.com/ElementsProject/lightning/blame/master/doc/lightningd-config.5.md#L399
06:31 < vasild> I have not tried this myself but I guess you give it the path to the executable file
06:37 < lxer> I found a even easier solution: simply make a symlink from ~/.lightning/plugins/ to the plugin file. no config needed. 
06:38 < zmnscpxj> well the intent is actually to just copy the plugin executable in the plugins directory, so ---
06:38 < zmnscpxj> hard and softlinking works as well
06:43 < lxer> I always like the Nginx style: 'sites-enabled', 'sites-available'. So I do something similar for the plugins.
06:58 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Quit: Leaving]
07:56 -!- mdunnio [~mdunnio@104-182-134-195.lightspeed.cicril.sbcglobal.net] has joined #c-lightning
07:59 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #c-lightning
08:08 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Quit: jb55]
08:28 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
08:28 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
09:04 -!- mdunnio [~mdunnio@104-182-134-195.lightspeed.cicril.sbcglobal.net] has quit [Remote host closed the connection]
09:52 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
10:09 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
10:09 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
10:44 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
10:53 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection]
11:44 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
11:45 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
12:00 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
12:12 < vasild> rusty: wrt https://github.com/ElementsProject/lightning/pull/3535#issuecomment-587241778 -- maybe I miss something but removing json_to_double() implies changing the external interface. For example, to ask users to type 3150000 instead of 3.15
12:14 < vasild> I changed the code to work internally with integers, but still leave the external jsons to contain e.g. 3.15 (and work with 3150000 internally all over the place)
12:17 < rusty> vasild: yes, leave interface.
12:18 < vasild> will push the patch shortly
12:28 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
12:29 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
12:41 < willcl_ark> How does C-Lightning determine which python interpreter (or venv) to use for a plugin? I have no issues with my own setup (using pyenv and .python-version file) but I want to make sure my plugin can work for people not using such a setup...
12:43 < vasild> willcl_ark: as far as I know plugins are just executable files that are, well... executed and there is no special python magic around it.
12:44 < vasild> you could even have a shell script (#!/bin/sh) as a plugin
12:44 < willcl_ark> vasild: hmmm, I wonder if adding a shebang to the top with the correct python interpreter path would fix it
12:44 < vasild> what is the very first line of your python plugin?
12:44 < willcl_ark> OK thanks
12:45 < willcl_ark> its currently just #!/usr/bin/env python3
12:45 < willcl_ark> I think if I get the user to customise that to the right venv path, it will work
12:47 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
12:48 < vasild> should
12:48 < willcl_ark> :P its not ideal though... sure I can find a neater way
12:58 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has quit [Ping timeout: 260 seconds]
13:05 -!- instagibbs [~instagibb@pool-71-178-191-230.washdc.fios.verizon.net] has joined #c-lightning
13:17 -!- alko89 [~alko@cpe-85-10-28-138.static.amis.net] has joined #c-lightning
14:10 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
14:20 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
14:49 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning
14:56 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
14:57 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
15:01 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
15:18 -!- kexkey [~kexkey@37.120.205.238] has quit [Read error: Connection reset by peer]
15:34 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Ping timeout: 240 seconds]
15:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
16:06 -!- lxer [~lx@ip5f5bf497.dynamic.kabel-deutschland.de] has quit [Ping timeout: 265 seconds]
16:11 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
16:27 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
16:28 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
17:21 -!- grubles_ [~blockhash@unaffiliated/grubles] has joined #c-lightning
18:18 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
18:19 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
18:35 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
18:58 <@niftynei> zmnscpxj_, i've got a 'pre-print' version of the revised interactive tx construction  (+ openchannel2) rfc draft up, i'd appreciate any comments or questions you've got on it https://github.com/niftynei/lightning-rfc/pull/1/commits/b58b8979394a74659211ae2ddb14768ce68bb95f
18:59 <@niftynei> i'm planning to get it re-implemented before opening a PR on the main rfc repo, but any feedback i can get on it now would be very useful
19:23 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
19:27 < rusty> niftynei: blacklist_podle needs the node_id, no?
19:28 < rusty> niftynei: signature needs to be defined, too.  Usual trick is to put node_id first, and sign has of rest of msg.
19:31 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
19:58 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.6]
19:58 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
20:25 -!- alko89 [~alko@cpe-85-10-28-138.static.amis.net] has quit [Ping timeout: 248 seconds]
20:26 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
20:30 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
20:57 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
21:25 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection]
21:52 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds]
21:58 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
22:45 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
22:46 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
23:34 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds]
23:34 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Quit: Leaving]
23:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
23:45 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
23:54 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
23:54 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
23:58 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
--- Log closed Wed Feb 19 00:00:45 2020