--- Day changed Tue Oct 17 2017 00:01 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has quit [Remote host closed the connection] 00:01 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has joined #lnd 00:05 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 00:20 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 00:20 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #lnd 00:21 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has joined #lnd 00:25 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 00:25 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 00:28 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 00:42 -!- deusexbeer [~deusexbee@093-092-181-081-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 252 seconds] 01:09 -!- Emcy [~MC@unaffiliated/emcy] has joined #lnd 01:09 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 01:25 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 01:30 -!- lxer [~lx@ip5f5bd5a9.dynamic.kabel-deutschland.de] has joined #lnd 01:36 -!- c0d3r [bcf3ac08@gateway/web/freenode/ip.188.243.172.8] has joined #lnd 01:37 < c0d3r> hello there! 01:48 -!- sycofly [~sycofly@121.99.240.44] has joined #lnd 01:52 -!- sycofly_ [~sycofly@121.99.240.44] has joined #lnd 01:53 -!- sycofly [~sycofly@121.99.240.44] has quit [Ping timeout: 240 seconds] 01:55 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-vbtkvbdrfsnjteoj] has quit [Quit: Connection closed for inactivity] 01:55 -!- alreadylate [~textual@c-250e71d5.153-1-64736c10.cust.bredbandsbolaget.se] has quit [] 02:07 < stevenroose> Anyone that can borrow me 350? lntb3500n1pv7t3aqpp5clyszkuk87djw7t38jqltudy4a6gpjjdv5neuyur6vh78tsuxpssdqcv9mk2um0d4jjqar9wd6xjmn8xqyz5vqjwpxljcxjqfmq8tar8exjru98cc2pr9v5n0kkpr02tdvw7nelhek6yp3dhy4eqxqkw0y7uv9xhpf5l7zsj44rds927cfzvuk33f0fzgpzrmz7e 02:12 < c0d3r> I have some questions about coding 02:12 < c0d3r> Does anyone can discuss it with me? 02:15 < fronti> stevenroose: i tried but: "payment_error": "unable to find a path to destination", 02:16 -!- johanth_ [uid223041@gateway/web/irccloud.com/x-zjvudovifpyiccmv] has joined #lnd 02:16 < stevenroose> c0d3r: I can try 02:16 < stevenroose> fronti: that's too bad 02:16 < stevenroose> fronti: interested in a channel? 02:17 < fronti> stevenroose: why not :) 02:17 * fronti is still trying to understand and test 02:17 < fronti> stevenroose: to make sure testnet or? :) 02:18 < stevenroose> fronti: you should actually be able to create/propose a channel with my based on the paymetn request 02:18 < stevenroose> yeah testnet ofz 02:18 < stevenroose> ofc 02:19 < fronti> [lncli] rpc error: code = Unknown desc = unable to find peer nodeID(0282d04010afaf9230b7711ee55e17637c95e6253e0cd72bef45bb30ff586278c9), peerID(0) 02:19 < fronti> i decoded the payment request and use the destination, is this the right way 02:22 < c0d3r> ok 02:24 < c0d3r> You know that node is for single user 02:24 < c0d3r> Rght? 02:28 < c0d3r> So now I'm exploring ability to make node multi user 02:30 < c0d3r> And the main question is how to change node interface so it'll be able used by several users? 02:30 < c0d3r> Any suggestions? 02:32 < stevenroose> c0d3r: you mean lnd in general? 02:32 < stevenroose> fronti: hmm, add @lightning.roose.io maybe 02:35 -!- c0d3r [bcf3ac08@gateway/web/freenode/ip.188.243.172.8] has quit [Ping timeout: 260 seconds] 02:35 < stevenroose> Restarting lnd, it somehow lost connection to the btcd backend 02:35 -!- c0d3r [bcf3ac08@gateway/web/freenode/ip.188.243.172.8] has joined #lnd 02:36 < c0d3r> Hello again) 02:36 < stevenroose> hi 02:36 < c0d3r> Did you see my question? 02:36 < stevenroose> stevenroose | c0d3r: you mean lnd in general? 02:36 < c0d3r> Yep 02:37 < fronti> stevenroose: maybe a problem on testner. on 2 machines i have in btcd 2017-10-17 11:18:34.368 [INF] CHAN: FORK: Block 00000000c113ed27f8577087ac625b5a2256ad767d41516ffc2c7952395ce58e forks the chain at height 1210422/block 000000009c07340f797ff6c4dc3abb1b0fd99a130c825d8fbf1f570858364298, but does not cause a reorganize 02:38 < stevenroose> I'm at 1210424 02:39 < stevenroose> (00000000f0e0e6b73a3e08797019f7fd8beaa0dbd6358349a2fbdce444eac52d) 02:39 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has joined #lnd 02:40 < fronti> your lnd is still starting i guess as I got a connection refused 02:40 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has quit [Client Quit] 02:41 < stevenroose> It just seems to have crashed: https://gist.github.com/stevenroose/fe0d42b1199c83de2e5b6069cd09f401 02:41 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has joined #lnd 02:42 < stevenroose> And yes starting takes a long time somehow (hangs on Wallet Opened). I suspect its regarding key derivation 02:43 < stevenroose> No pending channels though 02:43 < stevenroose> Crashed again 02:43 < stevenroose> I'll open an issue for that 02:51 < stevenroose> fronti: what version of lnd are you running? (commit hash) 02:51 < stevenroose> Somehow lnd started crashing after our connection. I'm thinking we might have an incompatibility and mine stored an outdated message yours sent to me 02:52 < stevenroose> Or a too new message 02:57 < fronti> stevenroose: while we are testing i did an update. so i have since 5 minutes (or so) the latest git 02:57 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 02:58 < stevenroose> fronti: which one did you have when you connected to me? 02:58 < stevenroose> I have like a week old, let me check the diff with origin/master 02:58 -!- Emcy [~MC@unaffiliated/emcy] has joined #lnd 02:58 < fronti> not sure.. i installed 4 days ago 02:59 < fronti> i'm not that familar with git to find out which versions :( 02:59 < fronti> i know i have sometime to learn git more than git pull and git clone :) 03:00 < stevenroose> So you connected before updating? Hmm, 4 days ago, that's the 13th? 03:01 < fronti> yes 03:02 < stevenroose> There's commits the 11th and the 14th, so I guess you were on f20cb89982e0d9a66cf797383693241bf6c4acb5 03:02 < fronti> i found in the .git: ORIG_HEAD:f20cb89982e0d9a66cf797383693241bf6c4acb5 03:03 < fronti> <- have to work something else.. be back later. 03:05 < stevenroose> Haha, mine is also from the 14th, so I got the same version as you.. That's even more strange 03:08 -!- sycofly_ [~sycofly@121.99.240.44] has quit [Quit: This computer has gone to sleep] 03:10 < c0d3r> so.. 03:10 < stevenroose> c0d3r: the problem with making lnd multiuser is that there is a single "wallet" notion 03:11 < stevenroose> What kind of multi-user do you want? I guess you could keep track of users on top of lnd 03:11 < stevenroose> Like most hosted wallets/exchanges do with their nodes 03:12 < c0d3r> For example: i made web service to let users micro payments to many shops and services online 03:13 < c0d3r> They pay to my service some btc and it is their balance in my service 03:14 < c0d3r> So i'm like an aggregator 03:14 < stevenroose> You could keep track of who owns what in your own program 03:14 < c0d3r> I assume they trust my service 03:15 < stevenroose> And then interact with lnd when a user wants to make a payment and keep track of what incoming lnd payments correspond to what users 03:15 < stevenroose> That's the most common approach, imo 03:16 < c0d3r> Ok thank you for now 03:16 < c0d3r> I'll thin more) 03:16 < c0d3r> think 03:16 < stevenroose> Any time 03:27 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has quit [Remote host closed the connection] 03:41 -!- alanc [~alanc@109.255.196.64] has joined #lnd 03:46 -!- mnkk___ [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has joined #lnd 03:53 -!- c0d3r [bcf3ac08@gateway/web/freenode/ip.188.243.172.8] has quit [Ping timeout: 260 seconds] 03:56 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has quit [Remote host closed the connection] 03:56 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has joined #lnd 04:10 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 04:11 -!- Emcy [~MC@unaffiliated/emcy] has joined #lnd 04:16 -!- Stu [52101637@gateway/web/freenode/ip.82.16.22.55] has joined #lnd 04:19 < Stu> Is it too early to start looking to build technology on top of lnd to target a release for April next year? I've got a bitcoind based system up and running but I'd like to migrate to LND but not really too sure if this is feasible to start migrating yet. Any pointers on where to begin? (My project is in node.js and uses bitcoind rpc calls) 04:21 < Sentineo> I think lnd is not working with bitcoind 04:21 < Sentineo> but with btcd 04:21 < Sentineo> a go impelemntation 04:21 < Sentineo> lightningd is for bitcoind I think 04:22 < Sentineo> but the RPC calls are maybe compatible, in that case you do not really care 04:24 < Stu> excellent, thanks Sentineo! Would you say btcd is a better backend for building things that bitcoind? Currently I have a mysql db/bitcoind(s) setup and feels a bit... well micky mouse... but I'm just an avg programmer so not going to make my own wallet but want something I know can scale without relying on a 3rd party provider 04:26 < Sentineo> btcd is just the way to peer with the bitcoin network for lnd 04:26 < Sentineo> bitcoind is for lightningd 04:26 < Sentineo> so btcd and bitcoind should be pretty similar from functionality - now I do not know about resource consumptions, etc. others can tell 04:27 < Stu> do people just use btcd because it's written in 'go' then? Would love to know why people use a different implementation over the original reference implementation yet... 04:28 < Sentineo> probably easier to understand :) as lnd is in go 04:29 < Sentineo> now sure though ... molz might know the answer for you 04:29 < Sentineo> stay around, they will come in later (us is still sleeping for example) 04:41 < Stu> ok, thanks again. Damn another language to learn ;) 04:44 < Sentineo> yeah 04:44 < Sentineo> I know nodejs as well 04:44 < Sentineo> would be nice to have everything in JS now :P 04:44 < Sentineo> but they say go is easy, but still ... we are lazy creatures 04:53 -!- c0d3r [bcf3ac08@gateway/web/freenode/ip.188.243.172.8] has joined #lnd 05:17 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 05:17 -!- Emcy [~MC@unaffiliated/emcy] has joined #lnd 05:21 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 05:21 -!- Emcy [~MC@unaffiliated/emcy] has joined #lnd 05:26 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Remote host closed the connection] 05:26 < lxer> please don't. JS is terrible 05:30 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 05:31 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 05:37 -!- Stu [52101637@gateway/web/freenode/ip.82.16.22.55] has quit [Ping timeout: 260 seconds] 06:17 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has quit [] 06:34 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has joined #lnd 06:36 -!- aakselrod [~aakselrod@2601:281:c702:8621:4851:ae29:ff70:4f68] has quit [Quit: Leaving] 06:38 -!- aakselrod [~aakselrod@gateway/vpn/privateinternetaccess/aakselrod] has joined #lnd 06:39 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has quit [Ping timeout: 260 seconds] 06:42 -!- esotericnonsense [~esotericn@gateway/vpn/privateinternetaccess/esotericnonsense] has quit [Ping timeout: 260 seconds] 06:44 < stevenroose> Sentineo: (since Stu left), personally for me the reason for wanting to use btcd is because I think a one-implemenation situation is dangerous 06:45 < Sentineo> lxer: JS is not terrible, but people are terybly trying to use it class-i way, not prototype way as it should be. And make ugly .prototype.methodName shit code 06:45 < stevenroose> It first of all makes the protocol design too code-centric but also makes it harder to disagree with the decisions from Core. Not that I have up till now, but it might happen that the majority of the community is against the then-main devs of Core 06:45 < stevenroose> And for non-regular devs of Core, it's hard to branch off. 06:45 < Sentineo> stevenroose: yeah a valid point, but in a consensus driven software a different implementation makes a risk for a fork 06:46 < stevenroose> And yeah I have to agree with lxer that JS is horrible ;) 06:46 < Sentineo> are there reasons for that or just "you dislike it". 06:46 < stevenroose> Sentineo: true. the protocol should eventually come pretty stable though. I mean changes should be tested for long times for compatibility etc 06:47 < stevenroose> I dislike it because using it in the past made me not want to use it anymore :) Mainly lack of typing, no proper typing (ugly prototype hacks instead), lack of decent error handling, ... 06:48 < stevenroose> In JS, 90% of things that should not be possible just work and do something random and 10% crash the system 06:48 < stevenroose> Like the famous [] + {} :D 06:48 < Sentineo> famous? I do not know that one 06:49 < Sentineo> I know : { : | :&}:; 06:49 < stevenroose> Theres some of those "what would this do in JS" 06:49 < stevenroose> thats not JS, thats shell ;) 06:49 < Sentineo> right 06:49 < stevenroose> Like ["10", "10", "10"].map(parseInt) 06:49 < Sentineo> I read the book series you do not know JS and it kind of turned my view 06:50 < stevenroose> I'm happy with Go :) 06:51 < stevenroose> And I used do a lot of Dart in the past, just for fun 06:51 < stevenroose> I came from Java in uni so Dart was still very familiar but very free and cumbersome 06:51 < stevenroose> And can compile to JS ;) 06:52 < Sentineo> I should learn java 06:52 < Sentineo> I am not a programmer 06:52 < Sentineo> and yeah that ["10","10"] thins is weird :P 06:52 < Sentineo> it must be related to this not being set well 06:53 < stevenroose> No it's related to the fact that .map is JS is stupid. Normally map takes one argument and produces one return value 06:53 < stevenroose> but in JS, the functioon in map gets 1, 2 or 3 arguments depending on how many it can get, 1 being the value, 2 the index and 3 the total list 06:54 < stevenroose> and parseInt has a second argument that allows you to set the base 06:56 -!- alreadylate [~textual@37-247-1-221.customers.ownit.se] has quit [Read error: Connection reset by peer] 06:56 < Sentineo> i c 06:56 < lxer> in python I can do the same with halve the code. But what bothers me about JS is the libraries and dependcies. it never just works. So I gave up on using it. 06:56 < Sentineo> JS is stupid :D 06:56 < stevenroose> so you get "10" base 0 (which means default base 10), which is 10, "10" base 1, which makes no sense, thus NaN, and "10" base 2, which is 2 06:56 < stevenroose> so ["10", "10", "10"].map(parseInt) returns [10, NaN, 2] 06:56 < stevenroose> :D 06:57 < Sentineo> yeah I saw that, tried it 06:59 < Sentineo> how steep is go's learning curve? 06:59 < Sentineo> I know python, too 06:59 < Sentineo> I mean I can read the syntax, not understand code - that is kung fu 06:59 < stevenroose> Hmm, good question 07:00 < stevenroose> It's not steep to be able to do things (you'll need Google though, but thats the case for every language). But it's a bit harder to get into the best practices and paradigms that are used 07:01 < stevenroose> Like there are many things that you will be able to solve yourself but there will be a slightly (or largely) more efficient one that like 90% of projects use so you kinda want to use as well :p 07:02 -!- c0d3r [bcf3ac08@gateway/web/freenode/ip.188.243.172.8] has quit [Ping timeout: 260 seconds] 07:02 < Sentineo> so why wasn't the language of choice python for example? 07:03 < stevenroose> Before doing my first real project in Go (last year), I had been reading pull requests of btcd for some years and it helps understand some of the good practices. (davec is a good developer allright :p) 07:04 < stevenroose> I guess mostly for efficiency and typing reasons. And for lnd specifically I'd say because of btcd or even just personal preference of roasbeef. You'll have to ask him :) 07:04 < stevenroose> You want something with strong concurrency for such a network-driven application and good typing far such a data-critical one. 07:05 < aakselrod> the people who started lnd (tdryja, josephpoon, roasbeef) had all worked with btcsuite before 07:05 < aakselrod> was a natural choice, everyone was familiar with it 07:05 < stevenroose> aakselrod: it's a solid code base as well 07:06 < aakselrod> aye 07:12 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-girtjfkekblcqhra] has quit [Quit: Connection closed for inactivity] 07:22 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 07:22 -!- Emcy [~MC@unaffiliated/emcy] has joined #lnd 07:55 < Sentineo> thanks for sheding insight 07:55 < Sentineo> stevenroose: you were "moderating" pull requests? 07:56 < stevenroose> Haha, not really moderating, in the sense that I didn't have enough knowledge on the project and Go to give meaningful feedback 07:57 < stevenroose> Just what you would call a lurker, trying to make a bit sense of it in my spare time 08:17 < Sentineo> ah yeah 08:17 < Sentineo> a good way to learn so it seems though 08:17 < Sentineo> I would gladly halp, but hard to start :D 08:17 < Sentineo> so am learning maths and things needed to grasp this stuff :D 08:35 -!- c0d3r [bcf3ac08@gateway/web/freenode/ip.188.243.172.8] has joined #lnd 08:44 -!- deusexbeer [~deusexbee@079-170-136-200-dynamic-pool-adsl.wbt.ru] has joined #lnd 09:31 -!- c0d3r [bcf3ac08@gateway/web/freenode/ip.188.243.172.8] has quit [Quit: Page closed] 09:55 -!- labullecrypto [6014984d@gateway/web/freenode/ip.96.20.152.77] has joined #lnd 09:56 < labullecrypto> Hi, I am trying to test the lightning network neutrino app with a friend. I am having trouble understanding what my HostIP should be, more specifically which ports should I forward for the app to properly be able to interact with the network. 09:56 < labullecrypto> Could you please help me with this ? 09:56 -!- louiscn [4e741918@gateway/web/freenode/ip.78.116.25.24] has joined #lnd 10:00 < Sentineo> not sure, but netstat -tpl can help you see ports and apps using it 10:00 < Sentineo> do not know the ports sadly ... 10:04 < labullecrypto> Thanks ! I'll get started with that 10:12 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-weedtecshdoqbmev] has joined #lnd 10:18 < Sentineo> yw 10:22 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 252 seconds] 10:25 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Ping timeout: 248 seconds] 10:25 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Ping timeout: 248 seconds] 10:25 -!- whythat [~whythat@gateway/tor-sasl/whythat] has quit [Ping timeout: 248 seconds] 10:25 -!- abcmonero [~abcmonero@gateway/tor-sasl/abcmonero] has quit [Ping timeout: 248 seconds] 10:25 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 248 seconds] 10:36 < aakselrod> labullecrypto: for inbound lnd connections, you need TCP 9735 10:40 < labullecrypto> Thanks ! Also, are there any active nodes I can use ? 10:41 < aakselrod> lnd has a feature called "discovery" which will connect you to active nodes to download the network graph, and "autopilot" that will automatically create channels for you if you have enough coin to do so 10:44 < eck> what's the minimum go version required to build lnd? 10:44 < labullecrypto> I am using neutrino, but I am not sure I have autopilot.... ? 10:44 < eck> it appears to be at least 1.8? i'm getting build errors with 1.7.4 10:45 < aakselrod> it's included with the lnd app, labullecrypto 10:45 < aakselrod> eck: it's 1.8+, we recommend 1.9 10:45 < eck> ok 10:45 < eck> thanks 10:45 < aakselrod> we're always current+previous minor version (so currently, 1.8 and 1.9) using the latest patch for that version 10:46 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd 10:53 -!- abcmonero [~abcmonero@gateway/tor-sasl/abcmonero] has joined #lnd 10:53 -!- whythat [~whythat@gateway/tor-sasl/whythat] has joined #lnd 10:53 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 10:56 < sturles> How do I get go 1.8 on Debian 9? I have golang-1.8-go installed, but go version still report 1.7. If I remove golang-1.7-go, I have no go at all. 10:57 < aakselrod> sturles: uninstall OS-distributed go packages and install from https://golang.org/, unfortunately :( 10:58 < sturles> :-( 11:01 < sturles> I even upgraded to Debian 9 just to get the golang-1.8-go installed without too much trouble. I prefer to stay on supported packages which will be upgraded when security holes are found. :-/ 11:03 -!- labullecrypto [6014984d@gateway/web/freenode/ip.96.20.152.77] has quit [Quit: Page closed] 11:04 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-xlmijyqbsdmkvzsa] has joined #lnd 11:05 <@roasbeef> stevenroose: you're using btcd master, you need to use my fork still for two reasons: the witness serialization changed in btcd master, and also my fork has the neutrino serving code which btcd master doesn't 11:15 < aakselrod> sturles: if there's a way, i don't know it. i'm not running vanilla debian, unfortunately, so that's what i resort to (with manual updates). 11:18 < eck> sturles: it's in stretch-backports 11:19 < eck> sudo apt-get install -t stretch-backports golang 11:26 < sturles> Thanks! It worked. :-) 11:29 < eck> it may be worth adding the instructions for installing golang from stretch-backports to the build docs 11:29 -!- louiscn [4e741918@gateway/web/freenode/ip.78.116.25.24] has quit [Ping timeout: 260 seconds] 11:52 < stevenroose> roasbeef: is neutrino used when a btcd rpc is provided? 11:58 < sturles> lnd only talks to btcd, not bitcoind? 12:00 < jimpo> Pretty sure if you need to explicitly enable neutrino mode with --neutrino.active, whereas if you don't do that and provide btcd RPC, it'll use the btcwallet backend 12:01 < aakselrod> it uses btcwallet either way 12:01 < aakselrod> we have a patched btcwallet that can use neutrino 12:01 < aakselrod> i'm working on (it's on the back burner atm) a bitcoind interface for btcwallet and lnd 12:03 < aakselrod> but right now, lnd (via btcwallet) can only talk to btcd via RPC or via neutrino... bitcoind is not supported at all yet. 12:06 < Sentineo> what is neutrino btw? 12:06 < aakselrod> neutrino is a light client library used by our patched btcwallet and by lnd... it's an alternative to a BIP37 implementation that attempts to preserve privacy and not hammer full nodes' resources as much 12:08 < aakselrod> i can link the BIP but it's not exactly current, will be updated RealSoonNow(TM) 12:08 < aakselrod> https://github.com/Roasbeef/bips/blob/master/gcs_light_client.mediawiki 12:08 < aakselrod> compression algorithm is changing a bit, some of the messages are changing a bit, and the service flag is changing as well 12:08 < Sentineo> nice 12:09 < aakselrod> we hope to have it updated in the next few days and request a BIP number 12:18 <@roasbeef> stevenroose: to answer that question...ask yourself what neutrino is ;) 12:18 <@roasbeef> stevenroose: in general you'll have a snappier experience using the rpc mode 12:22 -!- eugene_ [c7a78923@gateway/web/freenode/ip.199.167.137.35] has joined #lnd 12:36 < stevenroose> roasbeef: well, that's why I was confused, a light client is kinda unnecessary when you have a full node 12:36 <@roasbeef> sure, the user gets a choice 12:36 < stevenroose> so the only incompatibility for now is the witness serialisation 12:36 <@roasbeef> just as with any other cryptocurrency software taht requires a consensus anchor 12:37 < stevenroose> what's the holdup for moving to btcd#master on that? I'd be willing to help out.. 12:37 <@roasbeef> please re-read my initial response 12:39 < stevenroose> I understand the witness seialization changed. So lnd needs to be upgraded to use the new one? 12:39 <@roasbeef> that change was only injson encoding 12:40 <@roasbeef> btcd master doesn't have the code to support neutrino yet 12:41 < stevenroose> (neutrino currently only works if it finds roasbeef/btcd peers, right?) 12:42 < stevenroose> Well, I'd think if lnd moved to btcsuite/master for rpc, you could still point neutrino users to roasbeef/btcd if they want to setup a serving node. Or does neutrino also directly use code (libs, ..) from roasbeef/btc*? 12:45 <@roasbeef> nope there are other dependancies like btcwallet and btcutil and some portions of neutrino 12:45 <@roasbeef> if it were possible at this current point, we would've done it already 12:46 < aakselrod> we're working toward it but it's only one of our priorities :) 12:50 -!- eugene_ [c7a78923@gateway/web/freenode/ip.199.167.137.35] has quit [Ping timeout: 260 seconds] 12:52 < stevenroose> Is there things I can work out with other than looking into issues? 12:54 -!- mnkk___ [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has quit [] 12:57 <@roasbeef> stevenroose: as in w.r.t contribution? keep testing and report issues, or attempt to fix an issue that adds/modifies functionality 13:00 -!- mnkk___ [~mnk4@ip5f5ae92a.dynamic.kabel-deutschland.de] has joined #lnd 13:03 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has quit [Quit: .] 13:06 -!- PaulCapestany [~PaulCapes@ip72-209-228-52.dc.dc.cox.net] has joined #lnd 13:06 < stevenroose> perfect 13:07 < stevenroose> Have some more spare time now, so I'm happy to 13:07 < stevenroose> Eating now 13:17 -!- chjj [~chjj@unaffiliated/chjj] has quit [Ping timeout: 258 seconds] 13:50 < fronti> just a question, i do a connect with lncli connect .. result is fine, if I try to connect again he told "already connected to peer" fine so i assume a route is open between these nodes. if I then do a queryroute i got unable to find a path to destination.. i did not understand 13:50 -!- dakk [~dakk@62-11-224-118.dialup.tiscali.it] has quit [Ping timeout: 260 seconds] 13:51 < aakselrod> fronti: a connection is only a TCP connection; a channel would need to be open to the node (meaning you need to commit money to it) in order to send money through it. 13:55 < fronti> ok i will try thanks 14:14 -!- alanc [~alanc@109.255.196.64] has quit [Ping timeout: 240 seconds] 14:17 -!- castl2342 [ubuntu@gateway/vpn/mullvad/x-mxbafnxusfnthzpp] has quit [Ping timeout: 260 seconds] 14:20 < fronti> ok, with an channel open it works well :) thanks 14:24 < aakselrod> excellent :) 14:28 -!- castl2342 [ubuntu@gateway/vpn/mullvad/x-fkbteaygrbpoxemw] has joined #lnd 14:36 -!- chjj [~chjj@unaffiliated/chjj] has joined #lnd 14:45 -!- deusexbeer [~deusexbee@079-170-136-200-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 240 seconds] 14:45 -!- deusexbeer [~deusexbee@080-250-077-012-dynamic-pool-adsl.wbt.ru] has joined #lnd 15:05 -!- eugene_ [c7425bea@gateway/web/freenode/ip.199.66.91.234] has joined #lnd 15:13 -!- olliey [1f32aa91@gateway/web/freenode/ip.31.50.170.145] has joined #lnd 15:17 -!- olliey [1f32aa91@gateway/web/freenode/ip.31.50.170.145] has quit [Ping timeout: 260 seconds] 15:42 -github-lnd:#lnd- [lnd] Roasbeef closed pull request #375: Add upload of integration logs from TravisCI builds (fixes #302) (master...ci_logging) https://git.io/vdKbN 16:15 -!- lxer [~lx@ip5f5bd5a9.dynamic.kabel-deutschland.de] has quit [Ping timeout: 252 seconds] 16:22 -!- eugene_ [c7425bea@gateway/web/freenode/ip.199.66.91.234] has quit [Ping timeout: 260 seconds] 16:24 -!- eugene_ [c7a78943@gateway/web/freenode/ip.199.167.137.67] has joined #lnd 16:35 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has joined #lnd 16:43 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has quit [Remote host closed the connection] 16:43 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has joined #lnd 16:48 -!- Emcy [~MC@unaffiliated/emcy] has joined #lnd 16:51 -!- rhavar [uid237883@gateway/web/irccloud.com/x-iptgikiwuufxvepg] has joined #lnd 17:46 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has quit [Read error: Connection reset by peer] 17:46 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has joined #lnd 17:59 -!- dabura667 [~dabura667@p98110-ipngnfx01marunouchi.tokyo.ocn.ne.jp] has joined #lnd 18:18 -!- esotericnonsense [~esotericn@gateway/vpn/privateinternetaccess/esotericnonsense] has joined #lnd 18:40 -!- deusexbeer [~deusexbee@080-250-077-012-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 18:41 <@roasbeef> added msg summaries to have something other than trace to watch node activity 18:41 <@roasbeef> 2017-10-17 18:40:26.416 [DBG] PEER: Sending NodeAnnouncement(node=03ff7e409ae429f52b05917d8cce7b27fea8406aca37026c425c8d2ed32829eaf8, update_time=2017-10-17 18:37:48 -0700 PDT) from 127.0.0.1:10019 18:41 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-weedtecshdoqbmev] has quit [Quit: Connection closed for inactivity] 18:51 -!- eugene_ [c7a78943@gateway/web/freenode/ip.199.167.137.67] has quit [Ping timeout: 260 seconds] 19:11 -!- rhavar [uid237883@gateway/web/irccloud.com/x-iptgikiwuufxvepg] has quit [Quit: Connection closed for inactivity] 19:45 -github-lnd:#lnd- [lnd] Roasbeef pushed 7 new commits to master: https://git.io/vdHeE 19:45 -github-lnd:#lnd- lnd/master b7e1933 Olaoluwa Osuntokun: peer: add message summaries of sent/recv'd message for debug log level... 19:45 -github-lnd:#lnd- lnd/master f3b8c91 Olaoluwa Osuntokun: test: bump up logging level for integration test nodes to debug... 19:45 -github-lnd:#lnd- lnd/master 03f9479 Olaoluwa Osuntokun: discovery: only interpret remote announcements as pre-mature... 19:49 -!- Emcy [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 19:49 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #lnd 20:15 -!- Emcy_ [~MC@unaffiliated/emcy] has quit [Read error: Connection reset by peer] 20:24 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-xlmijyqbsdmkvzsa] has quit [Quit: Connection closed for inactivity] 20:38 -!- andi___ [b4fedbef@gateway/web/freenode/ip.180.254.219.239] has joined #lnd 20:39 -!- andi___ [b4fedbef@gateway/web/freenode/ip.180.254.219.239] has quit [Client Quit] 20:51 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-fghskwtkrmkljqgt] has joined #lnd 21:18 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has quit [Ping timeout: 260 seconds] 22:00 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has joined #lnd 22:01 <@roasbeef> dat new wu tang tho... 22:11 -!- castl2342 [ubuntu@gateway/vpn/mullvad/x-fkbteaygrbpoxemw] has quit [Ping timeout: 248 seconds] 22:23 -!- Emcy [~MC@unaffiliated/emcy] has joined #lnd 22:24 -!- castl2342 [ubuntu@gateway/vpn/mullvad/x-sphrrstaneeagfig] has joined #lnd 22:34 < jimpo> I'm having trouble understanding the purpose of the logCommitTimer in the HTLC link. Is it just there to recover from the case where this fails? https://github.com/lightningnetwork/lnd/blob/master/htlcswitch/link.go#L818 22:35 < jimpo> (note: not talking about the batchTimer, that one makes sense) 22:40 <@roasbeef> it's there in order to address a possible state hwerein due to a simultaenous update, some of my updates wen're actually committed 22:41 <@roasbeef> were not 22:43 <@roasbeef> in the simulteanous add+sig case, both sides end up with a commitment state that doesn't cover the HTLC that they just sent 22:44 <@roasbeef> so after I get your sig, I revoke which then means by sig covers only your HTLC 22:44 <@roasbeef> we then must do another round to get back in sync 22:45 <@roasbeef> not that if the commit sig message included the current log index (as it did before the state machine got nerfed) this state couldn't arise 22:45 <@roasbeef> main benefit of the implicit ack is that it let's me "un add" an HTLC you've sent to me for w/e reason 22:47 <@roasbeef> #373 looks good tested locally and also amongst other existing nodes in the wild 22:47 < jimpo> cool 22:47 -github-lnd:#lnd- [lnd] Roasbeef closed pull request #373: lnwire: Refactor feature vector and observe initial_routing_sync bit (master...features) https://git.io/vdo9b 22:47 -!- alanc [~alanc@109.255.196.64] has joined #lnd 22:47 < jimpo> I think that makes sense with regards to the switch, still trying to play it out in my head 22:48 <@roasbeef> yeh it's one of those things you need to write out, and manually transition to see how the resulting commitment states end up 22:53 -!- pvs_ [d13a93f1@gateway/web/freenode/ip.209.58.147.241] has joined #lnd 22:55 <@roasbeef> ticker values chosen atm obvs super arbitrary 22:57 -!- pvs_ [d13a93f1@gateway/web/freenode/ip.209.58.147.241] has left #lnd [] 22:58 <@roasbeef> with the logs of executing lnd nodes in travis being exported, now easy to track down that most of the lingeirng integration test flakes are just due to timing issues 22:59 < jimpo> sweet 23:06 -!- muneeb [d13a93f1@gateway/web/freenode/ip.209.58.147.241] has joined #lnd 23:08 -!- sdfgsdfg [~sdfgsdfg@unaffiliated/sdfgsdfg] has quit [Remote host closed the connection] 23:10 -!- muneeb is now known as zrl 23:10 -!- zrl is now known as Guest75955 23:12 -!- Guest75955 [d13a93f1@gateway/web/freenode/ip.209.58.147.241] has quit [] 23:14 < jimpo> OK, with regards to this simultaneous update thing, the problem makes sense that the commitment chains can get out of whack because both nodes have a commitment that is missing their own updates 23:15 < jimpo> But it seems like this code (https://github.com/lightningnetwork/lnd/blob/master/htlcswitch/link.go#L810) should always force the second round of sigs/acks 23:15 < jimpo> without the timer being required *unless* updateCommitTx fails 23:17 -!- Emcy_ [~MC@unaffiliated/emcy] has joined #lnd 23:20 -!- Emcy [~MC@unaffiliated/emcy] has quit [Ping timeout: 248 seconds] 23:33 -!- dakk [~dakk@62-11-224-118.dialup.tiscali.it] has joined #lnd