--- Log opened Tue Aug 06 00:00:31 2019 00:01 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 01:50 -!- Victor_sueca is now known as Victorsueca 01:55 -!- justanotheruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has quit [Ping timeout: 268 seconds] 02:17 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 02:46 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 03:43 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 03:43 -!- booyah_ [~bb@193.25.1.157] has joined #c-lightning 03:44 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 03:44 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 03:45 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has left #c-lightning [] 03:46 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has joined #c-lightning 04:09 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 04:46 < darosior> rusty, cdecker: What would be the best way to register a public hook ? The macro defines a static inline function (cf https://github.com/ElementsProject/lightning/pull/2237#discussion_r247010214) but I want to register a hook accessible from multiple files. I first open coded it, then I tried tweaking macros without result, now I wonder if defining 04:46 < darosior> a second macro to register a globally accessible hook would not be the best choice, at the expanse of code duplication. What do you think ? 05:02 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds] 05:05 -!- justan0theruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has joined #c-lightning 05:05 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 05:36 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 06:08 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 245 seconds] 06:08 -!- ghost43_ [~daer@gateway/tor-sasl/daer] has joined #c-lightning 06:09 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 260 seconds] 06:09 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 06:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 07:00 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 07:39 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 07:55 <@cdecker> darosior: iirc the reason it is a static inline is that I wanted to be able to include it in a header file (allowing for other files to call it) and not have to split it into a declaration and definition part in two separate files. static inline was the only variant that I got to work 07:55 < darosior> Fwiw I finally created a new pair of files 07:56 < darosior> > darosior: iirc the reason it is a static inline is that I wanted to be able to include it in a header file (allowing for other files to call it) and not have to split it into a declaration and definition part in two separate files. static inline was the only variant that I got to work 07:56 < darosior> I ended up creating a new pair of files (lightningd/hooks) with a new macro which does not create the definition, only the call 07:57 -!- belcher [~belcher@unaffiliated/belcher] has quit [Read error: Connection timed out] 07:57 < darosior> I don't know if it's a good pattern but new files for global hooks seems legit, like we have lightningd/notification for globally accessible notifications 07:57 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning 07:57 < darosior> s/seems legit/seemed legit to me/ 09:06 < m-schmoock> cdecker: if rust is around, im running the gossip voodoo branch since a couple of days now but without a crash... 09:07 < m-schmoock> few weeks ago it crashed like every few days or in a week or so 09:26 -!- ghost43_ is now known as ghost43 10:13 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning 10:18 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Ping timeout: 268 seconds] 10:24 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has quit [Ping timeout: 272 seconds] 10:30 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning 10:33 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 10:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 248 seconds] 11:18 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning 11:21 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 246 seconds] 11:47 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning 11:49 -!- reallll is now known as belcher 11:49 <@cdecker> Awesome m-schmoock, I'll relay the good news, or bad if it was intended to cause the crash :-) 12:04 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has left #c-lightning [] 12:04 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has joined #c-lightning 12:17 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #c-lightning 12:48 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 12:49 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 244 seconds] 13:28 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 13:56 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 13:57 < e4xit> cdecker: is there, by chance, a way to disable all gossip and graph updates in C-Lightning? I would like to use it in a mode to make a single channel to a single node, using ultra-low bandwidth. That might work with your man-in-the-middle proxy idea from above (thursday)... 14:00 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning 14:01 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 14:09 -!- mdunnio [~mdunnio@38.126.31.226] has joined #c-lightning 14:09 -!- justan0theruser is now known as justanotheruser 14:10 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 14:13 < darosior> e4xit: `dev-suppress-gossip` ? 14:26 < darosior> However (I just tested) it seems that you cant use `fundchannel` after `dev-suppress-gossip` 14:36 < e4xit> wow! that could be awesome, thanks. I will fund the channel first 14:37 < darosior> I don't know if this is what you intent to achieve but using https://github.com/darosior/regtest-manager I've set up two nodes with a channel and no more gossip (you just need to fund the channel before suppressing the gossip) : `start_regtest && fund_regtest && lnreg1 dev-suppress-gossip && lnreg2 dev-suppress-gossip && rm regtest/lndir1/gossip_st 14:37 < darosior> ore && rm regtest/lndir2/gossip_store` 14:38 < darosior> After that I could succesfully pay `lnreg2` with `lnreg1` : `lnreg1 pay $(lnreg2 invoice 1000 a a | jq -r .bolt11)` without having a gossip_store anymore. 14:39 < e4xit> that, does sounds like exactly it! Once I have setup the channel, I intend to take (one) node offline, and only use it to pay recieved invoices, to the channel partner, so not interested in any gossip etc. If trampoline payments arrive, I intend to use the channel partner (who is online) to do routing on behalf of offline node 14:41 < e4xit> it looks like c-lightning does not use ZMQ (like LND), can C-Lightning and LND therefore co-exist peacefully off a single bitcoind instance? 14:50 < e4xit> hmmm, "lightning_connectd(19716): Failed to create 10 socket: Address already in use" it appears not? 14:51 < darosior> Which command did you use ? 14:51 < darosior> And for lnd and C-lightning co-existence.. I've never tested ;-) 14:54 < e4xit> that was just using `lightningd/lightningd --network=testnet --log-level=debug` 14:55 < e4xit> jsut goingg to try fleshing out a conf file to see if that sorts it... 14:58 < darosior> Change the bind address 14:58 < darosior> the `--bind-addr` argument to `lightningd` 14:59 < e4xit> ah! its trying 9735 also! 14:59 < darosior> You must already have a testnet node listening, thus you cant open a socket listening on the same port. `lightningd/lightningd --network=testnet --log-level=debug --bind-addr 127.0.0.1:10111` should work 15:00 < darosior> If you of course dont have a process listening on 10111 :-) 15:01 < e4xit> thanks, I have now progressed to the next error :P 15:01 < darosior> Which is ? 15:04 < e4xit> I'm in! thanks for your heklp 15:04 < darosior> You are welcome 15:04 < e4xit> It was just my data-dir argument being incorrect 15:06 < e4xit> darosior: "lightning config file line 8: dev-supress-gossip=1: unrecognized option" hmmm, I don't see this option in `lightningd/lightningd --help` either 15:07 < e4xit> I have the other dev ones, as I configured with the dev flag, but not that one... 15:09 < e4xit> Oh sorry, is it a cli command, sorry! 16:04 -!- cryptoso- [~cryptosoa@gateway/tor-sasl/cryptosoap] has joined #c-lightning 16:04 -!- cryptosoap [~cryptosoa@gateway/tor-sasl/cryptosoap] has quit [Ping timeout: 260 seconds] 17:16 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:34 -!- instagibbs [~instagibb@pool-100-15-121-126.washdc.fios.verizon.net] has quit [Ping timeout: 245 seconds] 17:36 -!- instagibbs [~instagibb@pool-100-15-121-126.washdc.fios.verizon.net] has joined #c-lightning 18:24 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 20:27 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 20:30 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has left #c-lightning [] 20:31 -!- blockstream_bot [~blockstre@ec2-3-223-24-8.compute-1.amazonaws.com] has joined #c-lightning 20:39 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 260 seconds] 20:52 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 21:11 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has quit [Quit: No Ping reply in 180 seconds.] 21:12 -!- RonNa [~quassel@60-251-129-61.HINET-IP.hinet.net] has joined #c-lightning 21:31 -!- Victor_sueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 21:34 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Ping timeout: 246 seconds] 23:59 -!- justanotheruser [justanothe@gateway/vpn/nordvpn/justanotheruser] has quit [Ping timeout: 258 seconds] --- Log closed Wed Aug 07 00:00:32 2019