--- Log opened Tue Sep 10 00:00:06 2019
00:12 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
00:18 -!- vincenzopalazzo [~vincenzop@host253-17-dynamic.37-79-r.retail.telecomitalia.it] has joined #c-lightning
00:21 -!- vincentpalazzo [~vincenzop@host137-162-dynamic.245-95-r.retail.telecomitalia.it] has joined #c-lightning
00:24 -!- vincenzopalazzo [~vincenzop@host253-17-dynamic.37-79-r.retail.telecomitalia.it] has quit [Ping timeout: 258 seconds]
00:36 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
01:19 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Remote host closed the connection]
02:19 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has quit [Quit: No Ping reply in 180 seconds.]
02:21 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has joined #c-lightning
02:59 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
03:49 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning
03:52 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 245 seconds]
03:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has left #c-lightning []
03:57 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has joined #c-lightning
03:58 < e4xit> How can I see which outbound port C-Lightning is usign for a peer (for outbound connection)? I can see peer port in the db, but nothing about outbound ports...
04:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
04:39 -!- k3tan2 is now known as k3tan
04:44 -!- Victor_sueca is now known as Victorsueca
06:19 -!- vincentpalazzo [~vincenzop@host137-162-dynamic.245-95-r.retail.telecomitalia.it] has quit [Quit: Leaving]
06:34 -!- erasmospunk [~erasmospu@2a01:4f8:160:9147::2] has quit [Quit: bye]
06:40 -!- erasmospunk [~erasmospu@2a01:4f8:160:9147::2] has joined #c-lightning
06:43 -!- MasterdonX [~masterdon@5.226.137.20] has quit [Ping timeout: 245 seconds]
06:47 -!- MasterdonX [~masterdon@207.244.76.233] has joined #c-lightning
07:25 < fiatjaf> why are ALL my python tests failing?
07:25 < fiatjaf> do I have to start a node before I run the tests?
07:27 < fiatjaf> ConnectionRefusedError: [Errno 111] Connection refused 
07:46 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
07:47 < darosior> fiatjaf: you need to install tests/requirements.txt, doc/requirements.txt, and add pylightning to PYTHONPATH
07:47 < darosior> fiatjaf: "do I have to start a node before I run the tests?" no
07:48 < fiatjaf> I did install that
07:49 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
07:49 < darosior> ```
07:49 < darosior> make -j10 && PYTHONPATH=PYTHONPATH:$PWD/contrib/pylightning TEST_DEBUG=1 DEVELOPER=1 VALGRIND=0 PYTEST_PAR=24 pytest --fulltrace tests/test_plugin.py -vvv --timeout=550 --timeout_method=thread -p no:logging -n 12
07:49 < darosior> ```
07:49 < fiatjaf> all the tests are running and all are failing with either a connectionrefusederror or another one
07:49 < darosior> from the lightning dir
07:49 < darosior> Ah
07:49 < darosior> It's weird
07:49 < fiatjaf> ok
07:49 < fiatjaf> wait
07:49 < fiatjaf> I've installed things in a virtualenv
07:50 < fiatjaf> that must be the reason
07:50 < darosior> ...
07:50 < darosior> Activate it then ^^
07:51 < fiatjaf> it is activated!
07:51 < fiatjaf> but I think make doesn't understand that
07:51 < darosior> No I personally test with a virtualenv, and it's ok
07:52 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
07:52 < fiatjaf> ok, then I'll double-check that
07:52 < fiatjaf> but first I need help with some stupid problem because my C knowledge is nonexistent:
07:52 < darosior> Go on I can help you
07:52 < fiatjaf> why does this change https://github.com/ElementsProject/lightning/compare/master...fiatjaf:description_hash?expand=1
07:53 < fiatjaf> causes an error: /home/fiatjaf/comp/lightning/lightningd/test/../invoice.c:695: undefined reference to `param_sha256'
07:54 < fiatjaf> param_sha256 should be in the same place as param_bool, param_tok and so on
07:56 < darosior> `make update-mocks` ?
07:58 < darosior> We should explicit to run `make update-mocks` in the doc. In practice, link errors in C tests are 99% sure to be fixed with `update-mocks` :-)
07:59 < fiatjaf> it seems that has fixed it
08:54 -!- MrHash [~mrhash@host81-153-221-226.range81-153.btcentralplus.com] has joined #c-lightning
08:57 < MrHash> hello @cdecker if i revert this commit (https://github.com/cdecker/lightning/commit/0ce13f463ce25f2fbb949a694b271c6442c93794) will this branch work with elements in regtest mode?
09:03 -!- treehug88 [~textual@pool-173-56-75-234.nycmny.fios.verizon.net] has quit [Quit: Textual IRC Client: www.textualapp.com]
09:32 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
10:00 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
10:45 < fiatjaf> I'm trying to implement the description_hash support
10:45 < fiatjaf> should I open an issue?
10:45 < fiatjaf> I think yes
10:45 <@niftynei> +1
10:59 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
11:00 -!- MrHash [~mrhash@host81-153-221-226.range81-153.btcentralplus.com] has quit [Remote host closed the connection]
11:22 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
12:10 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has left #c-lightning []
12:10 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has joined #c-lightning
12:11 <@cdecker> MrHash: yes, that's the change that switched from regtest to liquidv1
12:11 <@cdecker> MrHash: but I have a better branch that makes this whole thing configurable again
12:25 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
13:00 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
13:12 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
13:37 < e4xit> Where does C-Lighting store which outbound (ephemeral) port its using to talk with a peer? it's not in lightningd.sqlite3... 
13:38 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 245 seconds]
13:39 < e4xit> I need a way for my program to know which port to sniff, so that it can proxy traffic via meshnet
13:41 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
13:42 < darosior> e4xit it's 9735, peer messages are queued and I think that they all use this port
13:44 < e4xit> darosior: when I make a connection to a peer, it uses a random high-numbered port. 9735 is for incoming connections AFAIK
13:45 < darosior> You may be right, I'm not sure about that
13:45 < darosior> I'll check the code
13:45 < e4xit> e.g. here is my connection from node A to node B: "192.168.1.1:55904" (I am on a LAN)
13:46 < e4xit> I know I can see "which ports lightningd is using" from system tools, but really I want to query C-Lightning (or read it's db) if possible
13:46 < e4xit> as I might have multiple peers, for example
13:47 < darosior> But I think that's the OS which chose the port
13:47 < e4xit> yes, I think it is
13:48 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
13:48 < e4xit> in Python, you just bind the socket to nothing and let the OS choose the port, e.g. `sock.bind(('', 0))`, but still C-Lightning must keep track of these somehow.... or maybe not?
13:49 < darosior> Yes that's effectively the OS (checked)
13:49 < darosior> No we dont need, we store fds
13:49 < e4xit> agree :)
13:50 < darosior> Actually the peer connection is done like this:
13:50 < e4xit> oh, damn. hmmmmmmm, how can I get around this
13:50 < darosior> A peer connect / we connect to a peer : the `connectd` daemon handles this
13:51 < darosior> Once a channel is created the fd is passed to `channeld` which will handle channel operations
13:51 < e4xit> ok
13:51 < e4xit> I can't really get at that then
13:51 < e4xit> thanks
13:52 < darosior> There is one instanciation of each per peer : if you have a node, you'll be able to see one `lightning-channeld` per active channel
13:52 < darosior> using pstree for example
13:52 < e4xit> oh ok
13:53 < darosior> You could check the open ports per process
13:54 < darosior> per each lightning-connectd and lightning-channeld running
13:56 < e4xit> yep. this actually might work. I am using the assumption that the machine will only have a single channel, so the only lightning-channeld I see is my port!
13:57 < e4xit> with pstree and lsof I can get the port from the command line :) Now I just need to implement in Python -- thank you very much
14:08 -!- reallll is now known as belcher
14:11 -!- michaelfolkson [~textual@bzq-82-81-55-16.red.bezeqint.net] has joined #c-lightning
14:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 245 seconds]
14:27 < darosior> You are welcome
15:02 -!- michaelfolkson [~textual@bzq-82-81-55-16.red.bezeqint.net] has quit [Quit: Sleep mode]
15:03 < e4xit> excellent that was a very easy 6 LOC in the end! thanks again darosior!
15:04 < darosior> :-)
15:06 < darosior> cdecker: does your seed handles testnet addresses ?
15:09 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
15:13 -!- michaelfolkson [~textual@bzq-82-81-54-76.red.bezeqint.net] has joined #c-lightning
15:17 -!- michaelfolkson [~textual@bzq-82-81-54-76.red.bezeqint.net] has quit [Ping timeout: 245 seconds]
15:19 <@cdecker> You mean in the lightning-elements branch? No that'd be another asset ID still
15:19 <@cdecker> Definitely need to rebase that branch, I have all the asset tags in the chainparams which works very nicely
15:56 < e4xit> Is there any way to make C-Lightning use a Unix socket instead of an Internet socket? 
15:57 < e4xit> ... for the WAN networking stuff (e.g channel updates)
16:00 <@cdecker> Should be doable :-)
16:01 < e4xit> cdecker: I assume it's source code modification, rather than command line options? :)
16:01 <@cdecker> Indeed, here's the location you are looking for though https://github.com/ElementsProject/lightning/blob/1c0d435f5e4367586632b6841504b754728dedc0/connectd/connectd.c#L874-L912
16:02 < e4xit> muchas gracias
16:02 <@cdecker> De nada
16:03 < e4xit> I think that might enable me (and C-Lightning) to send/recv packets when there are no active network interfaces, right? (if I can proxy them out of band)
16:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
16:13 < darosior> No I meant for testnet node pubkeys
16:14 < darosior> I didnt ask clearly ^^
16:14 <@cdecker> I don't follow darosior which seed then?
16:14 < darosior> ln seed
16:14 <@cdecker> Ah, ok now I get it
16:14 <@cdecker> No testnet nodes are currently not being served
16:15 < darosior> Thanks
16:15 <@cdecker> It's a bit much infrastructure I'd need to replicate for that 
17:55 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
17:58 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
17:59 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
18:26 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
18:42 <@niftynei> so, we have a mini-problem with dual-funding & the proposed fundchannelmulti workflow, as currently proposed
18:43 <@niftynei> the problem is that we no longer exclusively control broadcasting of the funding transaction
18:45 <@niftynei> this is especially problematic if the peer adds funds to the funding tx, since the opener sends their signatures to the peer before receiving their signatures back... in theory the peer may not send their signatures back but just broadcast the funding tx anyway
18:45 <@niftynei> if you're doing this with multiple peers, there's no way to collect all the signatures  you need 
18:46 <@niftynei> we can change the dual-funding proposal such that only the opener can send the funding tx; that'd make fundmulti possible
18:47 <@niftynei> the downside is that the accepting peer never receives the entire funding tx; they'd be reliant on the opener to publish it
18:47 <@niftynei> which maybe is a fine tradeoff?
18:48 <@niftynei> it moves the 'might ghost you' situation from the opener to the accepter
18:53 < rusty> niftynei: yes, I think this makes sense.
18:54 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has quit [Ping timeout: 246 seconds]
18:54 < rusty> niftynei: almost by definition the accepter can't be tring to merge multiple txs (unless we want do create a whole mixer infra).
18:54 < rusty> niftynei: but we should let the opener do so.
20:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has left #c-lightning []
20:21 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has joined #c-lightning
20:37 <@niftynei> cool, yeah. it feels like the right move to me too :)
20:40 -!- wallet42 [sid154231@gateway/web/irccloud.com/x-ghdgacblqxpdwvmj] has quit [Ping timeout: 252 seconds]
20:43 -!- harding [~harding@cpe-66-91-121-125.hawaii.res.rr.com] has quit [Ping timeout: 245 seconds]
20:44 -!- wallet42 [sid154231@gateway/web/irccloud.com/x-tygjqsvyyzrokwed] has joined #c-lightning
21:25 -!- harding [~harding@cpe-66-91-121-125.hawaii.res.rr.com] has joined #c-lightning
21:32 -!- harding [~harding@cpe-66-91-121-125.hawaii.res.rr.com] has quit [Ping timeout: 240 seconds]
21:34 -!- harding [~harding@cpe-66-91-121-125.hawaii.res.rr.com] has joined #c-lightning
22:25 -!- mode/#c-lightning [+o rusty] by ChanServ
22:25 -!- 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.7.2.1 **FUNDS AT RISK IF < 0.7.1!** Logs at http://gnusha.org/c-lightning/
22:26 -!- mode/#c-lightning [-o rusty] by rusty
22:42 -!- harding [~harding@cpe-66-91-121-125.hawaii.res.rr.com] has quit [Ping timeout: 245 seconds]
22:43 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 276 seconds]
22:44 -!- harding [~harding@cpe-66-91-121-125.hawaii.res.rr.com] has joined #c-lightning
22:46 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
23:18 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit]
23:18 -!- qubenix [~qubenix@66.172.11.228] has joined #c-lightning
23:36 -!- Amperture [~amp@65.79.129.113] has quit [Remote host closed the connection]
23:56 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has left #c-lightning []
23:56 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has joined #c-lightning
23:57 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has quit [Quit: No Ping reply in 180 seconds.]
23:59 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has joined #c-lightning
--- Log closed Wed Sep 11 00:00:07 2019