--- Day changed Sat Dec 22 2018 00:06 < booyah_> sanket1729: is your bitcoind running? configured password/authorization to it in lnd? just some ideas 00:19 -!- jchia_ [~jchia@58.32.68.96] has quit [Quit: Leaving.] 00:21 -!- zib [zib@slick.hkt0.keff.org] has quit [Ping timeout: 250 seconds] 00:31 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 00:32 -!- zib [zib@slick.hkt0.keff.org] has joined #lnd 00:43 -!- zib [zib@slick.hkt0.keff.org] has quit [Ping timeout: 268 seconds] 00:46 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 00:47 < sanket1729> yes, my bitcoind is running. You can check the config files in gist 00:47 -!- zib [zib@slick.hkt0.keff.org] has joined #lnd 00:48 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Client Quit] 00:48 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 00:49 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Client Quit] 00:49 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 00:53 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Client Quit] 01:09 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 01:54 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 02:22 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 02:58 < Veggen> molz: Have to say that after mainnet became much more reliable, I don't run my testnet node constantly. I ditched the VPS where I ran the testnet node, even, so now I don't even have always-on-hardwware to run it - unless I run it at the same odroid I run my production LND, but I don't want that. 02:58 < Veggen> expect this is the case for a lot of people, really. 02:59 < Veggen> I'm somewhat hardware minimalist these days. Only run small and fanless boxes that don't take up much space. 03:03 < Veggen> sanket1729: 401 is probably wrong credentials. 03:04 < Veggen> (to bitcoind) 04:13 -!- aielima [~aielima@gateway/tor-sasl/aielima] has joined #lnd 04:16 -!- stevenroose [~steven@vps.weuste.club] has quit [Ping timeout: 252 seconds] 04:16 -!- stevenroose [~steven@vps.weuste.club] has joined #lnd 04:46 < molz> Veggen, well after lnd beta was launched on mainnet, i noticed there were less testnet nodes but now there're more, a lot people are testing their projects and apps on testnet 05:06 < Veggen> sure, but I'm not so sure people bother to run them continuously? 05:25 < molz> Veggen, right, it's testnet, it's been like this since the beginning, many people set up nodes to try out and then shut them off and forget about them 05:26 < molz> but now since "Lightning is not vapourware like the fudsters said" so more people are interested in creating their projects and they're more serious in their testing 05:31 -!- zib [zib@slick.hkt0.keff.org] has quit [Ping timeout: 245 seconds] 05:34 < molz> bitcoind v0.17.1 has been tagged officially 05:35 < Veggen> yup, but I also believe some people just forego testnet. 05:42 -!- farmerwampum [~farmerwam@184.75.220.66] has quit [Ping timeout: 240 seconds] 05:46 < molz> haha yep i've seen that too 05:47 < molz> and then their stuff doesn't work, or they lost money, so back to testnet.. rinse and repeat :D 05:52 -!- zib [zib@slick.hkt0.keff.org] has joined #lnd 05:53 < Talkless> molz: good news, but I don't see release notes yet 05:54 < molz> Talkless, it's "tagged" meaning it's released but has to wait for the signed binaries 05:55 < molz> but you can compile and use it 05:55 < Talkless> I would like to know the details before using it, maybe some config options added etc 05:55 < molz> ah yes, i think there's a changelog, it's just a minor version though 05:59 < Talkless> https://github.com/bitcoin/bitcoin/tree/v0.17.1/doc/release-notes 05:59 < Talkless> I don't see even 0.17.0 ? 06:01 < molz> here's a new thing for this version: - #14698 `ec71f06` Add bitcoin-tx.exe into Windows installer (ken2812221) 06:01 < molz> :D 06:05 < molz> https://github.com/bitcoin/bitcoin/blob/v0.17.1/doc/release-notes.md 06:05 < molz> https://github.com/bitcoin/bitcoin/blob/v0.17.0/doc/release-notes.md 06:09 < Talkless> oooh it's "release-notes" file directly, not versioned one. 06:09 < Talkless> lol 06:11 < Talkless> Right, time to build bitcoind! 06:11 -!- deusexbeer [~deusexbee@080-250-077-069-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 244 seconds] 06:16 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Ping timeout: 250 seconds] 06:17 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 06:22 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Ping timeout: 272 seconds] 06:23 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 06:42 < molz> btw, Talkless, someone on lnd slack just told us it took him only 10 min to upgrade from v4.2 to v5.1, he's on "an old ibm server.." :D 06:43 < Talkless> 4.2?? 06:45 -!- math__ [~mario@p54923273.dip0.t-ipconnect.de] has quit [Remote host closed the connection] 06:48 < Talkless> ooh molz you mean lnd 0.4.2 to 0.5.1 ? 06:48 < Talkless> rescanned in 10 minutes?? 06:48 < molz> yup 06:49 < molz> migration and rescanning 06:49 < Talkless> glorious non-ARM master race :)) 07:03 < molz> haha :) 07:54 < lndbot> tuxx, does c-lightning have a fuzz harness? 08:01 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds] 08:01 -!- aerth [~aerth@gateway/tor-sasl/aerth] has quit [Ping timeout: 256 seconds] 08:02 -!- aielima [~aielima@gateway/tor-sasl/aielima] has quit [Ping timeout: 256 seconds] 08:02 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 256 seconds] 08:02 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has quit [Ping timeout: 256 seconds] 08:12 -!- frib [~dynorsau@pool-71-167-9-152.nycmny.fios.verizon.net] has joined #lnd 08:18 -!- aerth [~aerth@gateway/tor-sasl/aerth] has joined #lnd 08:18 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd 08:19 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd 08:30 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Excess Flood] 08:31 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #lnd 08:37 -!- lypsis [~lypsis@2a02:c207:3001:7075:dead:beef:babe:cafe] has quit [Quit: ZNC - https://znc.in] 08:37 -!- lypsis [~lypsis@ec2-18-194-44-195.eu-central-1.compute.amazonaws.com] has joined #lnd 09:04 -!- lypsis [~lypsis@ec2-18-194-44-195.eu-central-1.compute.amazonaws.com] has quit [Quit: ZNC - https://znc.in] 09:06 -!- lypsis [~lypsis@ec2-18-195-130-236.eu-central-1.compute.amazonaws.com] has joined #lnd 09:07 -!- lypsis [~lypsis@ec2-18-195-130-236.eu-central-1.compute.amazonaws.com] has quit [Client Quit] 09:29 -!- frib [~dynorsau@pool-71-167-9-152.nycmny.fios.verizon.net] has quit [Ping timeout: 272 seconds] 09:30 -!- friv [~dynorsau@pool-71-167-9-152.nycmny.fios.verizon.net] has joined #lnd 09:31 < ctrlbreak> Does GO need to be installed for each user of a system? 09:32 < molz> ctrlbreak, no, if you install it at root 09:32 < ctrlbreak> I'm trying to set up LND to run under it's own user... but I can't convince it that GO is installed. 09:32 < molz> you need to activate it 09:32 < ctrlbreak> I used 'snap' to install it as root. 09:33 < ctrlbreak> i.e. - sudo snap install --classic go 09:33 < molz> i don't know how that works for you 09:33 < molz> my guide is simple i don't need any snap :P 09:33 < ctrlbreak> well fuck... how do I remove the snap install and then install it manually?... arggghhhh. 09:34 < tuxx> eugene: it doesnt, no. 09:36 < ctrlbreak> okay molz... nursing a hangover but am mashing your guide up with the one I've been following. 09:46 < ctrlbreak> If I want to fully abandon an LND install for a linux user (not funded, no worries there)... is it just as simple as deleting the .lnd directory in their home dir? 09:52 < Talkless> ctrlbreak: I believe you need go just for compilation, lnd binary is statically linked, as I don't see any go-specific stuff in /proc/$(pgrep ldn)/maps 09:53 < Talkless> so basically compile using go from snap, and run lnd without needing that snap 09:53 < Talkless> ctrlbreak 09:53 < Talkless> /proc/$(pgrep lnd)/maps * 09:54 < Talkless> ctrlbreak: I too run lnd on different user. make & make install maed with GOPATH=/home/lnd/lnd.go 09:55 < ctrlbreak> Thanks Talkless... I don't know a thing about 'snaps', so the go snap was removed and I installed it manually to /usr/local... 09:55 < ctrlbreak> I have LND running under a dedicated user now. 09:55 < Talkless> ctrlbreak: what distro? 09:56 < ctrlbreak> Ubutnu 16.04LTS 09:56 < molz> ctrlbreak, and you need to export your GOPATH 09:56 < ctrlbreak> yup. 09:56 < ctrlbreak> it's in the profiles. 09:56 < Talkless> GOPATH needed only for build imho 09:56 < ctrlbreak> export GOPATH=$HOME/go 09:56 < ctrlbreak> export PATH=$PATH:/usr/local/go/bin:$GOPATH/bin 09:56 < molz> then you need to activate it. source ~/.profile 09:57 < ctrlbreak> Yup... did. 09:57 < ctrlbreak> I'm all good now... 09:57 < molz> ok then it should work haha 09:57 < Talkless> I never did any activation :/ 09:57 < ctrlbreak> yup. running as user 'lnd' now and doing the backend sync now. 09:57 < molz> cool 09:58 < molz> Talkless, linux is weird to me, when i update go now i don't have to activate it but once in a blue moon the terminal screen might act up by not seeing go 09:59 < Talkless> I just do this before compilation: export GOROOT=/usr/lib/go-1.10; export GOPATH=/home/lnd/lnd.go; export PATH=$GOPAT/bin:$GOROOT/bin:$PATH 10:00 -!- friv [~dynorsau@pool-71-167-9-152.nycmny.fios.verizon.net] has quit [Ping timeout: 250 seconds] 10:00 < Talkless> although I have't tried with go 1.11 yet, I will need to build it, as Debian Stretch only have 1.10 10:00 < Talkless> maybe I could fetch if from Debian Sid... 10:00 < ctrlbreak> ffs... wtf is 'snap'? lol 10:00 < molz> you need go1.11, it's a must :) 10:00 < ctrlbreak> /dev/loop0 90M 90M 0 100% /snap/core/6130 10:01 < molz> i'm on go 1.11.4 10:01 < ctrlbreak> they're literally pre-packaged RO filesystems that are loop-mounted? 10:01 < Talkless> molz: for 0.5.1 1.10 works 10:01 < Talkless> for master maybe probably not 10:01 < ctrlbreak> git dis nonsense ouddahere! 10:02 < molz> Talkless, for go 1.11 we now can run go projects without $GOPATH 10:02 < Talkless> ctrlbreak: well it's confined, you should be able to "mount" your directories so go could access them, though I do not have much snap experience. 10:02 < Talkless> molz: so where does it install stuff? 10:02 < molz> anywhere you want 10:02 < Talkless> ho you specify? 10:02 < Talkless> how 10:03 < ctrlbreak> I prefer to not have to learn about snap at this point in time because my head hurts ... so is going away! 10:03 < molz> go mod init 10:05 < molz> Talkless, https://github.com/golang/go/wiki/Modules 10:05 < Talkless> Dec 22 18:13:48 odroid-hc1 systemd[1]: bitcoind.service: State 'stop-sigterm' timed out. Killing. 10:05 < Talkless> Dec 22 18:13:48 odroid-hc1 systemd[1]: bitcoind.service: Killing process 1452 (bitcoin-shutoff) with signal SIGKILL. 10:05 < Talkless> dammit, systemd killed bitcoind, when I initiated systemctl restart, after compiling new one 10:05 < Talkless> # fgrep -R /etc/systemd -eDefaultTimeoutStopSec 10:05 < Talkless> /etc/systemd/system.conf:#DefaultTimeoutStopSec=90s 10:06 < Talkless> default timeout is too small.. 10:09 < Talkless> molz: go mod init creates new module.. do we need that for building lnd? 10:10 < molz> Talkless, no, if you do it like we normally do then no 10:13 < molz> Talkless, here's a small example of creating a project outside your GOPATH: https://github.com/golang/go/wiki/Modules#quick-start 10:14 < Talkless> molz: thanks, but I'm not into go development 10:27 < molz> Talkless, yea not saying you are, but knowing what's going on with Go development which affects lnd helps :P 10:28 < Talkless> yeah I guess so. It's important to know that modules exists, if that changes how you buiDL/deploy software 10:44 -!- frib [~dynorsau@174.138.0.134] has joined #lnd 11:10 < ctrlbreak> My LND node is coming online! Funding it now ;-) 11:13 < molz> yay!! finally!! :D 11:38 <@roasbeef> ctrlbreak: nice 11:42 < ctrlbreak> soooo... macaroons no longer used? 11:42 < ctrlbreak> FYI - I (more or less) followed this guide: https://gist.github.com/bretton/0b22a0503a9eba09df86a23f3d625c13 11:43 -!- e4xit [~e4xit@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has joined #lnd 11:45 < molz> we still do, have more macaroons than ever 11:48 < molz> find .lnd/ -name '*macaroon*' 11:49 <@roasbeef> nah they're still used 11:49 <@roasbeef> should have the bakery up sometime next year 11:50 <@roasbeef> there's a PR up, just a matter of a possible slight re-design and review 11:50 <@roasbeef> but some higher prio things atm 11:50 < tuxx> roasbeef: fuzzing c-lightning is so annoying... 11:50 <@roasbeef> fuzz lnd instead ;) 11:51 <@roasbeef> did you get it to build? 11:51 < tuxx> roasbeef: are you immersed into it? 11:51 < tuxx> roasbeef: yea its fuzzing already.. but crashing because my harness sucks :D 11:51 < tuxx> roasbeef: i hate the ccan/io stuff 11:51 <@roasbeef> yeh idk how the ccan stuff works, looks interesting though 11:51 <@roasbeef> the tree alloc n all 11:51 <@roasbeef> you know they have an IRC channel as well? 11:52 < tuxx> roasbeef: yea exactly.. you pass the ctx and then it frees the tree from the parent downward 11:52 < tuxx> thats the ccan/tal stuff.. the ccan/io stuff is more like for io_loop 11:53 < tuxx> its kindof complex to understand and its not documented... also the lightningd_lightningd speaks to the lightning_gossipd via stdin... 11:53 < tuxx> i thought it was passing msgs more or less raw.. but the msg types dont match up with the RFC so i guess its not raw :( 11:53 < tuxx> but i dumped the output that the lighntingd writes so i have a decent input corpus... 11:53 < tuxx> but idk.. its such a pain.. 11:54 < tuxx> roasbeef: i know they have an irc.. but its not very active aparently.. 11:54 <@roasbeef> ahh gtocha 11:54 < tuxx> maybe due to the festive season :) 11:56 < tuxx> roasbeef: fuzzing lnd wldnt be as fun... i doubt you'd find very much 11:57 < ctrlbreak> LOL... I just checked on my FW NAT rules for at this location and my main bitcoind node has moved ~6TiB of traffic (~this year) 11:57 < tuxx> roasbeef: did your fuzzing efforts in lnd uncover anything? logic bugs? 11:57 < tuxx> i guess logic bugs are the only thing you cld potentially find right? 12:00 <@roasbeef> found some panic/crashing bugs in the wire parsing 12:00 <@roasbeef> those have been patched though 12:00 < tuxx> its coverage driven though right? 12:01 < tuxx> "Go-fuzz is a coverage-guided fuzzing solution" 12:01 < tuxx> kk 12:05 < ctrlbreak> yay. NATs working... no trouble creating an eclair channel with it, even on a non-standard port. 12:06 <@roasbeef> ctrlbreak: nat in lnd? nice, depends on your router real;y 12:06 <@roasbeef> actually, did you do it manually, or with the nat option in lnd? 12:06 < ctrlbreak> Manually... 12:07 < ctrlbreak> internal VM is binding to :9835 ... as my cLightning is already occupying standard port. 12:08 < ctrlbreak> Next I want to try creating a channel between this new LND node and my older cLightning node... and then balancing it. 12:26 <@roasbeef> gotcha 12:27 < ctrlbreak> I have no idea how to rebalance my own channels yet... but I intend to learn. (just not today) 12:28 < ctrlbreak> I'd like to get some additional channels open with the liquidity remaining first (~9mil sats)... 12:28 < ctrlbreak> does autopilot work? Should I be using it on mainnet? 12:30 < molz> not recommended for mainnet yet 12:30 < molz> im running autopilot on my testnet nodes 12:30 -!- thomasanderson [~thomasand@2605:a601:b021:f00:b1f7:9999:ff0c:c9d1] has joined #lnd 12:32 -!- thomasanderson [~thomasand@2605:a601:b021:f00:b1f7:9999:ff0c:c9d1] has quit [Remote host closed the connection] 12:33 < ctrlbreak> How should I manually pick a LN node to initiate a channel with? What does everyone here use for criteria. My only goal with these particular channels is to assist (if possible) with improving the robustness of the LN with some of my own funds. 12:38 -!- frib [~dynorsau@174.138.0.134] has quit [Quit: Leaving] 12:42 -!- thomasanderson [~thomasand@2605:a601:b021:f00:b1f7:9999:ff0c:c9d1] has joined #lnd 12:46 -!- thomasanderson [~thomasand@2605:a601:b021:f00:b1f7:9999:ff0c:c9d1] has quit [Remote host closed the connection] 12:49 -!- thomasanderson [~thomasand@136.52.18.22] has joined #lnd 12:55 -!- thomasanderson [~thomasand@136.52.18.22] has quit [Remote host closed the connection] 13:00 < molz> ctrlbreak, connect to yalls: 03e50492eab4107a773141bb419e107bda3de3d55652e6e1a41225f06a0bbf2d56@mainnet-lnd.yalls.org:9735 13:01 < Talkless> ctrlbreak: Alex Bosworth says "don't use 1ml.com" to select top nodes :) https://www.youtube.com/watch?v=HlPIB6jt6ww 13:02 < ctrlbreak> Yes... I've watched the video :-S 13:02 < ctrlbreak> Then what *should* be used? 13:02 < ctrlbreak> Or is this a wink-wink type thing? 13:03 < Talkless> ctrlbreak: well, actually, idk :)) 13:03 < Talkless> maybe help some smaller channels? 13:04 < Talkless> roasbeef: is there a way to "log" attempts to forward? to see if my node is too slow to be accepted for forwarding, etc? 13:04 < Talkless> forward through me 13:05 < ctrlbreak> I think I might just sit on my remaining balance until I teach myself how to do some explicit routing to balance my own chans. 13:09 < tuxx> i~. 13:09 < tuxx> woops .. :) i wanted to kill my hanging ssh with Enter ~. 13:09 < tuxx> aparently it wasnt hanging and i didnt type it properly :) 13:10 < tuxx> in order to use lightning i guess one needs to expose 9735 publically? 13:13 < qubenix> tuxx: you can avoid it by using an onion service 13:13 < ctrlbreak> hey heyyyyyy... I think my Node Rank^tm score isn't too shabby! 13:13 < ctrlbreak> https://1ml.com/node/0290fb6ecd5865f7a973e1d48ffbc2612f80f6a2defbd6a188928bd0492bc2847e 13:14 < tuxx> qubenix: ye im well not really opposed to exposing it 13:19 < molz> tuxx, if you open port 9735 and expose your IP on lnd.conf, you can get inbound connections 13:24 -!- aielima [~aielima@gateway/tor-sasl/aielima] has joined #lnd 13:42 < tuxx> roasbeef: Fuzz the wtwire messages. 13:43 < tuxx> roasbeef: that is listed in the fuzzing PR on github as "future work"... is the watchtower code in a state where it might be worthwhile to fuzz it? 13:46 < tuxx> ah sorry i read that he already has done some work on that 13:55 < molz> tuxx, go ahead and fuzz all the things! :D 14:20 -!- manantial [~tecnecio@unaffiliated/manantial] has quit [Remote host closed the connection] 14:35 -!- aielima [~aielima@gateway/tor-sasl/aielima] has quit [Remote host closed the connection] 14:35 -!- aielima [~aielima@gateway/tor-sasl/aielima] has joined #lnd 14:51 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 15:18 < lndbot> I barely fuzzed the watchtower nessages 15:18 < lndbot> I’m in the process of changing the harnesses to one harness per message so the fuzzer doesn’t get confused 15:23 < lndbot> Could definitely generate better corpus messages but I gotta read up on ideal corpus messages - it shouldn’t be a dump of messages 15:26 < lndbot> I also feel like fuzzing doesn’t have to be restricted to just protocol messages 15:28 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 15:31 < tuxx> eugene: are you the author of https://github.com/lightningnetwork/lnd/pull/1895 ? 15:31 < tuxx> Eugene Crypt-iQ 15:31 < tuxx> ahh :) 15:32 < lndbot> Yea... slow progress but hopefully will finish over the holidays 15:33 < lndbot> I think fuzzing will be more pick and choose with this PR, like pick a message and then fuzz it 15:33 < lndbot> But that means you can’t fuzz all messages at once I think it will be better this way tho 15:34 < lndbot> Unless you have a good computer 15:35 < lndbot> We can totally split up the future work if you want 15:37 < tuxx> pm'd u 15:46 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 240 seconds] 15:52 < molz> tuxx, you can't pm someone on slack 15:52 < molz> tuxx, unless you pm him from your slack account 16:02 < tuxx> molz: yup 17:00 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 17:16 -!- thomasanderson [~thomasand@2607:fb90:5dd:b7b4:5505:6e12:5f70:fb5f] has joined #lnd 17:27 -!- bralyclow [~bralyclow@76-202-84-204.lightspeed.tukrga.sbcglobal.net] has joined #lnd 17:32 -!- bralyclow [~bralyclow@76-202-84-204.lightspeed.tukrga.sbcglobal.net] has quit [Ping timeout: 250 seconds] 17:35 -!- thomasanderson [~thomasand@2607:fb90:5dd:b7b4:5505:6e12:5f70:fb5f] has quit [Remote host closed the connection] 17:39 -!- thomasanderson [~thomasand@2607:fb90:5d5:1ff2:b0d7:7ba3:e569:eb1] has joined #lnd 17:48 -!- ddustin [~ddustin@unaffiliated/ddustin] has quit [Remote host closed the connection] 18:05 -!- frib [~dynorsau@pool-71-167-9-152.nycmny.fios.verizon.net] has joined #lnd 18:13 -!- e4xit [~e4xit@cpc123762-trow7-2-0-cust7.18-1.cable.virginm.net] has quit [Ping timeout: 246 seconds] 18:18 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 18:19 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd 18:34 -!- thomasanderson [~thomasand@2607:fb90:5d5:1ff2:b0d7:7ba3:e569:eb1] has quit [Remote host closed the connection] 18:50 -!- ddustin [~ddustin@unaffiliated/ddustin] has joined #lnd 19:13 -!- frib [~dynorsau@pool-71-167-9-152.nycmny.fios.verizon.net] has quit [Quit: Leaving] 19:22 -!- frib [~dynorsau@pool-71-167-9-152.nycmny.fios.verizon.net] has joined #lnd 20:07 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Ping timeout: 245 seconds] 20:09 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 20:29 -!- github-lnd [github-lnd@gateway/service/github.com/x-lhcxijstybesjxpp] has joined #lnd 20:29 -github-lnd:#lnd- [lnd] orbitalturtle opened pull request #2363: Deprecate IncorrectHtlcAmount (master...Deprecate-FinalIncorrectHtlcAmount) https://git.io/fhJrF 20:29 -!- github-lnd [github-lnd@gateway/service/github.com/x-lhcxijstybesjxpp] has left #lnd [] 20:31 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #lnd 20:32 -!- Eagle[TM] [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 240 seconds] 22:40 -!- manantial [~tecnecio@unaffiliated/manantial] has joined #lnd