--- Log opened Tue Sep 03 00:01:00 2019
00:19 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
00:45 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
00:57 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 258 seconds]
00:58 < e4xit> darosior, cdecker, I am just building github @master. I did try a few bits, but didn't make much process 
00:59 < e4xit> what I recall, I could turn off "-Wstrict-prototypes" for the compiler, but as it was a "-Werror" i think it would still fail.
01:05 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:41 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
01:50 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
01:57 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has joined #c-lightning
02:17 < e4xit> darosior: cdecker: submitted as an issue with additional information: https://github.com/ElementsProject/lightning/issues/3021
02:17 < darosior> Thanks, that's the way to go ! :-)
02:47 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
03:02 < e4xit> darosior: where can I use the flag `dev-suppress-gossip`? It doesn't seem to appreicate me sticking it in the config file or running with cli
03:12 < darosior> e4xit: This is a RPC command
03:27 < e4xit> ok thanks. I have another question :) i started C-Lightning with no channels, and using a non-default port (9733). I haven't seen any traffic on that port using tcpdump (which is great -- what I want!) but, I did expect it to try to query some DNS seeds and the like... is my behaviour expected? Or do you think I might not be monitoring the port traffic correctly?
03:28 < e4xit> The same port monitoring shows plenty of traffic for bitcoind on 8333, so I am inclined to think that there is no traffic on my port...
03:51 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
04:10 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has left #c-lightning []
04:10 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has joined #c-lightning
04:53 < fiatjaf> what is the canonical recommended way of doing backups?
04:53 < fiatjaf> now that the backup plugin isn't recommended anymore
04:53 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 258 seconds]
05:01 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
05:12 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
05:16 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
05:16 <@cdecker> Don't do backups, it's always dangerous
05:17 <@cdecker> We're working on replicated DB support, to alleviate this issue
05:17 <@cdecker> The dbbackup plugin was actually quite good tbh, it just needed some minor tweaks
05:17 <@cdecker> I'll give it a go later and try to make it work a bit better
05:22 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
05:26 < m-schmoock> in the end, loosing money in lightning is a donation to everyone else ;)
05:58 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 245 seconds]
06:05 < e4xit> Can I safely start/run C-Lightning with a still-synchronising bitcoind instance?
06:06 < e4xit> by safely, I mean, on testnet...
06:08 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
06:14 < darosior> It will wait for bitcoind to be synced before doing anything
06:15 < darosior> before being able to do anything*
06:16 < molz> e4xit, this goes for *all* lightning impls. you can't get your LN client to run until bitcoin node is fully synced
06:35 < e4xit> OK thanks each. 
06:37 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 244 seconds]
06:45 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
06:49 -!- vincenzopalazzo [~vincenzop@host90-214-dynamic.54-79-r.retail.telecomitalia.it] has joined #c-lightning
07:08 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 258 seconds]
07:18 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
07:31 <@cdecker> Well, it'll be "running" and processing blocks, but you probably won't be able to do anything useful such as sending/receiving onchain funds, or open channels
07:48 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
07:53 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 258 seconds]
08:01 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
08:03 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Remote host closed the connection]
08:04 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning
08:04 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Ping timeout: 245 seconds]
08:06 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
08:08 < e4xit> I think I kind of asked this before, but is there any way to hook into the messaging of C-Lighting? I would like to filter out (e.g. HTLCUpdate) messages which are destined for a certain node which is offgrid, and has only a mesh network connection. I have looked into doing this with a regular TCP proxy, but wondering if there might be an easier way... 
08:26 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 264 seconds]
08:37 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
08:43 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
08:53 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Ping timeout: 246 seconds]
08:55 -!- queip [~queip@unaffiliated/rezurus] has quit [Ping timeout: 244 seconds]
09:03 -!- queip [~queip@unaffiliated/rezurus] has joined #c-lightning
09:19 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
09:24 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
09:25 < darosior> hmmm the easier way to do this would be to write a hook (there is one for htlc_accepted, you might want to use it to refuse HTLCs so you dont get update ?)
09:33 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
09:49 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
09:54 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Ping timeout: 258 seconds]
10:10 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
10:14 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Ping timeout: 245 seconds]
10:26 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
10:31 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Ping timeout: 264 seconds]
10:33 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
11:01 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
11:02 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
11:11 < fiatjaf> e4xit, once my bitcoind became very out-of-sync, then lightningd started failing payments because it had a wrong sense of time.
11:35 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
11:39 <@niftynei> e4xit re no
11:39 <@niftynei> e4xit re: no traffic on the port, did you connect out to any peers? i don't believe we have auto-connect turned on
11:40 <@niftynei> you can run the 'bootstrap-node.sh' script in contrib/ to get the dns seeding behavior that bitcoind has
11:41 <@niftynei> it just connects you to a few pre-selected nodes
11:47 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
11:47 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
12:21 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning
12:25 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 258 seconds]
12:29 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has left #c-lightning []
12:29 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has joined #c-lightning
12:30 -!- reallll is now known as belcher
12:36 < e4xit> niftynei: oh ok, thats good -- I don't want to make any outbound connections, have any gossip or any other traffic if possible
12:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
12:53 <@niftynei> cool B)
13:06 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
14:33 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has quit [Remote host closed the connection]
14:34 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
14:43 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
14:53 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning
15:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
15:01 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
15:12 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection]
15:34 -!- k3tan [k3tan@gateway/vpn/protonvpn/k3tan] has joined #c-lightning
16:08 -!- vincenzopalazzo [~vincenzop@host90-214-dynamic.54-79-r.retail.telecomitalia.it] has quit [Quit: Leaving]
16:12 -!- moneyball [sid299869@gateway/web/irccloud.com/x-wwgbwsasxjqnrqlh] has joined #c-lightning
16:52 -!- rh0nj [~rh0nj@88.99.167.175] has quit [Ping timeout: 245 seconds]
16:54 -!- rh0nj [~rh0nj@88.99.167.175] has joined #c-lightning
17:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:44 -!- mdunnio [~mdunnio@50-203-76-10-static.hfc.comcastbusiness.net] has joined #c-lightning
17:51 -!- mdunnio [~mdunnio@50-203-76-10-static.hfc.comcastbusiness.net] has quit [Remote host closed the connection]
18:54 < fiatjaf> will option_static_remotekey allow us to recover funds with only the hsm_secret as long as peers cooperate, like lnd's "static backups"?
19:22 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
20:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
20:42 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has left #c-lightning []
20:43 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-icdpzigfnkmughei] has joined #c-lightning
21:00 < rusty> fiatjaf: theoretically, yes.  In practice, no since we don't scan for those keys (yet).
21:31 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
21:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 258 seconds]
22:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
22:55 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
23:31 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
--- Log closed Wed Sep 04 00:00:00 2019