--- Log opened Mon Feb 17 00:00:41 2020
00:04 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Remote host closed the connection]
00:06 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
00:34 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: Quit]
00:52 -!- lxer [~lx@ip5f5bf497.dynamic.kabel-deutschland.de] has joined #c-lightning
01:10 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #c-lightning
01:13 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: Quit]
01:14 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #c-lightning
01:14 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
01:15 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
01:16 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
01:29 -!- mimmo [~user@2001:b07:ac9:6525:3479:8686:6e62:73a] has joined #c-lightning
01:41 < mimmo> Hello, I'm pretty new to c-lightning and I'm testing it by combining it with bitcoin and elements side-chain. I used to work in c/c++ 30 years ago. So I'm not fluent with it anymore. Is this the right place to submit newbie questions?
01:43 < lxer> you can try here. but it is not a very active channel.
01:45 < mimmo> thanks. What is the alternative without filling the git repository of silly questions?
01:47 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
01:48 < lxer> perhaps https://bitcoin.stackexchange.com  
01:49 < mimmo> Thanks!
01:50 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Ping timeout: 260 seconds]
01:54 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
01:54 -!- achow101 [~achow101@unaffiliated/achow101] has joined #c-lightning
01:55 < rusty> We like questions though!
01:58 < mimmo> Thanks rusty. I did all the tutorials in the elementsproject. When I started to read about the standalone mode for side chain the very first question I did to myself has been: my I use c-lightning with a standalone side-chain? 
02:01 < mimmo> I know that you can use c-lightning with liquid chain, which is anchored to bitcoin mainnet. But I have a use case where the side-chain has to be standalone.
02:07 < mimmo> I submitted this question as an issue in the c-lightning repo. cdecker and ZmnSCPxj told that I have to modify c-lightning code to make the standalone chain to be recognised by c-lighting. My I have a clue about all those details to be coded in the chainparams network[] struct? 
02:51 < lxer> I followed the manual for setting up Tor, but I keep getting permissions errors. https://dpaste.org/vhAW# . I can start tor as root, but then c-lightning can't access it. Any ideas on how to fix this?    
02:57 < rusty> mimmo: yes, that's where you'd add your new chain.
03:00 < rusty> lxer: yes, it's usually run as root.  c-lightning should use the control port (usually 9051).  I use 
03:00 < rusty> ControlPort 9051
03:00 < rusty> CookieAuthentication 1
03:00 < rusty> in /etc/tor/torrc
03:11 < lxer> but then I get this:  lightning_connectd: Connecting stream socket to Tor service: Connection refused
03:17 < mimmo> rusty: thanks. I'll try to understand how to create the genesis block and then the genesis blockhash to be added in the network struct.  
03:18 < lxer> you're creating your own alt-coin? 
03:20 < rusty> lxer: 'addr=autotor:127.0.0.1:9051' ?
03:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
03:21 < lxer> I have  addr=statictor:127.0.0.1:9051
03:21 < mimmo> lxer: yes. just to better understand this stuff 
03:22 < mimmo> lxer: do you already know how to generate the genesis block and its hash? It is required in the description of the network to be added to c-lightning sourc e code
03:33 < lxer> mimmo some years ago I used https://github.com/moonsbtt/AltcoinGenerator-1/blob/master/altcoin_generator.sh  I don't know if it still works. 
03:34 < mimmo> :-). I'll try it in the next few days
03:35 < mimmo> last update is feb 2018, so it should still work. Thanks so much for your help
03:55 -!- masterdonx2 [~masterdon@185.108.128.160] has quit [Ping timeout: 272 seconds]
03:58 -!- MasterdonX [~masterdon@42.0.30.151] has joined #c-lightning
04:09 < darosior> lxer: if you use a Debian-like add your user to the debian-tor group
04:10 < lxer> already did that
04:13 < darosior> Did you restart tor afterwards ?..
04:42 < mimmo> lxer: your hint worked. Thanks so much again
04:44 < lxer> ok. and don't forget that you need to have at least 2 active nodes. 
05:02 < lxer> after setting  --user and changing some folders, I finally got Tor working. except Lightning is giving a different message now https://dpaste.org/Ttyb
05:04 < mimmo> lxer: The script create 4 dockers :-) already connected...I learnt something today 
05:47 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has quit [Quit: jonatack]
05:52 < mimmo> exit
05:52 -!- mimmo [~user@2001:b07:ac9:6525:3479:8686:6e62:73a] has left #c-lightning ["ERC (IRC client for Emacs 25.2.2)"]
06:02 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
06:13 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #c-lightning
06:44 -!- sword_smith is now known as sword_smith_
06:45 -!- sword_smith_ is now known as sword_smith
06:57 < vasild> Now lightningd does not require an authentication for accessing the RPC via its unix file socket. Some primitive access control can be achieved by filesystem permissions, but that is far from flexible. What about adding an authentication? Have this been considered? Would it be nice to have? Then the socket file can be exposed in a public directory, like e.g. /tmp/.s.PGSQL.5432 or /tmp/mysql.sock. 
06:57 < vasild> Also, this would allow to expose the RPC via TCP, like what bitcoind does.
07:10 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit]
07:11 -!- qubenix [~qubenix@66.172.11.228] has joined #c-lightning
07:21 < darosior> Arf the txprepare crash was signaled like 6 hours after the release...
07:23 < darosior> vasild: I've planed to do that in 2019, that's the reason why I added this crappy rpc_command hook that rusty had to fix at least 3 times...
07:24 < darosior> I wanted to do that through a plugin but that's not possible, see https://github.com/ElementsProject/lightning/issues/3303 for rationale
07:25 < darosior> Maybe we can do it from lightningd
07:29 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit]
07:30 -!- qubenix [~qubenix@66.172.11.228] has joined #c-lightning
07:33 < vasild> good
07:44 < vasild> I am thinking about requiring a valid user/pass over the rpc socket (~/.lightning/bitcoin/lightning-rpc) before doing anything else.
07:44 < darosior> Just the same week we speak about mobile integration.. https://github.com/PISAresearch/wt_cli :-)
07:44 < vasild> that's a bit different than wallet lock/unlock (https://github.com/ElementsProject/lightning/issues/3303)
07:45 < darosior> But the backend doesn't seem to be open source..
07:46 < darosior> vasild: you mean at startup ?
07:46 < darosior> There is the hsm encryption for this specific case
07:46 < vasild> not at lightningd startup, but whenver somebody connects to the socket
07:46 < vasild> at the "startup" of each client connection :)
07:48 < darosior> Hmm I think cdecker and rusty were in favor of adding an optional auth field to JSONRPC
07:49 < darosior> requests
07:51 < vasild> that is a possibility also, I am not familiar with the protocol going over ~/.lightning/bitcoin/lightning-rpc, but if everything is jsonrpc requests, then an additional auth field would do. Maybe a bit suboptimal because if a client opens a connection and fires 10 requests then he would have to provide it for each request and lightningd would have to verify it also for each of the 10 requests.
07:53 < vasild> When a client connects to pgsql via /tmp/.s.PGSQL.5432 they provide their user/pass only once at the beginning, not for every SQL.
07:58 < darosior> An auth token doesn't require the user to enter its password n times
07:58 < darosior> And yeah only JSONRPC pass through the rpc socket
07:59 < darosior> The logic is in lightningd/jsonrpc and uses ccan/io
08:00 < vasild> good, this is details, I will come back to this later
08:07 <@cdecker> The upside of providing the auth data each time is that we can use cryptographic means to not only authenticate the caller (username+pass, API key, challenge+signature, ...) but we can also authorize the request itself (signature over the payloads, ...)
08:07 <@cdecker> A plugin could have username+password to create a session key valid for ~1h and tany subsequent call uses the session key
08:08 <@cdecker> That can also enable things like delegation quite nicely
08:14 < vasild> it is getting better and better :)
09:21 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection]
09:21 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning
09:37 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
09:37 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
10:01 < lxer> finally got Tor working. had to build from source and use the latest version.  
10:05 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]
10:07 -!- Funky0x [ralphdacs-@gateway/shell/matrix.org/x-pocatvhsloopjfkf] has quit [Ping timeout: 240 seconds]
10:15 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
10:15 < rafalcpp> is there a place where people gather and debug problems with LN payment not going, e.g. from  both sides?
10:18 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Read error: Connection timed out]
10:22 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
10:54 <@cdecker> rafalcpp: best to contact the implementations that are failing to cooperate, i.e., if c-lightning is involved feel free to ask here :-)
10:55 < rafalcpp> allright
10:55 < rafalcpp> (I dont use c-l right now, just asked in an active place)
10:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
10:57 <@cdecker> No problem ^^
11:11 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has quit [Quit: Leaving]
11:16 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Quit: Quit]
11:16 -!- x7268 [ralphdacs-@gateway/shell/matrix.org/x-hwyjtbttipcqjgtb] has joined #c-lightning
11:20 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
11:24 -!- while [~iam@69.61.169.171] has joined #c-lightning
11:25 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #c-lightning
11:27 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Client Quit]
11:37 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #c-lightning
11:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
11:47 -!- x7268 [ralphdacs-@gateway/shell/matrix.org/x-hwyjtbttipcqjgtb] has quit [Quit: killed]
11:50 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
12:02 -!- rafalcpp [~racalcppp@ip-178-211.ists.pl] has quit [Ping timeout: 265 seconds]
12:23 -!- mimmo [~user@2001:b07:ac9:6525:786a:8271:5201:35a8] has joined #c-lightning
12:29 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Ping timeout: 268 seconds]
12:30 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #c-lightning
12:32 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Client Quit]
12:33 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #c-lightning
12:33 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Client Quit]
12:35 -!- willcl_ark [~quassel@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #c-lightning
12:42 -!- dr-orlovsky [~dr-orlovs@ip216.ip-54-36-238.eu] has quit [Ping timeout: 240 seconds]
12:45 -!- dr-orlovsky [~dr-orlovs@ip216.ip-54-36-238.eu] has joined #c-lightning
13:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
14:49 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
15:21 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
15:24 -!- mimmo [~user@2001:b07:ac9:6525:786a:8271:5201:35a8] has quit [Quit: ERC (IRC client for Emacs 25.2.2)]
15:24 -!- mode/#c-lightning [+o rusty] by ChanServ
15:24 -!- rusty changed the topic of #c-lightning to:  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.8.1 Logs at http://gnusha.org/c-lightning/
15:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
15:56 -!- lxer [~lx@ip5f5bf497.dynamic.kabel-deutschland.de] has quit [Ping timeout: 268 seconds]
16:11 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
16:38 < k3tan> rusty: just with v0.8.1, i've git pull origin master (updating to v0.8.1), then make, make install. when i lightning-cli --version im still getting v0.8.0 - is this just me?
16:39 < rusty> k3tan: `which lightning-cli`?
16:40 < rusty> k3tan: works here: `/usr/local/bin/lightning-cli --version` gives v0.8.1
16:40 < k3tan> oooo
16:41 < k3tan> let me check
16:42 < k3tan> ok i seemed to have stuffed up somewhere
16:45 < k3tan> rusty: looking forward to meeting you at the bitcoin sydney meetup btw
16:49 < k3tan> during make i receive "mv: replace 'tools/headerversions', overriding mode 0755 (rwxr-xr-x)?"
16:53 < qubenix> k3tan: did you do `git checkout v0.8.1` after your `git pull...`? otherwise you're still on the old tag.
16:56 < k3tan> yeah im on the right tag
16:56 < k3tan> i think
16:58 < qubenix> i just updated mine from v0.8.0 to v0.8.1 and --version works correct for me. try `git status` to see what tag you're on.
17:00 < k3tan> ok sorted! works now. thank you rusty and qubenix 
17:54 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has left #c-lightning []
17:54 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-zkjjaoqsjfattawp] has joined #c-lightning
18:02 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
18:06 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
18:57 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection]
18:57 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has joined #c-lightning
19:25 -!- queip [~queip@unaffiliated/rezurus] has quit [Read error: Connection reset by peer]
19:30 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
19:39 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
19:42 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 240 seconds]
20:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
21:22 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has quit [Remote host closed the connection]
21:22 -!- afk11 [~afk11@gateway/tor-sasl/afk11] has joined #c-lightning
21:38 -!- while [~iam@69.61.169.171] has quit [Remote host closed the connection]
23:16 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]
23:43 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
23:50 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
--- Log closed Tue Feb 18 00:00:44 2020