--- Day changed Sat Mar 17 2018 00:25 -!- Pioklo_ [~Pioklo@5.83.71.43] has joined #lnd 00:35 -!- Pioklo_ [~Pioklo@5.83.71.43] has quit [Ping timeout: 264 seconds] 00:50 -!- grafcaps [~haroldbr@50.90.83.229] has joined #lnd 00:54 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 240 seconds] 00:56 -!- offerm [546f8b93@gateway/web/freenode/ip.84.111.139.147] has quit [Ping timeout: 260 seconds] 01:12 -!- kunla [~kunla@bl13-153-142.dsl.telepac.pt] has quit [Ping timeout: 260 seconds] 01:15 -!- grafcaps [~haroldbr@50.90.83.229] has joined #lnd 01:20 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 260 seconds] 01:29 -!- Bezpol [1f0043cc@gateway/web/freenode/ip.31.0.67.204] has quit [Quit: Page closed] 01:53 -!- LN-Hero [68eea966@gateway/web/freenode/ip.104.238.169.102] has quit [Ping timeout: 260 seconds] 01:54 -!- dezentralized_ [~yaaic@148.56.16.76] has joined #lnd 01:56 -!- bmbnct [9438104c@gateway/web/freenode/ip.148.56.16.76] has joined #lnd 01:56 -!- bmbnct [9438104c@gateway/web/freenode/ip.148.56.16.76] has quit [Client Quit] 01:59 -!- dezentralized_2 [~yaaic@148.56.16.76] has joined #lnd 01:59 -!- dezentralized_ [~yaaic@148.56.16.76] has quit [Read error: Connection reset by peer] 02:11 -!- iv4n [~iv4n@1.46.41.101] has quit [Ping timeout: 248 seconds] 02:16 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #lnd 02:21 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Ping timeout: 240 seconds] 02:23 -!- fusion441 [~fusion44@p2E59F745.dip0.t-ipconnect.de] has quit [Quit: Leaving.] 02:25 -!- t4sk [026cd586@gateway/web/freenode/ip.2.108.213.134] has joined #lnd 02:29 < zib> Feels like my lnd-0.4 is not processing blocks 02:29 < zib> "only height 513908 is known" 02:31 < zib> Known bug? It's a new install. Restarting fixed it. But sad it happened immedietly heh 02:33 -!- grafcaps [~haroldbr@50.90.83.229] has joined #lnd 02:38 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 260 seconds] 02:52 -!- fusion44 [~fusion44@p2E59F745.dip0.t-ipconnect.de] has joined #lnd 02:53 -!- fusion44 [~fusion44@p2E59F745.dip0.t-ipconnect.de] has left #lnd [] 03:10 -!- dezentralized_2 [~yaaic@148.56.16.76] has quit [Read error: Connection reset by peer] 03:12 -!- Styils [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 03:17 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #lnd 03:19 -!- naribia [adefec52@gateway/web/freenode/ip.173.239.236.82] has quit [Quit: Page closed] 03:21 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Ping timeout: 240 seconds] 03:44 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #lnd 03:53 -!- iv4n [~iv4n@1.46.41.101] has joined #lnd 04:07 -github-lnd:#lnd- [lnd] junderw opened pull request #864: [Feature] Add TLSExtraDomain to config (master...addtlsdomain) https://git.io/vxYFF 04:07 -!- ajph [~ajph@unaffiliated/ajph] has joined #lnd 04:18 < meshcollider> Veggen: yes bitcoind is *much* faster for IBD than btcd because core has made many efficiency improvements over the last few years, btcd development hasn't been very active unfortunately 04:25 < BB-Martino> I do have bitcoin.mainnet in the startup params. Is there any reason why it wouldn't go to mainnet? I still can't send any payments ("nable to apply channel update: unable to fetch chan point for chan_id=8620838226088: tx_index=#14103040 is out of range") 04:29 < BB-Martino> also, why is there no chan_id when I do listchannels? even if I wanted to close this, I wouldn't know from chan_id which channel it is 04:31 < BB-Martino> i do have one open channel, peculiar that its chan_id is 0 04:31 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has joined #lnd 04:38 < BB-Martino> restarted lnd, channel with channel_id = 0 disappeared, but still can't send any payments :( 04:48 -!- maurris [~maurris@unaffiliated/maurris] has joined #lnd 04:48 -!- deusexbeer [~deusexbee@093-092-177-253-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 265 seconds] 04:49 -!- deusexbeer [~deusexbee@093-092-176-212-dynamic-pool-adsl.wbt.ru] has joined #lnd 04:55 -!- camulos [~user@91.92.199.117] has joined #lnd 04:58 -!- kunla [~kunla@81.193.53.189] has joined #lnd 05:06 < BB-Martino> now lnd is also being flooded with messages such as: 05:06 < BB-Martino> 2018-03-17 12:04:52.343 [ERR] DISC: Router rejected channel edge: unable to fetch utxo for chan_id=564382617145180160, chan_point=f816d3b51dca71320c2b09e0df6cefad362c4baae3801325aab42da989e0ca55:0: target output has been spent 05:06 < BB-Martino> 2018-03-17 12:04:52.390 [ERR] DISC: Router rejected channel edge: unable to fetch utxo for chan_id=564383716621418496, chan_point=b2883c7b71391c2f3f70403c45475f583dd3a2b1eb93b2df2a6a12c91f43bb4a:0: target output has been spent 05:22 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Remote host closed the connection] 05:26 -!- ajph [~ajph@unaffiliated/ajph] has quit [Ping timeout: 256 seconds] 05:27 < t4sk> I also have a channel with chan_id 0 05:30 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 05:31 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 05:35 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 246 seconds] 05:37 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #lnd 05:38 -!- arihan [~arihan@2a02:c7f:d826:1901:b77d:77e8:1344:1e5f] has joined #lnd 05:40 -!- belcher [~belcher@unaffiliated/belcher] has joined #lnd 05:52 -!- LN-Hero [68eea914@gateway/web/freenode/ip.104.238.169.20] has joined #lnd 06:02 < LN-Hero> Hello all, does anyone have instructions on how to use the autopilot and mission control functionality? Thanks 06:03 < LN-Hero> Nevermind 06:03 < LN-Hero> Should have read the release notes more thoroughly 06:08 -!- LN-Hero [68eea914@gateway/web/freenode/ip.104.238.169.20] has quit [Ping timeout: 260 seconds] 06:10 <@mlz> BB-Martino, sounds like you're still running an older commit 06:10 -!- grafcaps [~haroldbr@50.90.83.229] has joined #lnd 06:11 < BB-Martino> really? 06:11 < BB-Martino> i git pull'd into a completely empty directory, it shouldn't be the case 06:11 < BB-Martino> went by the installation tutorial, 2018-03-17 13:07:29.787 [INF] LTND: Version 0.4.0-alpha 06:12 <@mlz> from your old node, before update, if you closed out all channels, withdrew your coins out from the LND wallet, delete the old .lnd database, then update your go version to 1.10, install dep, update LND, can't go wrong after these tasks 06:12 < BB-Martino> did all of that, except i'm using go-1.9 instead of go-1.10 06:15 < BB-Martino> Roasbeef suggested I may be on testnet. I started lnd with --bitcoin.mainnet so it shouldn't be the case but in the off chance that it is, how do I check this? 06:15 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 264 seconds] 06:19 <@mlz> BB-Martino, ok are you using btcd or bitcoind? 06:20 < BB-Martino> bitcoind 06:21 -!- ajph [~ajph@unaffiliated/ajph] has joined #lnd 06:23 <@mlz> BB-Martino, you were running on mainnet before the beta was released, correct? 06:24 < BB-Martino> For what it's worth, before I saw the announcement about 0.4 an earlier version has been running for weeks with the ability to send payments. What I did: close all channels, withdraw the money, halt lnd, install go 1.9, remove ~/go, remove ~/.lnd except lnd.conf, install a new lnd (with dep ensure, following the installation instructions to the letter), update the launcher to use --bitcoin.mainnet, send some money, open some channels, try to send a 06:24 < BB-Martino> payment 06:24 < BB-Martino> that's correct, yes 06:24 < BB-Martino> but all the db's have been removed 06:24 < BB-Martino> i'm not sure why it's trying to use a channel that i didn't open since the reinstall (i'm basing this on chan_id not appearing, not sure if it's relevant) 06:27 < BB-Martino> i'm being flooded to hell with these logs... i understand some peers may be trying to deal with channels opened on the previous instance, but seeing that I have a new wallet.db and new pubkey, it's surprising that they can make requests and everything not even having the right pubkey 06:28 < BB-Martino> I really just want to get this to work. I'd even consider reinstalling and starting from scratch, but I just did that, so.... 06:29 <@mlz> i have an old node still open and yes i do see these messages but my new node is not like this... (but my new node is brand new just got started never had a channel before) 06:30 < BB-Martino> mine either 06:30 < BB-Martino> the only common point is the ip & port. 06:30 <@mlz> you can set your debuglevel to "info", it will be less active 06:31 < BB-Martino> thanks for the tip. i might try that. for now my priority is being able to send any payments. 06:32 < BB-Martino> ps. i have "unconfirmed_balance": "288516" -- haven't tried opening a channel or did anything in 24 hours. something may be stuck 06:36 < t4sk> where can I find a list of all the options I can put in the lnd.conf? Is the sample.conf complete in that regard? 06:45 -!- rls [~rls@74.120.222.234] has quit [Read error: Connection reset by peer] 06:46 -!- rls [~rls@74.120.222.234] has joined #lnd 06:46 -!- catblitz [2e80ff6b@gateway/web/freenode/ip.46.128.255.107] has joined #lnd 06:47 < catblitz> hi guys, how can I launch lnd in autopilot mode? 06:47 <@mlz> BB-Martino, what is that "unconfirmed_balance"? an onchain tx? 06:51 < t4sk> catblitz pass --autopilot.active=1 06:53 < catblitz> t4sk: thank you ^^ 06:53 -!- JackH [~laptop@host-80-47-80-55.as13285.net] has joined #lnd 06:56 < BB-Martino> mlz: good question. 06:57 <@mlz> BB-Martino, where is it when you do the query? "pendingchannels"? 06:57 < BB-Martino> ah, someone must have closed a channel maybe, I do see one transaction with confirmations=2 in there 06:58 < BB-Martino> if you're asking about the unconfirmed_balance, it comes from listchaintxns 06:58 < BB-Martino> but no worries, it's fine, my main issue is still not being able to pay invoices 06:58 <@mlz> ah 06:59 <@mlz> many nodes are still down so i can imagine there's some disconnection in routing, your partner might have to have a direct channel with you 07:00 < BB-Martino> i was trying to pay the invoice on the yalls.org article (it's my go-to test invoice) 07:01 <@mlz> alexbosworth might be able to help 07:01 < BB-Martino> if there was an issue with routing in general, wouldn't it say "couldn't find a path..." 07:01 < BB-Martino> instead of telling me about a specific open channel i'm supposed to have which i don't really have 07:01 <@mlz> or unknownNextPeer 07:01 <@mlz> BB-Martino, when you try to pay that invoice, it tells you to open a channel with someone? 07:02 < BB-Martino> no, it gives the error message I pasted earlier. (Unable to apply channel update: unable to fetch chan point for chan_id=8620838226088: tx_index=#14103040 is out of range (max_index=0), network_chan_id=(*lnwire.ShortChannelID)(0xc420016ab4)(7:14103040:2216)) 07:02 -!- sovjet [~sovjet@user182.c2.sevnica.kabelnet.net] has joined #lnd 07:03 < BB-Martino> and i have another channel open now with chan_id = 0 07:03 <@mlz> oh maybe you were trying to pay yalls on testnet 07:03 < BB-Martino> out of nowhere. and i guess it'd be gone again if I restarted lnd. 07:03 < BB-Martino> yalls is mainnet 07:03 < BB-Martino> at least that article is 07:03 <@mlz> BB-Martino, what's the URL?? 07:03 < BB-Martino> https://mainnet.yalls.org/articles/97d67df1-d721-417d-a6c0-11d793739be9:0965AC5E-56CD-4870-9041-E69616660E6F/cdc9c4a9-b5bd-4b6d-a634-a982ea02a30d 07:04 <@mlz> hm 07:04 < BB-Martino> it was the first article I got and it's always worked like a charm on mainnet 07:04 < BB-Martino> does it work for you? can you pay the invoice? 07:05 <@mlz> i haven't tried, but alex said something about mainnet yalls might not be working 07:06 < BB-Martino> aw. is there any chance you could pm me an invoice? 07:06 < BB-Martino> i want to try to pay something generated by a fresh lnd on mainnet that's supposedly working 07:07 <@mlz> sure but my node doesn't have a channel with anyone yet 07:07 < BB-Martino> it'd be pointless, then. :( 07:08 < BB-Martino> if anyone can pm me an invoice from a 100% working node with channels connected, i'd appreciate it 07:08 <@mlz> im not sure who i want to open a channel with 07:09 <@mlz> blockstream store doesn't have cool hats 07:09 <@mlz> and bitrefill doesn't have amazon for where i am yet 07:11 < BB-Martino> so... i did 'openchannel' to your node, been waiting for ~50 seconds now for a result 07:11 -!- ChaoticMind [~ChaoticMi@2a03:8600:1001:1012::1005] has joined #lnd 07:13 <@mlz> BB-Martino, you are a very impatient person :P lol 07:14 <@mlz> BB-Martino, you should open a store on mainnet 07:14 < BB-Martino> Only with the unexpected things. If opening a channel was supposed to take between 2 seconds and 30 minutes i'd just go make a sandwich 07:14 < BB-Martino> but after 2-3 minutes of not doing anything, i get the feeling it's not going to work out. which is a shame, because both of us have a fresh install of lnd's latest version. 07:14 <@mlz> yup, and i'd go make some coffee :D 07:15 <@mlz> BB-Martino, opening a channel depends on an onchain tx, can't blame LN though 07:15 < BB-Martino> i'm not talking about waiting for confirmations 07:15 < BB-Martino> i'm talking about getting any type of response and the channel showing up in pendingchannels 07:16 < BB-Martino> i'm still waiting for the RPC command to return with a response 07:17 < BB-Martino> and now it's open \o/ - i'll ping you for a new invoice when it's active. 07:23 -!- grafcaps [~haroldbr@50.90.83.229] has joined #lnd 07:26 <@mlz> cool... you're the first to open to my exquisite node, thank you :D lol 07:26 <@mlz> to open a channel* 07:28 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 256 seconds] 07:44 -!- camulos [~user@91.92.199.117] has left #lnd [] 07:47 -github-lnd:#lnd- [lnd] aantonop opened pull request #866: Docs: Inconsistent ZMQ port numbers in examples (master...docs) https://git.io/vxOUx 07:50 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has joined #lnd 07:52 -github-lnd:#lnd- [lnd] adamrabie opened pull request #867: Update INSTALL.md (master...patch-1) https://git.io/vxOTZ 08:01 -!- grafcaps [~haroldbr@50.90.83.229] has joined #lnd 08:09 -!- catblitz [2e80ff6b@gateway/web/freenode/ip.46.128.255.107] has quit [Quit: Page closed] 08:15 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 246 seconds] 08:24 < baltakatei> Woo, now instead of `UnknownNextPeer` error, I'm getting `FeeInsufficient` error. Progress! 08:24 -!- grafcaps [~haroldbr@50.90.83.229] has joined #lnd 08:25 < baltakatei> Thank you to you good people who made a channel to my mainnet node. 08:28 <@mlz> baltakatei, doesn't say much what your issue is 08:34 < baltakatei> @mlz I'm still trying to understand what the error message lnd gives me by looking up things myself first before asking for help. I just started using lnd yesterday and thought I'd throw some disposable bitcoin into it to see if I can get it to work while blockchain fees are low. 08:36 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wailrdpaekjqdoga] has quit [Quit: Connection closed for inactivity] 08:38 < baltakatei> @mlz I received the `UnknownNextPeer` and `FeeInsufficient` errors while attempting to purchase stickers from the Blockstream store. 08:39 <@mlz> baltakatei, do you have a direct channel with Blockstream store? 08:40 < baltakatei> Last night I did not. Their node is the one with alias "SLEEPYARK", right? 08:42 <@mlz> yes 08:43 -!- Ulmo_Aptos [1804e4d5@gateway/web/freenode/ip.24.4.228.213] has joined #lnd 08:43 < Ulmo_Aptos> Foo 08:43 < baltakatei> @mlz, My node has no direct channel to their node. 08:44 < Ulmo_Aptos> Alright, here's the error I'm getting: lncli openchannel 031c527494f295220d26a1814c18e7db3f4f03203ce1a53a0b74b52ed570a3972a 9000000 7000000: "[lncli] rpc error: code = Code(202) desc = feerate_per_kw 7500 above maximum 6305" 08:44 < Ulmo_Aptos> But, then I tried setting a lower fee using --sat_per_byte, but that didn't have an effect. 08:45 < Ulmo_Aptos> How do I set a compliant amount on my LND node? 08:46 < Ulmo_Aptos> What does it mean by "Go 1.1 is the recommended version"? I already have Go version 1.9 which is way past 1.1. 08:48 -!- CapitanRetardo [bcc21911@gateway/web/freenode/ip.188.194.25.17] has joined #lnd 08:53 < Ulmo_Aptos> No one is here? 08:53 < baltakatei> @Ulmo_Aptos, do you mean "Go 1.10"? 08:53 < Ulmo_Aptos> yes 08:53 < Ulmo_Aptos> I think I figured it out: they are using an odd math in which 1.10>1.9. 08:53 < baltakatei> (I'm really new to lnd so take that as you will) 08:54 < baltakatei> I think that's how versioning works nowadays. They're not decimal numbers. 08:54 < Ulmo_Aptos> ok. 08:54 < baltakatei> Like Bitcoin Core version 0.16 really means "16th iteration of version 0" 08:54 < baltakatei> (something like that) 08:54 < Ulmo_Aptos> Thank you 08:54 < Ulmo_Aptos> So, how do I set my feerate_per_kw? 08:54 < baltakatei> I remember reading on https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md that Go 1.10 is recommended for compiling lnd. 08:54 < lndbot> semantic versioning is MAJOR.MINOR.BUGFIX (or similar) 08:55 < Ulmo_Aptos> Thank you tyzbit 08:55 < baltakatei> I can't find "feerate_per_kw" on http://api.lightning.community/ 08:55 < Ulmo_Aptos> it's not there 08:55 < Ulmo_Aptos> it's called fee_per_kw in LND 08:56 < Ulmo_Aptos> It's called feerate_per_kw in C-Lightning, and the error message is given in that way. 08:56 < lndbot> so Bitcoin Core 0.16.0 is 0 (technically not version 1, or the first milestone version of the software), the 16th minor update (updates that add/change functionality that do not make previous versions incompatible), and the first release before any bugfixes (that do not change functionality internally, just fix bugs or minor unintended functionality) 08:57 < lndbot> the more you know :stars: 08:57 < Ulmo_Aptos> Damn, tyzbit, I had forgotten that from when I used to compile Linux kernels. 08:57 < baltakatei> Ulmo, I'm not too sure how error transmission works on the Lightning Network protocol but perhaps there is a C-Lightning node somewhere on the payment route that is giving that error? 08:57 < lndbot> https://semver.org/ 08:58 < baltakatei> Ulmo, ah I see. You're saying the "fee_per"kw" is not "feerate_per_kw". 08:58 < Ulmo_Aptos> How does OpenChannel's sat_per_byte relate to ListChannel's fee_per_kw? 08:59 < Ulmo_Aptos> baltakatei, I think LND's fee_per_kw is the same thing as C-Lightning's feerate_per_kw 09:00 < baltakatei> In my terminal log I can see "fee_per_kw" as output from the listchannels and pendingchannels command. 09:03 < baltakatei> Ulmo, Isn't the `--sat_per_byte` option only relevant for the `SendCoins` and `SendMany` commands? 09:04 < baltakatei> And aren't those used to send BTC from the lnd wallet to an arbitrary bitcoin address on on the blockchain? (outside LIghtning Network) 09:05 < Ulmo_Aptos> hmm 09:05 < lndbot> sat_per_byte can be used on channel openings 09:05 < baltakatei> The fees involved in channels seem to be mostly in units of "milli satoshis" or "millionths of satoshis". 09:05 < Ulmo_Aptos> stupid me updated GO and now I can't even connect to the node any more :( 09:06 < baltakatei> tyzbit, ah. That makes sense, since they anchor the channel to the blockchain. 09:06 -!- CapitanRetardo [bcc21911@gateway/web/freenode/ip.188.194.25.17] has quit [Quit: Page closed] 09:06 < lndbot> it's still a segwit transaction, though, so I think they just convert the weight to bytes 09:06 < s7r> i am looking for some simple documentation for lnd ... any hints? 09:06 < baltakatei> s7r I can link you what I've been using. 09:06 < lndbot> http://lightning.network/docs/ 09:07 < s7r> baltakatei, Please do 09:07 < lndbot> if it's LND specifically, a lot of the code is self-documented in README.md's in the function dirs https://github.com/lightningnetwork/lnd/tree/master/channeldb 09:08 < lndbot> the tutorial is also very illuminating http://dev.lightning.community/tutorial/ 09:08 < Ulmo_Aptos> Ugh, I got the error "2018-03-17 09:07:05.644 [INF] PEER: unable to read message from 127.0.0.1:9735: unknown address type: 27" 09:08 < baltakatei> https://github.com/lightningnetwork/lnd/releases/tag/v0.4-beta was where I started. https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md for figuring out how to get `lnd` to work with `bitcoind`. http://api.lightning.community/ for understanding the different `lncli` commands. 09:10 < Ulmo_Aptos> ok, I tried with my other node, it connected, but now openchannel is hanging :( 09:10 < Ulmo_Aptos> ok! it responded: "[lncli] rpc error: code = Code(202) desc = feerate_per_kw 7500 above maximum 6305" 09:12 < baltakatei> I had to learn how to compile `bitcoind` myself since `lnd` requires a library(?) called "ZMQ" for communicating with `bitcoind`. I also had to modify my bitcoin.conf to include zmq settings ("--zmqpubrawblock", "--zmqpubrawtx"). 09:12 < baltakatei> Ulmo, do you know what "kw" stands for in "feerate_per_kw"? 09:17 < Ulmo_Aptos> Yes, it's in the source: in LND: "The required number of satoshis per kilo-weight that the requester will pay at all times, for both the funding transaction and commitment transaction.", and in C-Lightning: "feerate per kiloweight (satoshis) for the commitment transaction and HTLCS (at this stage, same for both sides)", and later: "BOLT #3: The fee for an HTLC-timeout transaction MUST BE calculated to match: 1. Multiply `feerate_p 09:17 <@mlz> kilo weight 09:17 < Ulmo_Aptos> (rounding down)., and "BOLT #3: The fee for an HTLC-success transaction MUST BE calculated to match: 1. Multiply `feerate_per_kw` by 703 and divide by 1000 (rounding down)." 09:18 < Ulmo_Aptos> mlz, thank you. Btw, I thought it meant kilowatt at first, since I have solar panels and a tesla powerwall, so it confused me :/ 09:18 < s7r> thanks for these - really helpful. 09:18 <@mlz> :D 09:19 < s7r> it looks very complex but lots of things will be automated and wrapped in a nice gui i hope 09:19 <@mlz> bitcoin started using kilo weight since segwit activation in August last year 09:19 < Ulmo_Aptos> Yes, I read that. 09:19 < Ulmo_Aptos> well, I kind of remembered "weight" and assumed "kiloweight" is 1,000 weight. 09:20 < Ulmo_Aptos> So, I think I found a descrepancy in the code according to the above things, so I'm going to track it down ... 09:20 < Ulmo_Aptos> BOLT#3 says 663/1000 AND 703/1000 09:20 < Ulmo_Aptos> ? 09:21 <@mlz> it's still beyond my understanding but i found this wiki helpful if anyone needs further info about kw: https://en.bitcoin.it/wiki/Weight_units 09:21 < Ulmo_Aptos> https://github.com/lightningnetwork/lightning-rfc/blob/master/03-transactions.md shows some discussion at "Fees: Fee calculation" that I'm reading now. 09:22 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has quit [Ping timeout: 240 seconds] 09:22 < Ulmo_Aptos> Commitment weight: 724 + 172 * num-untrimmed-htlc-outputs HTLC-timeout weight: 663 HTLC-success weight: 703 09:27 < baltakatei> Ah, there's a song in BOLT #1. :) 09:27 < baltakatei> I mean, BOLT #0 09:34 -!- t4sk [026cd586@gateway/web/freenode/ip.2.108.213.134] has quit [Quit: Page closed] 09:35 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has joined #lnd 09:42 < s7r> When making an update, both parties exchange the secrets for the prior state, so that all prior states will have been revoked except for the current state. Both parties will never broadcast an old state, because they know the other party can take all their money if they do so. 09:42 < s7r> how does this work exactly ? how is this transaction created? 09:43 <@mlz> rompert, it's still a pain to find my little channel on https://rompert.com/recksplorer/ :/ 09:52 -!- offerm [546f8b93@gateway/web/freenode/ip.84.111.139.147] has joined #lnd 09:53 < offerm> Hi Guys, Need your help. Trying to bring up btcd on mainnet. first sync takes forever. Looks like downloading headers takes very long time. Any ideas? 09:57 < baltakatei> offerm: I haven't used btcd before. The only ideas I would have are for bitcoind. 09:57 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Remote host closed the connection] 09:58 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #lnd 09:59 < offerm> does bitcoind has all the changes needed for LN? 10:00 < baltakatei> offerm, not the one available from bitcoincore.org. I had to compile my own bitcoind in order to get the ZMQ messaging system included in bitcoind (which lnd requires). 10:01 < Ulmo_Aptos> offerm, bitcoind is far faster. I also have a few ways to speed up btcd, but they're not worth it. Just use bitcoind, as baltakatei explained. 10:02 < baltakatei> I followed this guide for compiling bitcoind on my computer (Debian 9 GNU/Linux): https://github.com/bitcoin/bitcoin/blob/master/doc/build-unix.md 10:02 < Ulmo_Aptos> how do I fix "[lncli] rpc error: code = Code(216) desc = to_self_delay 1081 larger than 432" 10:04 < offerm> many thanks! 10:45 -!- rollinDyno [~rollinDyn@cpc130682-camd16-2-0-cust250.know.cable.virginm.net] has joined #lnd 11:06 -!- drrty2 [drrty@gateway/vpn/privateinternetaccess/drrty] has quit [Ping timeout: 268 seconds] 11:09 < s7r> can i use bitcoind instead of btcd? 11:09 < s7r> i already have it 11:09 -!- nortorC3R38D [~ffnizscw@114.7.19.5] has joined #lnd 11:10 -!- nortorC3R38D [~ffnizscw@114.7.19.5] has quit [Client Quit] 11:12 -!- t4sk [026cd586@gateway/web/freenode/ip.2.108.213.134] has joined #lnd 11:15 <@mlz> s7r, yes 11:16 <@mlz> just make sure it has ZMQ built in 11:19 < s7r> mlz: thank you 11:22 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving] 11:27 <@mlz> s7r, np, if your bitcoind is not run with -txindex, you have to restart it with -reindex -txindex, i guess you know all this stuff? 11:27 <@mlz> and the guide to install lnd is here: https://github.com/lightningnetwork/lnd/blob/master/docs/INSTALL.md#installing-lnd 11:36 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 11:38 -!- Linrono [6c1f9344@gateway/web/freenode/ip.108.31.147.68] has joined #lnd 11:43 -!- kunla [~kunla@81.193.53.189] has quit [Quit: WeeChat 2.0.1] 11:51 < s7r> mlz, yes, it is with txindex=1 from starters because i also host an electrumx server on this server 11:52 <@mlz> s7r, oh.. then you're good to go, just have to put in a proper bitcoin.conf for lnd 11:53 < s7r> yup. i have compiled from source so i guess zmq is enabled .. should be fine 11:55 <@mlz> i used to compile with no zmq, so for my first bitcoind node to run with lnd, i had to recompile it with this line: apt-get install libzmq3-dev 11:55 <@mlz> and it was done in just minutes 12:03 -!- Pioklo_ [~Pioklo@5.83.71.43] has joined #lnd 12:08 < arihan> can you use a hostname for --externalip=X.X.X.X? What if the nodes IP changes for a well connected node? just looking into setting it up as i run an electrum server anyway. 12:09 -!- deusexbeer [~deusexbee@093-092-176-212-dynamic-pool-adsl.wbt.ru] has quit [Ping timeout: 256 seconds] 12:10 -!- deusexbeer [~deusexbee@093-092-181-166-dynamic-pool-adsl.wbt.ru] has joined #lnd 12:25 < Linrono> hello there! i am trying to run lnd on mainnet now that i have it ~working~ on testnet, but when i change bitcoin.testnet to bitcoin.mainnet i seem to lose rpc access to my bitcoind node. can anyone help me with this? 12:26 < Linrono> i am using the .cookie file for auth and it works with testnet but not mainnet 12:28 <@mlz> Linrono, do you have a bitcoind node running on mainnet? 12:29 < Linrono> i sure do 12:29 <@mlz> look at your bitcoin.conf 12:31 < Linrono> ok 12:31 < Linrono> mlz, i do have testnet=0 12:32 <@mlz> Linrono, what's the current blockheight of your bitcoind, do: bitcoin-cli -getinfo 12:35 < Linrono> mlz, i have 513982 when running getblockchaininfo 12:35 < Linrono> same with -getinfo 12:36 <@mlz> Linrono, and you deleted the old .lnd testnet database? 12:37 < Linrono> mlz, no i did not do that, i didn't know i needed to 12:37 < Linrono> i assumed that it would have the info in two different folders, my mistake 12:38 < Linrono> well actually im still getting the same error 12:38 < Linrono> unable to load RPC credentials for bitcoind: unable to extract RPC credentials: unable to find rpcuser in config, cannot start w/o RPC connection 12:38 < Linrono> this is after deleting .lnd from my home directory 12:39 <@mlz> are both of your nodes in the default directories? 12:40 < Linrono> no they are not, i currently have my data dir for bitcoind on an external drive, i have a symbolic link to bitcoin.conf and .cookie in my ~/.bitcoin folder and a .cookie that also points to my testnet3 folder 12:41 <@mlz> Linrono, do you have bitcoin.mainnet=1 in your lnd.conf? 12:41 < Linrono> i had bitcoin.mainnet set in the commandline but not in the config 12:42 <@mlz> i'm wondering if the .cookie files confuse your lnd, idk 12:42 <@mlz> and if they're not in the default directories, i think you have to set up the same rpcuser and rpcpass for both nodes 12:42 < Linrono> i gotcha, its just weird how it works perfectly in testnet 12:43 <@mlz> right 12:44 < Linrono> im gonna look at the code again and try to find where it looks for the cookie files 12:45 < Linrono> ooo maybe i found it 12:46 < Linrono> in config.go it lists chaindir as a switch case 12:46 < Linrono> testnet3 and regtest 12:47 < Linrono> but my mainnet node uses the datadir to host the cookie file 12:47 < Linrono> thats why it can find the testnet cookie but not the mainnet cookie 12:47 < Linrono> maybe? lmao 12:48 -!- AndBobsYourUncle [~AndBobsYo@cpe-23-240-21-154.socal.res.rr.com] has quit [Quit: Textual IRC Client: www.textualapp.com] 12:50 < t4sk> did anyone make a web frontend to lnd yet? 12:50 < Linrono> oh no its set as the data dir before 13:01 -!- IllusiveMan [uid279126@gateway/web/irccloud.com/x-mtlrbgnfsnqstzrv] has quit [Quit: Connection closed for inactivity] 13:02 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wpdrmqdadihvyjtt] has joined #lnd 13:03 <@mlz> Linrono, did you change something in config.go? 13:03 < Linrono> mlz, i did just now to get it to print where it is looking for the cookie file 13:04 < Linrono> mlz, i hadnt before i asked about this 13:04 <@mlz> Linrono, i wouldn't, more likely you need to delete the .cookie files from bitcoind, delete eveything related to testnet, and restart your bitcoind 13:05 < Linrono> mlz, i gotcha, im just exploring now. i tried deleting the lnd folder and restarting bitcoind a couple of times. dont really know what to do 13:06 < Linrono> mlz, i already tried with the change to config.go and it prints the path its looking for fine 13:06 < Linrono> mlz, gonna try it with testnet and mainnet and see what i get 13:20 < Linrono> mlz, so my test verified that when i set bitcoin.mainnet in the commandline it is still looking for the cookie file in the testnet folder 13:21 < Linrono> mlz, you had mentioned setting bitcoin.mainnet in my lnd.conf? 13:23 < Linrono> even when i blow out the .lnd folder, it is still looking for testnet 13:27 < Linrono> mlz, so i figured it out 13:27 < Linrono> lnd looks at the bitcoin.conf file 13:28 < Linrono> to see if it is running testnet/regtest it only looks for the option in the bitcoin.conf file 13:28 < Linrono> it doesnt look at whether it is set to 1 or 0 13:28 < Linrono> i switch to and from testnet by setting that option to 1 and 0 respectively 13:29 < Linrono> since i had testnet=0, lnd thought i was running testnet and set everything to testnet 13:30 <@mlz> oh really... 13:30 <@mlz> i've never used 'testnet=0' i use comments 13:31 < Linrono> gotcha 13:31 < Linrono> yeah funny little quirk 13:31 <@mlz> yup 13:32 < Linrono> wait so if you comment the testnet line it works for you 13:32 < Linrono> ? 13:33 <@mlz> Linrono, at this point i think if you would just separate testnet from mainnet, like put them in two different users 13:33 <@mlz> it would be simpler 13:33 < Linrono> no i definitely need to figure something else out, was just wondering 13:33 < Linrono> thanks for your help 13:34 <@mlz> yw 13:38 -!- ajph [~ajph@unaffiliated/ajph] has quit [Ping timeout: 256 seconds] 13:41 -!- ChaoticMind [~ChaoticMi@2a03:8600:1001:1012::1005] has quit [Quit: Leaving] 13:56 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 13:57 -!- booyah [~bb@193.25.1.157] has joined #lnd 14:13 -!- naribia [adefec52@gateway/web/freenode/ip.173.239.236.82] has joined #lnd 14:21 -!- creslin [~textual@deposing-waterfront.volia.net] has joined #lnd 14:22 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 14:22 -!- booyah [~bb@193.25.1.157] has joined #lnd 14:34 < arihan> is high CPU usage normal with lots of unable to fetch UTXO already spent? 14:38 -github-lnd:#lnd- [lnd] Roasbeef pushed 1 new commit to master: https://git.io/vxOuh 14:38 -github-lnd:#lnd- lnd/master 47329c9 Andreas M. Antonopoulos: docs: inconsistent ZMQ port numbers in examples... 14:39 -github-lnd:#lnd- [lnd] Roasbeef closed pull request #867: Update INSTALL.md (master...patch-1) https://git.io/vxOTZ 14:40 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 14:40 -!- booyah [~bb@193.25.1.157] has joined #lnd 14:41 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 14:42 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 14:46 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 256 seconds] 14:47 -!- sneakerhax [~sneakers@unaffiliated/sneakerhead] has joined #lnd 14:48 <@roasbeef> BB-Martino: there's nothing wrong with those messages, perhaps we should demote down to warning for that, tehre are just hold hacky faulty nodes on the network that were around before actual releases were put out 14:49 <@roasbeef> skace: channels can be pending for a while depending on the csv value, are they pending force close? if they're in the nursery, then we'll show how many block remain until we can sweep them 14:49 -!- booyah [~bb@193.25.1.157] has quit [Ping timeout: 246 seconds] 14:50 <@roasbeef> baltakatei: fee insuf can be to older nodes on the network, it may tae a day or two for people to actually upgrade, and keep in mind this is still the very early days as most node operators have no idea what they're doing asthey never even went on testnet beforehand 14:51 <@roasbeef> Ulmo_Aptos: that's just doe to c-lightning not liking our fees, not much that can be done on our end, but imo nodes shoudl be more liberals as far as the fees they'll accept 14:51 <@roasbeef> Linrono: make sure you're trying to connect to a bitcoind node running mainnet 14:52 < Ulmo_Aptos> roasbeef, I did learn how to set fees on my c-lightning nodes to accept the channel creation. I also had to restart with higher to_self_delay maximum. 14:52 <@roasbeef> arihan: it accepts ip's :p, if it changes, then the node will send out a new authenticated update with the new info 14:52 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Remote host closed the connection] 14:52 <@roasbeef> yeh clightning only uses low values for csv atm it seems, or rather only accepts low values 14:53 -!- booyah [~bb@193.25.1.157] has joined #lnd 14:54 -!- Pioklo_ [~Pioklo@5.83.71.43] has quit [Ping timeout: 260 seconds] 14:56 < arihan> roasbeef, ok thanks :) Did you see my message about CPU usage / lots of errors about UTXO not found / already spent? 14:56 <@roasbeef> there seem to be older faulty nodes on the network 14:56 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Excess Flood] 14:56 <@roasbeef> my guess is ppl messed up hacking their nodes to add mainnet 14:57 <@roasbeef> and somehow start to accept like testnet channels or something 14:57 <@roasbeef> we should cache utxo set look up to alevaite that, and shorter term start to create banscores for nodes that try to send us bogus information 14:58 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #lnd 14:59 < arihan> Ah ok, as long as its not something ive messed up and needed to fix 14:59 <@roasbeef> yeh nah i've seen that on my nodes as well 14:59 <@roasbeef> polling some of the other implementatinons to see if they're seeing this as well, so we can track it down 15:01 < arihan> roasbeef, just looked up some of the channel id's that its moaning about and they are closed ones. 15:02 <@mlz> arihan, set your debuglevel to "info" you'll get less annoying messages 15:02 -!- spinza [~spin@196.212.164.26] has quit [Quit: Coyote finally caught up with me...] 15:02 < arihan> Not that bothered about the messages i was wondering about the CPU lol its using 150% so 1 1/2 cores on a quad core 15:03 <@mlz> yea the cat is running on steroids :P 15:04 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer] 15:04 -!- booyah [~bb@193.25.1.157] has joined #lnd 15:05 < Ulmo_Aptos> arihan, is there an example node or transaction id with that error? I can search my logs. 15:06 < Linrono> roasbeef, it ended up being my conf file had testnet=0 in it but lnd takes that as use testnet. commenting the line or removing it fixed my issues 15:07 < Ulmo_Aptos> I have bitcoin.testnet=0 and it seems to work for me though. 15:07 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 15:07 < Linrono> ulmo_aptos, it was in my bitcoin.conf file 15:07 < Ulmo_Aptos> oh 15:08 < Linrono> then config.go only checks for the existance of the option, not whether it is set to 1 or 0 15:10 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 15:12 < BB-Martino> roasbeef: 1) Regarding the problem of seeing chan_id: 0 in my lists, you said that it could be because of confirmations. But in that case shouldn't the channel show up in pendingchannels (and with chan_id still showing a valid number)? 2) Regarding that failed payment message ("unable to fetch chan point" / "tx_index=#14103040 is out of range"): shouldn't lnd route around this faulty node? Does me getting this message mean this node is the gatekeeper to 15:12 < BB-Martino> the node which generated the invoice? 15:13 <@roasbeef> if it's the only active channel to the node that generated the invoice, then you may not be able to pay the invoice 15:13 <@roasbeef> check that your node is getting new blocks in, and also that lnd see those new blocks 15:15 < BB-Martino> it must, since i was able to pay the invoice after i opened a direct channel to the node (the one for mainnet.yalls.org specifically) 15:16 < BB-Martino> but instead of the usual error message of 'cannot find path to...' it came up with that "unable to fetch chan point" one 15:17 < BB-Martino> (I mean before I opened a direct channel) 15:19 -!- Linrono [6c1f9344@gateway/web/freenode/ip.108.31.147.68] has quit [Ping timeout: 260 seconds] 15:22 < Ulmo_Aptos> How do I convert channel ID and channel point into channel numbers that c-lightning would understand? 15:23 < Ulmo_Aptos> nvm i got it 15:23 < Ulmo_Aptos> 1st 5 hex are block#, next 6 hex are seq# and last is output# 15:24 < Ulmo_Aptos> (last 4 hex). So, 6 hex = 24 bits. 24 bits block# 24 bits seq# and 16 bits output# 15:25 -!- spinza [~spin@196.212.164.26] has joined #lnd 15:29 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 15:42 -!- stiell [~stian@fsf/member/stiell] has joined #lnd 15:44 < Ulmo_Aptos> roasbeef: I'm also seeing the same utxo not found in c-lightning error logs for the same sample channel I found in a LND log entry of the similar error. 15:44 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 15:44 <@roasbeef> gotcha yeh there's some faulty node that keeps sending them out 15:45 <@roasbeef> we 15:45 <@roasbeef> we'll reject it though as expected 15:45 < Ulmo_Aptos> The sampled channel was created sometime on or before 2018-02-05T14:56:04.749Z and first error of no utxo was 2018-03-16T13:45:33.397Z lightning_gossipd(20199): channel_announcement: no unspent txout 507791:1507:1 15:46 < Ulmo_Aptos> wow ok so maybe I should save my 50 gigabytes of logs 15:48 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 15:51 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 15:52 -!- grubles [~grubles@unaffiliated/grubles] has joined #lnd 15:55 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 248 seconds] 15:56 -!- sovjet [~sovjet@user182.c2.sevnica.kabelnet.net] has quit [Quit: Leaving] 15:56 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #lnd 16:02 -!- spudowiar [~spudowiar@unaffiliated/saleemrashid] has quit [Quit: WeeChat 2.0.1] 16:08 <@roasbeef> DNS should now be u 16:08 <@roasbeef> p 16:14 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 16:18 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds] 16:23 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 16:27 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 248 seconds] 16:27 -github-lnd:#lnd- [lnd] xgess opened pull request #873: move defaultchanconfs setting in sample-lnd.conf to bitcoin section (master...sample-conf-defaultchannelconfs) https://git.io/vxOrM 16:28 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 256 seconds] 16:32 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 16:37 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 246 seconds] 16:39 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #lnd 16:40 -github-lnd:#lnd- [lnd] MDrollette opened pull request #874: don't zero encKey from mem if never unlocked (master...nil-check-enckey) https://git.io/vxOoO 16:41 -!- gethh [uid264798@gateway/web/irccloud.com/x-cfhernwqzchgbqmk] has joined #lnd 16:44 -!- t4sk [026cd586@gateway/web/freenode/ip.2.108.213.134] has quit [Quit: Page closed] 16:48 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 16:51 < lndbot> is the faucet donation address posted last week still cromulent? tb1qh2lm74j9ulnu9vkksh07pqdttd8kh6lnp5xjdl 16:52 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds] 16:55 -!- creslin [~textual@deposing-waterfront.volia.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 17:00 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 17:02 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has quit [Ping timeout: 260 seconds] 17:05 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 263 seconds] 17:07 -!- lndbot1 [~lndbot@138.197.213.35] has joined #lnd 17:08 -!- lndbot [~lndbot@138.197.213.35] has quit [Read error: Connection reset by peer] 17:09 <@mlz> my node is a gossip girl, check out the nodes info: https://paste.ee/p/ENHSR#D7JcTnlQGtCsC8Wk9E4RynHqTyupqovr 17:11 -!- rls [~rls@74.120.222.234] has quit [Read error: Connection reset by peer] 17:12 -!- rls [~rls@74.120.222.234] has joined #lnd 17:12 -!- rollinDyno [~rollinDyn@cpc130682-camd16-2-0-cust250.know.cable.virginm.net] has quit [Quit: leaving] 17:13 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 17:17 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 248 seconds] 17:18 -!- tumi [tumi@u.nix.is] has quit [Quit: leaving] 17:18 -!- tumi [tumi@u.nix.is] has joined #lnd 17:21 -!- Giszmo [~leo@ip-199-233.219.201.nextelmovil.cl] has joined #lnd 17:24 -!- rls [~rls@74.120.222.234] has quit [Read error: Connection reset by peer] 17:25 -!- rls [~rls@74.120.222.234] has joined #lnd 17:27 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 17:32 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 17:42 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 17:47 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 256 seconds] 17:49 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 17:53 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #lnd 17:54 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 17:54 -!- Ulmo_Aptos [1804e4d5@gateway/web/freenode/ip.24.4.228.213] has quit [Ping timeout: 260 seconds] 17:57 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Ping timeout: 240 seconds] 18:04 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 18:06 -!- Giszmo [~leo@ip-199-233.219.201.nextelmovil.cl] has quit [Quit: Leaving.] 18:08 -!- Giszmo [~leo@ip-199-233.219.201.nextelmovil.cl] has joined #lnd 18:09 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 256 seconds] 18:18 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 18:23 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 18:34 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 18:38 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 263 seconds] 19:00 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 19:00 -!- mavd0g [995c91b9@gateway/web/freenode/ip.153.92.145.185] has joined #lnd 19:05 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 19:12 -!- mavd0g [995c91b9@gateway/web/freenode/ip.153.92.145.185] has quit [Quit: Page closed] 19:15 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 19:20 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 260 seconds] 19:26 -!- hiamrandy [baa7f936@gateway/web/freenode/ip.186.167.249.54] has joined #lnd 19:27 -github-lnd:#lnd- [lnd] lra opened pull request #876: Support space characters surrounding = in bitcoind configuration files (master...fix_autodetect_bitcoind_config) https://git.io/vxO1u 19:30 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 19:31 -!- hiamrandy [baa7f936@gateway/web/freenode/ip.186.167.249.54] has quit [Client Quit] 19:34 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 256 seconds] 19:40 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 19:45 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 260 seconds] 19:51 -!- quitobro_ [~quitobro@pool-108-41-0-186.nycmny.fios.verizon.net] has joined #lnd 19:51 -!- gethh [uid264798@gateway/web/irccloud.com/x-cfhernwqzchgbqmk] has quit [Quit: Connection closed for inactivity] 19:51 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-wpdrmqdadihvyjtt] has quit [Quit: Connection closed for inactivity] 19:52 -!- quitobro [quitobro@gateway/vpn/privateinternetaccess/quitobro] has quit [Ping timeout: 264 seconds] 19:52 -!- quitobro_ is now known as quitobro 19:54 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 19:55 -github-lnd:#lnd- [lnd] MDrollette opened pull request #877: config: default naked ports to localhost (master...bind-host) https://git.io/vxOMc 19:56 < skace> roasbeef: the pending force were fine 19:56 < skace> the noraml pending gave no indeication on completion 19:58 <@mlz> skace, do you have any coin in limbo that's supposed to come back to your wallet? 19:58 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds] 19:59 < skace> i do 20:00 < skace> not a lot, but still 20:03 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 20:04 <@mlz> it should tell you how many blocks left 20:08 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 20:09 < skace> it did not 20:09 < skace> only the force pending showed that 20:13 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 20:17 -!- maurris [~maurris@unaffiliated/maurris] has quit [Ping timeout: 240 seconds] 20:18 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 265 seconds] 20:21 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 20:21 < baltakatei> Does anyone have a 0.4-beta node up that I can connect to with my own 0.4-beta node? I'd like to avoid these glitchy older nodes that roasbeef mentioned. 20:22 < baltakatei> Failing that, is there a way to have lnd retry different routes with the same pay_req until one succeeds? 20:26 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 20:27 <@mlz> baltakatei, sure 20:27 < baltakatei> :D 20:27 -!- camonz [~camonz@253.red-2-136-119.dynamicip.rima-tde.net] has quit [Ping timeout: 264 seconds] 20:32 -!- simlay [~simlay@gateway/tor-sasl/simlay] has quit [Quit: WeeChat 2.0.1] 20:34 -!- simlay [~simlay@gateway/tor-sasl/simlay] has joined #lnd 20:35 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 20:39 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds] 20:42 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 20:43 -!- DrOlmer [~DrOlmer@unaffiliated/drolmer] has joined #lnd 20:45 < DrOlmer> anyone else keeps getting the same error: "[ERR] DISC: Router rejected channel edge: unable to fetch utxo for chan_id=562021965727793153, chan_point=60b7be27053a50eff0a5f56bb567620f09ff5763777f0318fcb7545802772bfd:1: target output has been spent" ? 20:46 -!- Giszmo [~leo@ip-199-233.219.201.nextelmovil.cl] has quit [Ping timeout: 260 seconds] 20:47 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 260 seconds] 20:48 <@mlz> DrOlmer, just ignore them 20:49 <@mlz> DrOlmer, i have this in my lnd.conf: "debuglevel=info" and now i'm getting less annoying messages 20:50 < DrOlmer> ye I have `info` as well, but those have level=`error` so there's "pollution" on the logs 20:56 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 21:01 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 246 seconds] 21:05 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #lnd 21:09 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 21:14 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 21:15 -!- grafcaps [~haroldbr@50.90.83.229] has quit [Ping timeout: 260 seconds] 21:25 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 21:27 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #lnd 21:29 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 21:32 -!- IllusiveMan [uid279126@gateway/web/irccloud.com/x-tldsfnvioqlpitkx] has joined #lnd 21:34 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 21:38 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 260 seconds] 21:46 -!- nixbox [45b54207@gateway/web/freenode/ip.69.181.66.7] has joined #lnd 21:47 < nixbox> Yo 21:47 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 21:47 < nixbox> Awesome job on releasing lnd 0.4 beta! 21:47 < nixbox> I am trying to set it up 21:47 < nixbox> Specifically, I already have bitcoind running in a docker container 21:47 < nixbox> i setup another docker container with lnd 21:47 < nixbox> pointed lnd to my bitcoind 21:47 < nixbox> it can connect and receive block updates over ZMQ 21:48 < nixbox> however when lnd starts 21:48 < nixbox> it tries to connect to 192.168.1.1 (my router) and an ephemeral port 21:48 < stiell> I'm currently getting '[ERR] DISC: Unable to query bootstrapper BOLT-0010 DNS Seed: [[test.nodes.lightning.directory soa.nodes.lightning.directory]]: dns: domain must be fully qualified' on HEAD, although the related issues (#848, #854) have been closed saying DNS seeding was temporarily down. Are they down again? Using testnet over Tor. 21:48 < nixbox> and then fails 21:48 < nixbox> stiell: I am getting that error too :) 21:49 < nixbox> lnd connecting to my router is super-weird, I think its probably because my router is doing NAT and when an incoming peer wants to connect, the port that my router maps it to shows up as my router's IP address followed by the prot 21:49 < nixbox> don't know how to fix that 21:49 < nixbox> anybody else encountered that? 21:50 < baltakatei> nixbox I had that same problem. 21:50 < lndbot1> nixbox: that's a weird one, I guess make sure you specify _all_ of the necessary bitcoind options 21:50 < nixbox> tyzbit, 2018-03-18 04:50:11.120 [DBG] CMGR: Failed to connect to 028bbe4e7a85ccff3987deee238fd69732a8e9e621d7e594398062d8bec2a3c571@192.168.1.1:48798 (reqid 1): dial tcp 192.168.1.1:48798: connect: connection refused 21:51 < baltakatei> I had to manually connect to a node using one of the mainnet LN explorers. You can connect to my node, though. 21:51 < lndbot1> is that a node connecting to you, or an outbound connection? 21:51 < nixbox> [Bitcoin] bitcoin.active=1 bitcoin.mainnet=1 bitcoin.node=bitcoind bitcoind.rpchost=x.x.x.x 21:51 < nixbox> tyzbit, I think that node is connecting to me 21:51 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 21:52 < lndbot1> does the pubkey match `lnd getinfo`? 21:52 < lndbot1> sorry, lncli getinfo 21:54 < nixbox> tyzbit, https://pastebin.com/y3ye4h16 21:55 < nixbox> tyzbit, thats "lncli getinfo" output 21:55 < lndbot1> yeah, somehow you're trying to connect to yourself. if not, I guess the DNS seed isn't working right with your unique config, what baltakatei said should fix you right up. Just connect to anyone on a mainnet explorer, but I'd be particular about which nodes you open channels to. Try to make sure you pick nodes that have been upgraded. 21:55 < lndbot1> disregard the DNS seed part 21:55 < baltakatei> I made the mistake of connecting to some glitchy nodes initially. 21:56 < nixbox> by manually you guys means using lncli manually? 21:56 < nixbox> s/means/mean 21:57 < baltakatei> Yeah. 21:57 < mdrollette> nixbox: lncli connect 031feee8045899c658eec2b6f2f6da6e4bdd7baabdc61bdc017761577342fbd011@76.184.81.28:9735 21:57 < baltakatei> `lncli openchannel --node_key=03e7...f66e --local_amt=100000` Something like that. 21:57 < lndbot1> well, you gotta connect first but yeah 21:58 < baltakatei> Oh yeah. Connect like how mdrollette shows. 21:58 < baltakatei> Then openchannel 21:58 < nixbox> done, connected, listpeers shows an entry 21:59 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 22:00 < nixbox> which lightining mainnet explorer should i use to check that my lnd node is working/connected? 22:00 < baltakatei> I'm using https://graph.lndexplorer.com/ 22:01 -!- rls [~rls@74.120.222.234] has quit [Read error: Connection reset by peer] 22:01 -!- rls [~rls@74.120.222.234] has joined #lnd 22:02 < lndbot1> the explorers are almost misleading enough to be not useful 22:02 < lndbot1> you know your node is working if you do `lncli describegraph` and you get a bunch of nodes and edges 22:03 < nixbox> woah, a bunch :) 22:03 < lndbot1> you are g2g my dude 22:03 < lndbot1> those "explorers" are really just "visualizers" for the data from whoever runs them's node. No one's graph looks the same. Some people won't see you on their graph, but that doesn't mean either of you are doing anything wrong. 22:04 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 260 seconds] 22:04 < nixbox> tyzbit, thanks a bunch 22:05 < lndbot1> glad to help, make sure to rep the #craefulgang and be safe 22:09 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 265 seconds] 22:13 <@roasbeef> hmm, are peeps able to hit 'dig test.node.lightning.directory SRV'? 22:14 <@roasbeef> dns seems to be working fine on my nodes when i hit the endpoints, there're been some issues with the resolvers of users' at times truncating our response, so we added a TCP fallback 22:14 < lndbot1> not sure if it's just me but ;; connection timed out; no servers could be reached 22:14 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 22:15 <@roasbeef> nixbox: if you manually try to hit that query above, what do you get? 22:15 <@roasbeef> what about just nodes.lightning.directory? 22:15 < lndbot1> instantly answered 22:16 <@roasbeef> with a response? 22:16 <@roasbeef> A or SRV? 22:17 < lndbot1> yeah lots of addrs, A records only 22:17 <@roasbeef> but you can't hit the SRV? 22:17 <@roasbeef> of either variant? 22:17 < lndbot1> okay, nodes.lightning.directory I get back SRVs 22:18 < lndbot1> if I request SRVs 22:18 <@roasbeef> what if you add +trace? 22:18 <@roasbeef> hmm, yeh seems to be ok on my end as well 22:18 < lndbot1> regular dig works for nodes.lightning.directory, dig SRV doesn't work for test.node.... 22:18 <@roasbeef> even just tried from 4 diff instance 22:18 < nixbox> roasbeef: https://pastebin.com/UYmppZQz 22:19 <@roasbeef> they're the same server even 22:19 < lndbot1> trace times out 22:19 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 264 seconds] 22:19 <@roasbeef> so try `dig +trace nodes.lightning.directory SRV` 22:19 <@roasbeef> as well as the test. 22:19 < lndbot1> on my home network, though on a VPS I got a response 22:20 < lndbot1> `dig +trace nodes.lightning.directory SRV` : home :: times out. VPS :: get a response 22:20 <@roasbeef> hmm yeh i think some resolvers still filter due to just the size 22:21 <@roasbeef> what about this `dig @104.131.26.124 +tcp nodes.lightning.directory SRV`? 22:21 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has joined #lnd 22:21 < lndbot1> get a response 22:22 < lndbot1> SRV records and everything 22:22 <@roasbeef> yeh see so the code does that itself 22:22 <@roasbeef> it tries udp, and then falls back to tcp resolution if needed 22:23 <@roasbeef> and when over tor it needs to manually attempt to do the srv as there's no socks version for fetching, for the regular query, we can tunnel that thru as normal, but need to do it manually for tor and the initial query 22:23 < baltakatei> roasbeef: https://pastebin.com/B0LJ1QX5 22:23 <@roasbeef> been meaning to throw up an issue to add additional bootstrap mechanisms 22:23 <@roasbeef> dns is only really need just to mkae initial connectivity 22:24 < lndbot1> idk about all the possible configs but I'm sure there are some home internet providers that do DNS filtering especially of "nonstandard" record types 22:24 <@roasbeef> that too 22:24 < lndbot1> my root dns is Google, I tried OpenDNS too but it didn't like the simple SRV request either 22:25 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 22:25 < nixbox> roasbeef: you mentioned test.node.lightning.directory, what successfully works for me is test.nodes.lightning.directory 22:26 <@roasbeef> oh yeh it's nodes 22:26 <@roasbeef> was a typo 22:26 < lndbot1> you could whip up a one-liner and ask people to submit their results somewhere that does a few digs and spits out DNS settings 22:27 < lndbot1> but the easier thing would probably be to, worst-case scenario, fall back to a DNS server you know works and hope that doesn't get filtered 22:28 < lndbot1> oh. I didn't realize it was node_s_. that works first try on mine lol 22:29 <@roasbeef> kek 22:30 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 265 seconds] 22:30 < nixbox> haha, thats why i pointed that out :D 22:31 < lndbot1> +1 to observation 22:41 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 22:44 <@mlz> dig @104.131.26.124 +tcp nodes.lightning.directory SRV -> http://paste.ubuntu.com/p/R9rWYgDKbV/ 22:45 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds] 22:45 -!- fusion44 [~fusion44@p2E59F8DB.dip0.t-ipconnect.de] has joined #lnd 22:49 -!- lnostdal [~lnostdal@gateway/tor-sasl/lnostdal] has quit [Ping timeout: 268 seconds] 22:50 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 23:18 -!- quitobro [~quitobro@pool-108-41-0-186.nycmny.fios.verizon.net] has quit [Quit: quitobro] 23:22 < stiell> What does it mean when I have an "active" channel in listchannels with chan_id 0 but getchaninfo 0 gives "edge not found"? 23:25 -!- rls [~rls@74.120.222.234] has quit [Remote host closed the connection] 23:29 -!- douglas__ [~douglas@c-73-234-93-65.hsd1.nh.comcast.net] has quit [Ping timeout: 260 seconds] 23:30 <@mlz> stiell, sounds like you're on an older version 23:31 <@mlz> and the channel doesn't exist anymore 23:34 < stiell> mlz: I'm using 0.4.0-beta on testnet. The peer is htlc.me, not sure what they are using. The channel was recently made (using openchannel) and its funding tx has 2 confirms. 23:34 -!- offerm [546f8b93@gateway/web/freenode/ip.84.111.139.147] has quit [Ping timeout: 260 seconds] 23:38 <@mlz> stiell, and you have chan_id 0 ? 23:39 < stiell> mlz: yes 23:40 <@mlz> stiell, did you get chan_id 0 when you connected to htlc.me? 23:44 < stiell> mlz: I connected before I opened the channel. listchannel has always showed chan_id 0 for the channel. 23:44 <@mlz> that has been changed for some time now 23:46 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 23:46 <@mlz> actually i don't recall listchannels ever showed chan_id=0, it was 'lncli connect...' 23:46 <@mlz> i have a channel with the lnd faucet and here's what i have: "chan_id": "1416578895405252608", 23:47 <@mlz> in listchannels 23:47 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 23:49 < stiell> describegraph shows no edges and 4 nodes. The htlc.me peer is not shown in describegraph, whatever that means. 23:52 < nixbox> stiell: i have the same issue with 0.4-beta on mainnet, "edge not found" 23:52 < nixbox> loving the rodeo though :D 23:53 < nixbox> just requested to open a channel with mainnet.yalls.org