--- Log opened Mon Oct 14 00:00:40 2019 --- Log closed Mon Oct 14 10:28:50 2019 --- Log opened Mon Oct 14 10:29:03 2019 10:29 -!- gnusha [~gnusha@unaffiliated/kanzure/bot/gnusha] has joined #lightning-dev 10:29 -!- Topic for #lightning-dev: Bitcoin Lightning Network Development: Be Excellent To Each Other! Logging at http://gnusha.org/lightning-dev/ Next Meeting: BERLIN 2019-10-18 17:00 @TLC 10:29 -!- Topic set by rusty [~rusty@pdpc/supporter/bronze/rusty] [Thu Oct 10 17:10:31 2019] 10:29 [Users #lightning-dev] 10:29 [+roasbeef ] [ CodeShark_ ] [ GAit ] [ kanzure ] [ nothingmuch ] [ takinbo ] 10:29 [ _flow_ ] [ cryptapus ] [ gambpang ] [ kcalvinalvin ] [ nsh ] [ TD-Linux ] 10:29 [ AaronvanW ] [ cryptoso- ] [ gertjaap ] [ knocte ] [ orange- ] [ TheFuzzStone[m]] 10:29 [ achow101 ] [ CubicEarth ] [ ghost43 ] [ Kostenko ] [ otoburb ] [ ThisAsYou_ ] 10:29 [ afk11 ] [ dabura667 ] [ gkrizek ] [ laptop_ ] [ Ox207fffff ] [ tigermousr ] 10:29 [ aj ] [ darosior ] [ gleb ] [ lightningbot ] [ oyvkva ] [ tinova ] 10:29 [ alko89 ] [ DavidMitchell[m]] [ gnusha ] [ Liliaceae ] [ pepesza ] [ tombusby ] 10:29 [ Amperture ] [ davout ] [ gpestana ] [ lio17 ] [ petezz4 ] [ treyzania_ ] 10:29 [ Anduck ] [ deafboy ] [ greypw ] [ llfourn ] [ pigeons ] [ tryphe ] 10:29 [ Apocalyptic ] [ designwish ] [ gribble ] [ lndbot ] [ pm7 ] [ tuxcanfly ] 10:29 [ aqquadro ] [ digi_james ] [ gwillen ] [ luke-jr ] [ pokazef ] [ unixb0y ] 10:29 [ ariard ] [ dlb76 ] [ hamess ] [ Madars ] [ rachelfish ] [ usil ] 10:29 [ arij ] [ dmkathayat ] [ hardforkthis7] [ marcinja ] [ rh0nj ] [ valwal ] 10:29 [ arshbot ] [ dongcarl ] [ harding ] [ marcoagner ] [ riclas ] [ vtnerd ] 10:29 [ arubi ] [ drolmer ] [ harrigan ] [ mdunnio ] [ robby938_______ ] [ wallet42 ] 10:29 [ asoltys ] [ electric-sheep[m] [ hkjn_ ] [ melvster ] [ robmyers ] [ warren ] 10:29 [ bad_duck ] [ Eliel ] [ ianthius ] [ midnightmagic] [ rompert_ ] [ waxwing_ ] 10:29 [ bauerj ] [ Emcy ] [ inara` ] [ molz ] [ RonNa ] [ wbnns ] 10:29 [ berndj ] [ emzy ] [ interfect[m] ] [ moneyball ] [ RubenSomsen ] [ willcl_ark ] 10:29 [ betawaffle ] [ erasmospunk ] [ jb55 ] [ Monthrec- ] [ scalability-junk] [ windsok ] 10:29 [ bitconner ] [ esotericnonsense] [ jimpo_ ] [ mr_burdell_ ] [ schmidty ] [ wpaulino ] 10:29 [ BlueMatt ] [ farmerwampum ] [ JoKe[m] ] [ msv5 ] [ sh_smith ] [ wraithm ] 10:29 [ bsm117532 ] [ fengling ] [ jonasschnelli] [ Nebraskka ] [ shesek ] [ wullon ] 10:29 [ buZz ] [ fiatjaf ] [ jonatack ] [ nehan ] [ so ] [ wxss ] 10:29 [ cdecker ] [ fjahr ] [ junderw ] [ nibbier_ ] [ stevenroose ] [ ysangkok ] 10:29 [ cfields ] [ fkinglag ] [ jungly ] [ niceplace ] [ stiell ] [ zerogue ] 10:29 [ Chris_Stewart_5] [ fluffypony ] [ justinmoon ] [ niftynei ] [ sugarpuff ] [ zmanian_ ] 10:29 [ cncr04s ] [ fox2p ] [ kamyl ] [ nodweber ] [ sword_smith ] 10:29 -!- Irssi: #lightning-dev: Total of 167 nicks [0 ops, 0 halfops, 1 voices, 166 normal] 10:29 -!- Channel #lightning-dev created Sun Oct 24 05:07:53 2004 10:30 -!- Irssi: Join to #lightning-dev was synced in 64 secs 10:31 -!- aqquadro [~name@unaffiliated/aqquadro] has quit [Ping timeout: 240 seconds] 10:37 -!- laptop_ [~laptop@2a00:23c4:4ebe:3601:180c:38bb:fcf2:5f64] has quit [Ping timeout: 276 seconds] --- Log closed Mon Oct 14 10:38:00 2019 --- Log opened Mon Oct 14 10:38:33 2019 10:38 -!- gnusha [~gnusha@unaffiliated/kanzure/bot/gnusha] has joined #lightning-dev 10:38 -!- Topic for #lightning-dev: Bitcoin Lightning Network Development: Be Excellent To Each Other! Logging at http://gnusha.org/lightning-dev/ Next Meeting: BERLIN 2019-10-18 17:00 @TLC 10:38 -!- Topic set by rusty [~rusty@pdpc/supporter/bronze/rusty] [Thu Oct 10 17:10:31 2019] 10:38 [Users #lightning-dev] 10:38 [+roasbeef ] [ cryptapus ] [ gambpang ] [ kcalvinalvin ] [ orange- ] [ TheFuzzStone[m]] 10:38 [ _flow_ ] [ cryptoso- ] [ gertjaap ] [ knocte ] [ otoburb ] [ ThisAsYou_ ] 10:38 [ AaronvanW ] [ CubicEarth ] [ ghost43 ] [ Kostenko ] [ Ox207fffff ] [ tigermousr ] 10:38 [ achow101 ] [ dabura667 ] [ gkrizek ] [ lightningbot ] [ oyvkva ] [ tinova ] 10:38 [ afk11 ] [ darosior ] [ gleb ] [ Liliaceae ] [ pepesza ] [ tombusby ] 10:38 [ aj ] [ DavidMitchell[m]] [ gnusha ] [ lio17 ] [ petezz4 ] [ treyzania_ ] 10:38 [ alko89 ] [ davout ] [ gpestana ] [ llfourn ] [ pigeons ] [ tryphe ] 10:38 [ Amperture ] [ deafboy ] [ greypw ] [ lndbot ] [ pm7 ] [ tuxcanfly ] 10:38 [ Anduck ] [ designwish ] [ gribble ] [ luke-jr ] [ pokazef ] [ unixb0y ] 10:38 [ Apocalyptic ] [ digi_james ] [ gwillen ] [ Madars ] [ rachelfish ] [ usil ] 10:38 [ ariard ] [ dlb76 ] [ hamess ] [ marcinja ] [ rh0nj ] [ valwal ] 10:38 [ arij ] [ dmkathayat ] [ hardforkthis7] [ marcoagner ] [ riclas ] [ vtnerd ] 10:38 [ arshbot ] [ dongcarl ] [ harding ] [ mdunnio ] [ robby938_______ ] [ wallet42 ] 10:38 [ arubi ] [ drolmer ] [ harrigan ] [ melvster ] [ robmyers ] [ warren ] 10:38 [ asoltys ] [ electric-sheep[m] [ hkjn_ ] [ midnightmagic] [ rompert_ ] [ waxwing_ ] 10:38 [ bad_duck ] [ Eliel ] [ ianthius ] [ molz ] [ RonNa ] [ wbnns ] 10:38 [ bauerj ] [ Emcy ] [ inara` ] [ moneyball ] [ RubenSomsen ] [ willcl_ark ] 10:38 [ berndj ] [ emzy ] [ interfect[m] ] [ Monthrec- ] [ scalability-junk] [ windsok ] 10:38 [ betawaffle ] [ erasmospunk ] [ jb55 ] [ mr_burdell_ ] [ schmidty ] [ wpaulino ] 10:38 [ bitconner ] [ esotericnonsense] [ jimpo_ ] [ msv5 ] [ sh_smith ] [ wraithm ] 10:38 [ BlueMatt ] [ farmerwampum ] [ JoKe[m] ] [ Nebraskka ] [ shesek ] [ wullon ] 10:38 [ bsm117532 ] [ fengling ] [ jonasschnelli] [ nehan ] [ so ] [ wxss ] 10:38 [ buZz ] [ fiatjaf ] [ jonatack ] [ nibbier_ ] [ stevenroose ] [ ysangkok ] 10:38 [ cdecker ] [ fjahr ] [ junderw ] [ niceplace ] [ stiell ] [ zerogue ] 10:38 [ cfields ] [ fkinglag ] [ jungly ] [ niftynei ] [ sugarpuff ] [ zmanian_ ] 10:38 [ Chris_Stewart_5] [ fluffypony ] [ justinmoon ] [ nodweber ] [ sword_smith ] 10:38 [ cncr04s ] [ fox2p ] [ kamyl ] [ nothingmuch ] [ takinbo ] 10:38 [ CodeShark_ ] [ GAit ] [ kanzure ] [ nsh ] [ TD-Linux ] 10:38 -!- Irssi: #lightning-dev: Total of 165 nicks [0 ops, 0 halfops, 1 voices, 164 normal] 10:38 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 10:38 -!- Channel #lightning-dev created Sun Oct 24 05:07:53 2004 10:39 -!- Irssi: Join to #lightning-dev was synced in 67 secs 10:48 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev 10:53 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Ping timeout: 240 seconds] 10:59 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev 11:01 -!- laptop_ [~laptop@2a00:23c4:4ebe:3601:552b:8e23:aeb4:865b] has joined #lightning-dev 11:11 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev 11:14 -!- vtnerd [~Lee@173-23-103-30.client.mchsi.com] has quit [Ping timeout: 265 seconds] 11:16 -!- vtnerd [~Lee@173-23-103-30.client.mchsi.com] has joined #lightning-dev 11:18 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 276 seconds] 11:18 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 11:34 -!- t-bast [~t-bast@ec2-35-180-216-238.eu-west-3.compute.amazonaws.com] has joined #lightning-dev 11:40 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev 11:53 -!- sstone [~sstone@185.186.24.109.rev.sfr.net] has joined #lightning-dev 11:54 < t-bast> hey sstone, reading through the logs of last time Rusty said it would be live in Berlin, so not sure if anybody is going to show up tonight...we'll see ;) 11:56 < sstone> yes I think that's why I though it was not on tonight 11:56 < sstone> thought 11:57 < t-bast> it was a bit confusing, we'll see 12:00 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 12:00 < cdecker> Yep, not sure either. Seems Friday (which was mentioned as a face-to-face opportunity for a spec meeting) also has some kick-off events going 12:01 < t-bast> let's see, if we're enough people we can still have some spec chat tonight ;) 12:02 < t-bast> what are you currently working on cdecker? 12:04 < cdecker> Not much tbh, just came back from holidays, mostly prepping the LNConf talk, and we have a release coming up soon 12:04 < t-bast> ok cool 12:04 < t-bast> I was wondering if you had helped Electrum with their lightning python implementation (you mentioned a toy implementation you made in python) 12:05 < t-bast> And we have some stuff to discuss with you regarding stuckless payments, sha256 midstate and friends ;) 12:06 < niftynei> hello! 12:06 < cdecker> Not really, I haven't looked at their code at all yet. I was planning to when they opened a PR on the lightning-integration repo 12:06 < t-bast> Hey niftynei! 12:06 < cdecker> But they wove the lightning daemon into the testing framework, whereas I wanted them to run the daemon as a separate process (like the others do), so we could test them in parallel without fearing interference 12:07 < cdecker> Hi niftynei :-) 12:08 < niftynei> :D 12:08 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev 12:09 < t-bast> Do you plan to deprecate lightning-integration in favor of Rusty's testing framework (when we eventually implement drivers for it) or do they both serve different purposes? 12:10 < cdecker> I was considering dropping that repo, but we found a couple of instances where testing a specific combination of implementations on a specific scenario is really useful, so maybe we can switch it's purpose a bit to be more for regression testing, rather than full matrix compatibility testing 12:10 < t-bast> ok good to know 12:10 < cdecker> How about you guys? Congrats on the funding round! 12:11 < niftynei> yes, congrats!! 12:11 < t-bast> Thanks! Really appreciated tweets and comments from people all over the community! 12:11 < t-bast> Now we just need to find experienced Scala Lightning Developers. Easy enough right? 12:12 < niftynei> ohhh 12:12 < cdecker> Hehe, hopefully it'll be easier now, with the added backing and news coverage 12:13 < t-bast> yeah definitely, we just need to spend more time on hiring and all 12:13 < t-bast> it's really surprising but Bitcoin knowledge in engineering schools in France is really poor 12:13 < niftynei> this does not surprise me at all tbh 12:14 < t-bast> how is it in other countries? US and Switzerland is any better? 12:14 < niftynei> i recently moved back to my hometown which has a small, well known university with a very well regarded CS department 12:14 < cdecker> Yep, that was my experience as well. It used to be really hard to find students for projects that were bitcoin-related 12:14 < niftynei> they don't even have a cryptography class as a permanent fixture on the class schedule 12:14 < t-bast> wow really? that's sad for students 12:15 < niftynei> it's offered as an elective every so often :[ 12:15 < t-bast> they're going to miss the computer security wave... 12:15 < cdecker> It's getting better now, and I help wherever I can giving courses to universities, but reach is still not there 12:15 < niftynei> they have one faculty member on staff who seems to have vaguely blockchain related ressearch 12:15 < niftynei> my take away is that it's very unevenly distributted in the US 12:15 < niftynei> basically stanford and MIT 12:16 < niftynei> maybe berkeley, but i'd guess that's due to proximity to Stanford more than anything 12:16 < t-bast> yeah that's pretty much what I saw, Stanford/MIT/Berkeley is hot on blockchain/crypto but didn't know about the rest 12:16 < cdecker> One of the problems is that all professors that are even tangentially working on blockchainy stuff get swept up into ICOs (or whatever the goto synonym for scams is today) 12:16 < t-bast> cdecker: xD 12:16 < niftynei> ^^ this what cdecker says 12:17 < cdecker> Ah, the temptations of free and easy money xD 12:17 < t-bast> And long years of trial after that :) 12:17 < sstone> well one of the issue we saw when we approached academics is that there needs to be some path to "funding" in a general sense 12:18 < niftynei> my hometown has a very large medical industry and oil & gas companies, and space. the engineering practices are all very cutting edge in other regards, but crypto is not really big here atm 12:18 < niftynei> it's interesting to me how local academia tends to mimic the local industry needs 12:18 < niftynei> which kind of matches what you're saying about 'path to funding' sstone 12:18 < t-bast> it makes sense: they know they can find partnerships for funding the research 12:19 < t-bast> and it's easier to get that research applied to solving real issues, which also makes sense... 12:19 -!- nobody123 [~nobody123@ipservice-092-217-244-175.092.217.pools.vodafone-ip.de] has joined #lightning-dev 12:19 < niftynei> few crpyto mining firms though, all looking to make contacts with energy companies >.< 12:19 < t-bast> haha you got cheap electricity over there? 12:20 < niftynei> honestly i don't know!! but if you wanted to talk to people in the energy business they're all here :) 12:20 -!- fengling [~qinfengli@45.32.53.207] has quit [Ping timeout: 268 seconds] 12:20 < niftynei> sort of unrelated but i have an unofficial news bulletin in that i'm hoping to send out a listserve email soliticing reviews for the latest dual funding proposal this week or next 12:21 < cdecker> Well, we didn't have to go looking for funding, since we were mostly paid for our teaching jobs at the institute. Takes a lot of time, but allows to do fundamental research that might not have a direct application yet 12:21 < sstone> niftynei: are you in Texas ? 12:21 < t-bast> oh great, my next question was going to be about your progress on dual funding - really interested in reading the latest 12:21 < niftynei> yes, houston! good deduction skills sstone :) 12:22 < sstone> oil and space :) 12:22 < niftynei> rusty and i agreed to some rather large protocol changes at the last minute, right as we were discussing merging the implementation i had so 12:23 < niftynei> it pushed it back a bit to say the least; i'm working on writing up the changes for the spec now. hoping to have it redone in the code in the next few weeks :) 12:23 < t-bast> great let's change everything - this way we can also make cancellable payments and decorrelation at the same time ;) 12:23 < niftynei> D: 12:23 < niftynei> the specific change we were going for is to specifically allow multiple channels to be opened with the same tx 12:24 < t-bast> do we explicitly disallow that atm? 12:24 < niftynei> well, the version of the protocol i had implemented it was physically impossible 12:24 < sstone> mmm... isn'it sort of possible with the current spec ? 12:25 < niftynei> it's possible with the current spect, but only the opener can fund the channels 12:25 < sstone> ah yes 12:25 < niftynei> so one 'opener' node could create a funding tx with lots of funding outputs in it 12:26 < niftynei> but only their funds! the updated scheme for the dual funding protocol that rusty came up with makes it such that, if you wanted to, you could have several dual-funded funding outputs in the same tx 12:26 < niftynei> channel funds for everyone!! 12:27 < t-bast> haha nice 12:27 < sstone> are you proposing that one tx could create both A->B and B->A channels? 12:27 < sstone> or a single channel with funds on both sides ? 12:27 < niftynei> ok good question. so you'd have on channel A<->B, where both A and B put money into the same funding output 12:28 < niftynei> but the protocol would also allow A, for example, to contact C and put an A<->B, A<->C outputs into the same tx... (i think) 12:28 < t-bast> can we even in the same tx create a channel A<->B, a channel A<->C and a channel A<->D? as long as all parties are online to collaboratively sign? 12:28 < niftynei> exactamondo 12:28 < t-bast> ah great, I think it's nice for new users so that they pay on-chain fee only once to open a bunch of initial channels 12:29 < niftynei> yes! honestly i don't know enough about coinjoins to know how close we're getting to that, but it also seems to be encroaching on that territory too 12:29 < t-bast> it's probably a nightmare to implement a good UX around that if some of the peers become unresponsive in the middle of the signing process, but that's another problem ;) 12:30 -!- fengling [~qinfengli@45.32.53.207] has joined #lightning-dev 12:30 < niftynei> yes! it is a problem. but! the nice thing about abandonment in the middle of a funding tx is that you don't *really* lose too much time 12:30 < t-bast> that's a great point: if channel funding becomes a kind of coin-join, it could be great 12:30 < niftynei> since the funds aren't on chain yet 12:30 < t-bast> yes, it's just a painful UX and painful code to write heh 12:30 < niftynei> oh ... yes 12:31 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 12:31 < sstone> if would be nice to combine opening channels, but if one fails (as in force closes) all the "linked' ones will fail too ? 12:31 < niftynei> the current version was a *lot* simpler in that regard but i think the possibility of reducing on-chain footprint is worth the complexity 12:32 < niftynei> the outputs will all still be distinct 12:32 < t-bast> will you be updating this PR to share your latest proposal: https://github.com/lightningnetwork/lightning-rfc/pull/524 ? 12:32 < niftynei> so other than the coordination required to get the funding tx built + signed, then the overhead of normal channel operation is the same as now 12:33 < niftynei> sstone, so no, channels will still be independent once they're on-chain and should work exactly the same 12:34 < sstone> yes I guess you're right, the other funding utxos will still be unspent 12:34 < niftynei> you're still only making 2-of-2 outputs per channel 12:35 < niftynei> there's just the oppportunity for 1) both sides to have inputs to that output and 2) more than one funding output to be created in that txc 12:35 < niftynei> *tx 12:35 < t-bast> great looks like you got RBF in there to improve closing 12:35 < niftynei> ah, that's just for RBF'ing an open tx! 12:35 < niftynei> lol 12:35 < niftynei> though tbh i haven't implemented that yet == i've been a bit slow! :) 12:35 < t-bast> oh only for the open, it doesn't help like simplified commitment does? 12:35 < niftynei> no :/ 12:36 < t-bast> ok got it 12:36 < niftynei> at least not as written :) 12:37 < t-bast> it looks like open channel v2 has a lot of opportunities for another funding tx CVE, we'll need a lot of testing on that one ;) 12:37 < niftynei> you think? there's definitely a need to check that inputs are non-malleable 12:38 < niftynei> so if a peer gives you an input point, you need to confirm that it is in fact a P2SH-P2W* or P2W* input 12:39 < niftynei> it definitely requires you to share more information about your utxo set with a peer, which is unfortuante 12:41 < t-bast> I'm only looking at the high-level concepts atm, why aren't you using tlv much? It seems most messages have a big fixed part and only additional tlvs at the end 12:41 < niftynei> otherwise it's mostly the same as our current opens :) 12:42 < niftynei> well so the open and accept messages are almost exact copies of the current protocol, the only difference is that the optional staticremote key field has been moved into the TLV 12:42 < t-bast> ok so it's mostly to show the similarity with the previous messages? 12:43 < niftynei> it's also a bit of an ideology choice in that fields that we know are 'required' in a message should go in the message 12:43 < niftynei> the TLVs are for extensions and options, mostly no? 12:44 -!- laptop_ [~laptop@2a00:23c4:4ebe:3601:552b:8e23:aeb4:865b] has quit [Remote host closed the connection] 12:44 -!- laptop_ [~laptop@2a00:23c4:4ebe:3601:552b:8e23:aeb4:865b] has joined #lightning-dev 12:45 < t-bast> We probably still need more experience with them to decide, but my first intuition would have been to wrap all those required fields in a single tlv field. This way if at some point we have a more efficient way of encoding all the data we need, we can use the same message but a different tlv field inside. 12:45 < niftynei> well, except in the onion, but that's a special case of limited ability to change message type 12:45 < sstone> besides, as the protobuf guys say, "required is forever" :) so having fields in TLV format instead of being hardcoded may become handy one day 12:45 < niftynei> but why not just change the message protocol then? 12:46 < niftynei> the messages themselves are type'd 12:46 < t-bast> I think it makes it simpler to group at the spec level, but maybe both solutions are messy anyway when we introduce a new way of doing things... 12:47 < niftynei> i'm not sure that providing upfront flexbility in this case necessarily gains us anything. you still need to do the same amount of update work that changing the message type contains 12:48 < niftynei> but it greatly diminishes your ability to delete code after things have been deprecated :) 12:50 < t-bast> do you *ever* hope to delete code in a lightning implementation? :d 12:51 < niftynei> i'm a very optimistic person :P 12:51 < ariard> cdecker: oh you're saying you are going to deprecate lightning-integration? Was exactly working on the rust-lighting integration rn 12:51 < niftynei> hehehe 12:52 < ariard> so how are we supposed to test for compliance forward ? 12:52 < t-bast> ariard: no don't worry :) 12:52 < cdecker> ariard: not deprecating, just changing it's scope a bit 12:52 < t-bast> there's this https://github.com/lightningnetwork/lightning-rfc/pull/655 12:52 < ariard> cdecker: there is some updates needed on maven and other stuff 12:52 < t-bast> rusty proposed a testing framework, but it doesn't completely replace lighting-integration (and isn't ready yet) 12:52 < cdecker> The new scope would be to test specific configurations (reproduce errors for fixes, ...) and no longer full matrix compat testing 12:53 < ariard> Full matrix compat testing will be moved to Rusty one? 12:54 < cdecker> Rusty's framework doesn't have the combinatorial explosion that lightning-integration testing, since we test all impls against a single impl (the framework), rather than testing all combinations 12:54 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev 12:55 < t-bast> allright I'm heading off, good talking to you niftynei and cdecker, see you in Berlin soon 12:56 -!- t-bast [~t-bast@ec2-35-180-216-238.eu-west-3.compute.amazonaws.com] has quit [Quit: Leaving] 12:56 < cdecker> Yep, looking forward to the big party, and seeing all of you guys again :-) 12:56 < niftynei> :wave: 12:58 < sstone> bye everyone! 12:58 -!- sstone [~sstone@185.186.24.109.rev.sfr.net] has quit [Quit: Leaving] 13:11 < nobody123> Hello guys so I went on with the mac installation, but now the gossipd/gossip_store.c is having issues 13:12 < nobody123> "error: implicit declaration of function 'pwritev' is invalid in C99 " 13:13 < niftynei> nobody123, i think you want #c-lightning 13:13 < nobody123> thanks 13:13 < niftynei> are you on the latest RC? that should be fixed 13:22 -!- aqquadro [~name@unaffiliated/aqquadro] has joined #lightning-dev 13:23 -!- hiroki_ [d2a585b4@pl72884.ag2001.nttpc.ne.jp] has joined #lightning-dev 14:11 -!- marcoagner [~user@bl13-225-206.dsl.telepac.pt] has quit [Ping timeout: 265 seconds] 14:14 -!- niceplace [~nplace@185.108.105.23] has quit [Ping timeout: 246 seconds] 14:17 -!- niceplace [~nplace@198.52.36.92] has joined #lightning-dev 14:31 -!- hiroki_ [d2a585b4@pl72884.ag2001.nttpc.ne.jp] has quit [Remote host closed the connection] 14:34 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev 14:38 -!- aqquadro [~name@unaffiliated/aqquadro] has quit [Ping timeout: 268 seconds] 14:49 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 268 seconds] 14:52 -!- nobody123 [~nobody123@ipservice-092-217-244-175.092.217.pools.vodafone-ip.de] has quit [Remote host closed the connection] 14:52 -!- nobody12_ [~nobody123@ipservice-092-217-244-175.092.217.pools.vodafone-ip.de] has joined #lightning-dev 14:58 -!- nobody12_ [~nobody123@ipservice-092-217-244-175.092.217.pools.vodafone-ip.de] has quit [Ping timeout: 265 seconds] 15:02 -!- fengling [~qinfengli@45.32.53.207] has quit [Ping timeout: 240 seconds] 15:05 -!- fengling [~qinfengli@45.32.53.207] has joined #lightning-dev 15:19 -!- nobody12_ [~nobody123@ipservice-092-217-244-175.092.217.pools.vodafone-ip.de] has joined #lightning-dev 15:23 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 15:23 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 15:27 -!- nobody12_ [~nobody123@ipservice-092-217-244-175.092.217.pools.vodafone-ip.de] has quit [Remote host closed the connection] 15:28 -!- mdunnio [~mdunnio@38.126.31.226] has joined #lightning-dev 15:29 -!- nobody12_ [~nobody123@ipservice-092-217-244-175.092.217.pools.vodafone-ip.de] has joined #lightning-dev 15:33 -!- mdunnio [~mdunnio@38.126.31.226] has quit [Remote host closed the connection] 15:34 -!- nobody12_ [~nobody123@ipservice-092-217-244-175.092.217.pools.vodafone-ip.de] has quit [Ping timeout: 265 seconds] 15:35 < fox2p> are there known limitations/extra steps for LND nodes running on AWS elastic IPs? 15:35 < fox2p> 10009 port is open but cannot connect through gRPC 15:35 < fox2p> figured it could be AWS specific 15:35 < fox2p> still tinkering with it 15:36 < fox2p> whoops, this isn't the lnd channel, oh well 15:56 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Remote host closed the connection] 16:02 -!- sh_smith [~sh_smith@cpe-76-174-142-242.socal.res.rr.com] has quit [Read error: Connection reset by peer] 16:04 -!- sh_smith [~sh_smith@cpe-76-174-142-242.socal.res.rr.com] has joined #lightning-dev 16:21 -!- valwal9 [~valwal@pool-108-21-84-253.nycmny.fios.verizon.net] has joined #lightning-dev 16:24 -!- valwal9 [~valwal@pool-108-21-84-253.nycmny.fios.verizon.net] has quit [Quit: The Lounge - https://thelounge.chat] 16:25 -!- valwal7 [~valwal@pool-108-21-84-253.nycmny.fios.verizon.net] has joined #lightning-dev 16:25 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev 16:27 -!- valwal [sid334773@gateway/web/irccloud.com/x-teustjwbxhtmkuct] has quit [] 16:27 -!- valwal7 [~valwal@pool-108-21-84-253.nycmny.fios.verizon.net] has quit [Client Quit] 16:28 -!- valwal [~valwal@pool-108-21-84-253.nycmny.fios.verizon.net] has joined #lightning-dev 16:34 -!- anon [~anon321@2a02:8308:50c0:4001:ef0d:9810:d192:60c3] has joined #lightning-dev 16:35 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev 16:40 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 16:53 -!- anon1 [~anon321@2a02:8308:50c0:4000:efb1:e569:a563:13a7] has joined #lightning-dev 16:56 -!- anon [~anon321@2a02:8308:50c0:4001:ef0d:9810:d192:60c3] has quit [Ping timeout: 276 seconds] 16:57 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev 17:17 -!- Ox207fffff [~Thunderbi@072-182-192-217.res.spectrum.com] has quit [Read error: Connection reset by peer] 17:17 -!- Ox207fffff [~Thunderbi@072-182-192-217.res.spectrum.com] has joined #lightning-dev 17:21 -!- Ox207fffff [~Thunderbi@072-182-192-217.res.spectrum.com] has quit [Ping timeout: 240 seconds] 17:26 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #lightning-dev 17:36 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lightning-dev 18:11 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 268 seconds] 18:14 -!- riclas [~riclas@77.7.37.188.rev.vodafone.pt] has quit [Ping timeout: 240 seconds] 18:37 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev 18:42 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 18:48 -!- Amperture [~amp@65.79.129.113] has quit [Remote host closed the connection] 19:09 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 240 seconds] 19:10 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 260 seconds] 19:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev 19:43 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lightning-dev 19:57 -!- Amperture [~amp@65.79.129.113] has joined #lightning-dev 20:14 -!- captjakk [~captjakk@174-16-212-40.hlrn.qwest.net] has joined #lightning-dev 20:39 -!- noxx [~noxx@p200300E617215E002DDC82FBAC670008.dip0.t-ipconnect.de] has joined #lightning-dev 20:39 -!- noxx [~noxx@p200300E617215E002DDC82FBAC670008.dip0.t-ipconnect.de] has quit [Remote host closed the connection] 21:07 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev 21:33 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 260 seconds] 21:41 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has quit [Ping timeout: 265 seconds] 22:36 -!- shesek [~shesek@unaffiliated/shesek] has quit [Read error: Connection reset by peer] 22:36 -!- shesek [~shesek@5.22.135.66] has joined #lightning-dev 22:36 -!- shesek [~shesek@5.22.135.66] has quit [Changing host] 22:36 -!- shesek [~shesek@unaffiliated/shesek] has joined #lightning-dev 23:14 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.] 23:20 -!- jonatack [~jon@2a01:e35:8aba:8220:6627:dad:d967:649d] has quit [Quit: jonatack] 23:21 -!- marcoagner [~user@bl13-225-206.dsl.telepac.pt] has joined #lightning-dev 23:22 -!- __gotcha [~Thunderbi@plone/gotcha] has joined #lightning-dev 23:29 -!- __gotcha [~Thunderbi@plone/gotcha] has quit [Ping timeout: 276 seconds] 23:38 -!- AaronvanW [~AaronvanW@unaffiliated/aaronvanw] has joined #lightning-dev 23:44 -!- kam270 [~kam270@183.182.104.69] has joined #lightning-dev 23:53 -!- jungly [~quassel@79.8.200.97] has quit [Remote host closed the connection] 23:55 -!- jungly [~quassel@79.8.200.97] has joined #lightning-dev --- Log closed Tue Oct 15 00:00:35 2019