--- Day changed Sun Apr 22 2018 00:03 -!- lnostdal [~lnostdal@85-118-77-0.mtel.net] has joined #lnd 00:13 -!- lnostdal [~lnostdal@85-118-77-0.mtel.net] has quit [Ping timeout: 248 seconds] 00:19 -!- lnostdal [~lnostdal@85-118-77-0.mtel.net] has joined #lnd 00:20 -!- Soopaman [~soopaman@cpe-70-122-225-218.tx.res.rr.com] has joined #lnd 00:25 -!- lnostdal [~lnostdal@85-118-77-0.mtel.net] has quit [Ping timeout: 265 seconds] 00:27 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 00:32 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 00:37 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 276 seconds] 00:39 -!- Fr4nZ82 [571b9d6e@gateway/web/freenode/ip.87.27.157.110] has joined #lnd 01:36 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 01:37 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 01:53 -!- Pioklo_ [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 01:57 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 265 seconds] 02:03 -!- dionysus69 [~Thunderbi@unaffiliated/dionysus69] has joined #lnd 02:15 -!- lnostdal [~lnostdal@85.118.80.236] has joined #lnd 02:16 -!- marijnfs_ [~smuxi@2a01:c23:b81a:1c00:15b:4f4f:dd87:198] has quit [Ping timeout: 256 seconds] 02:18 -!- wxss [~user@95.143.192.23] has joined #lnd 02:20 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has quit [Remote host closed the connection] 02:20 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has joined #lnd 02:38 -!- fusion44 [~fusion44@31.6.44.47] has quit [Quit: Leaving.] 02:49 -!- lnostdal [~lnostdal@85.118.80.236] has quit [Ping timeout: 240 seconds] 03:02 -!- lnostdal [~lnostdal@94-236-250-217.ip.btc-net.bg] has joined #lnd 03:07 -!- dionysus69 [~Thunderbi@unaffiliated/dionysus69] has quit [Ping timeout: 248 seconds] 03:33 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 03:35 -!- lnostdal [~lnostdal@94-236-250-217.ip.btc-net.bg] has quit [Read error: Connection reset by peer] 03:43 -!- Soopaman [~soopaman@cpe-70-122-225-218.tx.res.rr.com] has quit [Quit: Leaving.] 03:46 -!- Pioklo_ [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 268 seconds] 03:56 -!- tiagotrs [~user@p5DC4604A.dip0.t-ipconnect.de] has joined #lnd 03:56 -!- tiagotrs [~user@p5DC4604A.dip0.t-ipconnect.de] has quit [Changing host] 03:56 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 04:31 -!- Giszmo [~leo@ip-181-237-219-201.nextelmovil.cl] has quit [Ping timeout: 256 seconds] 04:32 -!- Fr4nZ82 [571b9d6e@gateway/web/freenode/ip.87.27.157.110] has quit [Ping timeout: 260 seconds] 04:48 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has quit [Remote host closed the connection] 04:48 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Remote host closed the connection] 04:49 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd 04:50 -!- intcat [~zshlyk@gateway/tor-sasl/intcat] has joined #lnd 04:51 -!- Giszmo [~leo@pc-37-38-86-200.cm.vtr.net] has joined #lnd 05:01 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #lnd 05:04 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 05:42 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #lnd 05:57 -!- dionysus69 [~Thunderbi@unaffiliated/dionysus69] has joined #lnd 05:59 < mlz> guys.. it's a nice Sunday, play with Lightning on this site: https://www.coinpanic.com/Lightning/CommunityJar 06:00 < mlz> and test your LND node to see if you can buy some fresh dirt or a cup of coffee here: https://main2-btc-ltc.forkbitpay.ninja/apps/Hoddr1KdzJcBf9MbhfXHziL1nnrtw7uMFWkZqL9Uhuyj/pos 06:07 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 268 seconds] 06:08 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 06:22 -!- cmdrtee [~mrtee@p200300C503D0D900F940D06EC145764B.dip0.t-ipconnect.de] has quit [Read error: Connection reset by peer] 06:22 -!- cmdrtee [~mrtee@p200300C503D0D900A8F232EC9F2D90E7.dip0.t-ipconnect.de] has joined #lnd 06:30 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Remote host closed the connection] 06:30 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has joined #lnd 06:43 -!- PatBoy [xyz@192.99.249.194] has joined #lnd 06:43 < PatBoy> hi, i got this error when i try to open a channel 06:43 < PatBoy> You gave bad parameters:feerate_per_kw 250 below minimum 253 06:44 < PatBoy> i try to raise fee with : sat_per_byte but that dont seem to work.. someone have an idea ? 06:44 -!- dionysus69 [~Thunderbi@unaffiliated/dionysus69] has quit [Ping timeout: 256 seconds] 06:48 < mlz> PatBoy, you trying to open a channel with a c-lightning node? 06:49 < PatBoy> eumm dont know i take a channel ramdom 06:49 < PatBoy> a node* 06:50 < mlz> i wouldn't open a channel with a random node but i think this is a c-lightning node that disagrees with fees from lnd nodes 06:51 < mlz> PatBoy, open a channel with this site and get some free coins: https://www.coinpanic.com/Lightning/CommunityJar 06:53 < PatBoy> ooo seem to work 06:53 < PatBoy> thx 06:54 < PatBoy> "num_pending_channels": 1, ... need to wait now :) 06:54 < PatBoy> thx 07:00 < mlz> PatBoy, np and right now you can send onchain txs with just 1 sat/byte :D 07:00 < PatBoy> yesterday i try the eclair implementation 07:01 < mlz> you're running LND right now, correct? 07:01 < PatBoy> i was not able to send a transaction when they where more than 1 hoop 07:01 < PatBoy> yess now i try the lnd :P 07:01 < mlz> i haven't tried eclair on mainnet yet 07:01 < mlz> but yea i've seen people have issues with eclair 07:01 < PatBoy> okk good thx 07:02 < PatBoy> if im not the only one at least it's not my ffault hahah 07:02 < mlz> lol 07:21 < PatBoy> nice thx i just order something on hodl :) 07:21 < PatBoy> nice thx i just order something on hodlmonkey hahha :P 07:26 -!- Fr4nZ82 [571b9d6e@gateway/web/freenode/ip.87.27.157.110] has joined #lnd 07:30 < Fr4nZ82> rpc lncli openchannel --node_key 0397b318c5e0d09b16e6229ec50744c8a7a8452b2d7c6d9855c826ff14b8fa8b27 --connect 193.107.204.158:9735 --local_amt 20271 error: code = Code(189) desc = You gave bad parameters:Our channel reserve 546 would be below their dust 573 on openchannel, what does it mean? what is dust? what is the wrong parameters? 07:35 -!- marijnfs_ [~smuxi@2a01:c23:b81a:1c00:15b:4f4f:dd87:198] has joined #lnd 07:39 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 07:42 -!- dionysus69 [~Thunderbi@unaffiliated/dionysus69] has joined #lnd 07:52 < mlz> hm that's SPICEFLOW, this node opened a channel to my lnd node and it was ok for them but not for an lnd node to open a channel to it? 07:52 < mlz> Fr4nZ82, also, the way you open a channel is not correct 07:56 < Fr4nZ82> i see this error often on other attempt, but not all attempt... What is the correct way mlz? 07:59 -!- jchia_1 [~jchia@45.32.62.73] has joined #lnd 07:59 -!- drrty2 [drrty@gateway/vpn/privateinternetaccess/drrty] has quit [Ping timeout: 240 seconds] 08:01 < mlz> lncli openchannel --node_key=xx --local_amt=xx --sat_per_byte=x (basic formula_ 08:02 < mlz> ah wait 08:02 < mlz> i guess your line is correct, LND added '--connect' which i didn't know 08:03 < mlz> and i've never used it 08:03 < mlz> in your case i would do: lncli openchannel 0397b318c5e0d09b16e6229ec50744c8a7a8452b2d7c6d9855c826ff14b8fa8b27 20271 --sat_per_byte=1 08:04 < Fr4nZ82> ok, i use connect in the lncli openchannel, but is the same to connect before and then open the channel 08:05 < mlz> i guess so 08:06 -!- jchia_1 [~jchia@45.32.62.73] has quit [Remote host closed the connection] 08:06 -!- jchia_1 [~jchia@116.192.20.171] has joined #lnd 08:09 < lndbot> yep, using --connect just makes it one command rather than two 08:09 < mlz> Fr4nZ82, why don't you open a channel with coinpanic, you can get some free coin too: https://www.coinpanic.com/Lightning/CommunityJar 08:09 < mlz> tyzbit i'm so you used to do connecting first :D 08:09 < mlz> -you 08:10 < lndbot> yeah, it's hard not to since if you're connected the openchannel just needs the pubkey 08:10 < mlz> i would search for the whole uri of a node first 08:10 < mlz> then 'lncli connect ' 08:11 < Fr4nZ82> i'm already connected to coinpanic 08:15 < lndbot> I think it'd be nice if the openchannel could parse a URI 08:15 < lndbot> but that's just being needy at this point 08:15 < lndbot> I'd much prefer AMP first 08:16 -!- Fr4nZ82 [571b9d6e@gateway/web/freenode/ip.87.27.157.110] has quit [Ping timeout: 260 seconds] 08:18 < RusAlex> hi mates. I've successfully started lnd software 08:19 < RusAlex> Now I need to connect to any lnd node ? 08:20 < RusAlex> I would like to buy something. I saw the site where bitcoin podcasts were selling for 0.01 USD with lightning payments 08:20 -!- Fr4nZ82 [571b9d6e@gateway/web/freenode/ip.87.27.157.110] has joined #lnd 08:21 < Fr4nZ82> sry, cant find it... do tou have irc chat log link? 08:23 < Fr4nZ82> i think i can not open channels because my wallet is near empty 08:24 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 264 seconds] 08:25 < mlz> ping djseeds 08:25 < mlz> he owns that site, not sure if he has it on mainnet 08:25 < mlz> RusAlex, or are you talking about testnet? 08:28 < RusAlex> no Im about mainnet =) 08:28 < RusAlex> do not need testnet anymore. 0.15mln usd in mainnet 08:28 < RusAlex> want to be a part of it ) 08:32 -!- fusion44 [~fusion44@p5483AD3E.dip0.t-ipconnect.de] has joined #lnd 08:34 -!- Pioklo_ [~Pioklo@118-40.echostar.pl] has joined #lnd 08:37 -!- tiagotrs [~user@p5DC4604A.dip0.t-ipconnect.de] has joined #lnd 08:37 -!- tiagotrs [~user@p5DC4604A.dip0.t-ipconnect.de] has quit [Changing host] 08:37 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 08:37 < RusAlex> lnd produces lots of output channel announces / discoveres 08:37 < lndbot> Hey RusAlex, lncast is still only on testnet, I’ve been pretty busy. Hopefully should be on mainnet ~1 month from now 08:37 < RusAlex> do I have to wait it finish ? 08:38 < RusAlex> lndbot: thank you for the update 08:38 < RusAlex> very appreciated your work 08:39 < RusAlex> I got error: unknown service lnrpc.WalletUnlocker lncli 0.4.1 commit=b0709b45f7af9314481d06e617b1cee088fd708e 08:42 < RusAlex> ok got it. I run lnd with --noencrypt flag 08:45 -!- fusion44 [~fusion44@p5483AD3E.dip0.t-ipconnect.de] has quit [Ping timeout: 248 seconds] 08:46 -!- fusion44 [~fusion44@31.6.22.233] has joined #lnd 08:51 -!- zyp_ [zyp@zyp.no] has joined #lnd 08:54 -!- stevenroose_ [~steven@vps.weuste.club] has joined #lnd 08:54 -!- bobazXY [~bobazY@200.ip-51-254-204.eu] has joined #lnd 08:55 < mlz> RusAlex, don't run lnd with --noencrypt 08:57 < RusAlex> why ? 08:59 < RusAlex> I wont hold there alot 08:59 < RusAlex> super I funded my lnd wallet. now I ready to create a payment channel 09:01 -!- dionysus69 [~Thunderbi@unaffiliated/dionysus69] has quit [Ping timeout: 268 seconds] 09:01 -!- spinza [~spin@196.212.164.26] has quit [Ping timeout: 240 seconds] 09:05 -!- nkuttler [~nkuttler@unaffiliated/nkuttler] has quit [Quit: leaving] 09:06 -!- max___ [~max@ip-86-49-245-49.net.upcbroadband.cz] has joined #lnd 09:06 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 260 seconds] 09:07 -!- max___ [~max@ip-86-49-245-49.net.upcbroadband.cz] has quit [Client Quit] 09:11 -!- fusion44 [~fusion44@31.6.22.233] has quit [Ping timeout: 256 seconds] 09:12 -!- spinza [~spin@196.212.164.26] has joined #lnd 09:24 -!- RusAlex [~Chel@unaffiliated/rusalex] has quit [Ping timeout: 248 seconds] 09:25 -!- kkt2[m] [kkt2matrix@gateway/shell/matrix.org/x-vlngxakiydyfmmub] has joined #lnd 09:25 -!- midnightmagic [~midnightm@unaffiliated/midnightmagic] has joined #lnd 09:25 -!- CodeShark [sid126576@gateway/web/irccloud.com/x-iuklvpzqbjusssdy] has joined #lnd 09:28 -!- pierce [x43matrixo@gateway/shell/matrix.org/x-zrxcjprabnruprdk] has quit [Ping timeout: 240 seconds] 09:29 -!- cjd[m] [cdelisle1@gateway/shell/matrix.org/x-mzoekrdjyodfksqn] has quit [Ping timeout: 245 seconds] 09:29 -!- fusion44 [~fusion44@p5483AD3E.dip0.t-ipconnect.de] has joined #lnd 09:29 -!- kkt2[m] [kkt2matrix@gateway/shell/matrix.org/x-vlngxakiydyfmmub] has quit [Ping timeout: 256 seconds] 09:29 -!- afdudley [afdudleyma@gateway/shell/matrix.org/x-chppvqalxwkyryba] has quit [Ping timeout: 260 seconds] 09:29 -!- rrol[m] [rrolmatrix@gateway/shell/matrix.org/x-fxgpjthsrxoqgzft] has quit [Ping timeout: 260 seconds] 09:29 -!- georgeangel[m] [georgeange@gateway/shell/matrix.org/x-uumqcmqdftnhrcmz] has quit [Ping timeout: 276 seconds] 09:29 -!- shem[m] [shemmatrix@gateway/shell/matrix.org/x-bwdbuokldbgytadv] has quit [Ping timeout: 256 seconds] 09:29 -!- interfect[m] [interfectm@gateway/shell/matrix.org/x-amfaeyishngmudxn] has quit [Ping timeout: 276 seconds] 09:37 -!- tiagotrs [~user@p5DC4604A.dip0.t-ipconnect.de] has joined #lnd 09:37 -!- tiagotrs [~user@p5DC4604A.dip0.t-ipconnect.de] has quit [Changing host] 09:37 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #lnd 09:39 -!- cmdrt33 [~mrtee@p200300C503D0D900A8F232EC9F2D90E7.dip0.t-ipconnect.de] has joined #lnd 09:40 -!- RusAlex [~Chel@unaffiliated/rusalex] has joined #lnd 09:42 -!- cmdrtee [~mrtee@p200300C503D0D900A8F232EC9F2D90E7.dip0.t-ipconnect.de] has quit [Ping timeout: 256 seconds] 09:56 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has joined #lnd 09:56 -!- zyp_ is now known as zyp 10:04 -!- Soopaman [~soopaman@cpe-70-122-225-218.tx.res.rr.com] has joined #lnd 10:08 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #lnd 10:10 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Read error: Connection reset by peer] 10:10 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 10:32 -!- Soopaman [~soopaman@cpe-70-122-225-218.tx.res.rr.com] has quit [Quit: Leaving.] 10:34 -!- galileopy [~galileopy@unaffiliated/galileopy] has joined #lnd 10:35 < larafale> hello folks, hope one of u can help me. I have lnd running, created a wallet, but now when I'm trying to generate a new address with "lncli --no-macaroons newaddress np2wkh" the command never resolve. any idea ? 10:36 < mlz> don't run with --no-macaroons 10:36 < larafale> I running lnd v0.4.1-beta from a fresh ubuntu, configured to a distant bitcoind server 10:38 -!- yoo [68fe5fd4@gateway/web/freenode/ip.104.254.95.212] has joined #lnd 10:38 < yoo> hey 10:38 < yoo> question for someone...? 10:38 < larafale> @mlz also, do you know why running "lncli --no-macaroons getnetworkinfo" return "[lncli] rpc error: code = Unknown desc = no graph edges exist" ? 10:41 < mlz> larafale, no idea, is your node on the network? 10:41 < mlz> does it have at least one channel? 10:41 < mlz> yoo, hi, please don't ask to ask, just ask your real question 10:41 < larafale> no, & no peers yet, don't know if this is normal from a fresh install 10:42 < mlz> larafale, right, nobody knows your node and it doesn't know other nodes so it's normal 10:42 < larafale> do you know a peer i can connect to ? 10:43 < RusAlex> larafale: 10:43 < mlz> larafale, 031b6ba6271514bd30202ba007a1d2ef2e2106aaa5774183c570137251687407dc@94.176.237.167:9735 10:43 < RusAlex> first time you start lnd it synch some data 10:43 < RusAlex> until it's finished I was not able to generate new address 10:43 < RusAlex> so just wait alittle 10:45 < larafale> @RusAlex do you know what data it is fetching ? because i specified a distant bitcoind testnet instance that is fully synced already. so i dont get why it is syncing 10:46 < RusAlex> just channels information I think. do not know. 10:46 < RusAlex> it's not too long 10:46 < mlz> larafale, oh are you on testnet? 10:46 < larafale> yes 10:46 < RusAlex> ah.. sorry Im on mainnet 10:46 < mlz> ok don't connect to that URI i posted 10:48 < mlz> larafale, connect to the testnet faucet: https://faucet.lightning.community/ 10:48 < larafale> from what I've understand from lnd with bitcoind as a backend, is that it would not have to sync anything because my node was already synced (versur running the default setting with btcd and syncing from scratch 10:49 < yoo> i'm trying to set up a lightning node to run on mainnet. and have lnd running, and have installed btcd 10:50 < yoo> but now as i'm about to start btcd by running this code: btcd --testnet --txindex --rpcuser=REPLACEME --rpcpass=REPLACEME 10:50 < yoo> i dont understand what i'm supposed to put in the place of REPLACEME. should i be making up a user name and password? 10:51 < larafale> @mlz so first, because I only want to test things, and i'm on testnet, i've added no-macaroons settings. should i use it ? 10:52 < larafale> @yoo yes 10:52 < mlz> larafale, no-macaroons will make you lose coins, so even on testnet try to figure this out if macaroons give you trouble and make a habit of not running with --no-macaroons 10:53 < larafale> @mlz ok thx for the tip I will 10:53 < mlz> cool :thumbsup: 10:54 < yoo> okay. and this will just be my password for accessing some kind of personalized data for btcd? 10:55 < larafale> @yoo you will use those credential specifying them when you will run the lnd deamon 10:55 < larafale> @yoo lnd will then be able to communicate via rpc to your btcd instance 10:56 < yoo> ohhh okay makes sense. thank you 10:56 < larafale> your btcd node is a full node 11:00 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 11:04 -!- SopaXorzTaker [~SopaXorzT@unaffiliated/sopaxorztaker] has quit [Remote host closed the connection] 11:08 -!- fusion44 [~fusion44@p5483AD3E.dip0.t-ipconnect.de] has quit [Ping timeout: 248 seconds] 11:08 -!- fusion44 [~fusion44@31.6.20.30] has joined #lnd 11:24 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has quit [Remote host closed the connection] 11:26 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 268 seconds] 11:26 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Ping timeout: 268 seconds] 11:28 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has quit [Quit: Leaving] 11:29 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has joined #lnd 11:30 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has quit [Client Quit] 11:31 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has joined #lnd 11:31 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has quit [Client Quit] 11:31 -!- fusion44 [~fusion44@31.6.20.30] has quit [Quit: Leaving.] 11:31 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has joined #lnd 11:33 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd 11:33 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 11:33 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has quit [Client Quit] 11:34 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 11:34 -!- ken2812221 [~User@133-203.dorm.ncu.edu.tw] has joined #lnd 11:35 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has quit [Excess Flood] 11:36 < yoo> anyone have any ddns (dynamic dns) apps they would recommend to allow for a reliable static ip. (nervous about privacy with some of these apps) 11:36 -!- rafalcpp [~racalcppp@84-10-11-234.static.chello.pl] has joined #lnd 11:36 < mlz> hm maybe tyzbit knows 11:37 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 11:38 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Client Quit] 11:38 < lndbot> well dynamic DNS means a non static ip 11:38 < lndbot> I like ddns.net for dynamic dns 11:39 < lndbot> If you want a static IP, use a VPN maybe? Spin up a tiny DigitalOcean box? 11:40 < lndbot> I was gonna do that but tbh it's too much work, my IP gets leaked everywhere else anyway 11:41 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 11:43 < lndbot> You only need to advertise to receive payments anyway 11:43 < yoo> okay i liked ddns.net in the past. i shouldn't be worried about malware or selling of traffic data i take it? they see to be the most popular so hoping i don't have to worry 11:44 < lndbot> Well some thoughtfulness is appropriate, but the traffic is all encrypted so the main concern in my eyes is advertising your amt of funds, but you can just open private channels. 11:45 < lndbot> And again, if you don't advertise an IP you will show up in graphs but people will only see your IP when you connect 11:45 -!- wxss [~user@95.143.192.23] has quit [Quit: leaving] 11:46 < yoo> okay thats sounds like a good plan (y) 11:51 -!- fusion44 [~fusion44@p5483AD3E.dip0.t-ipconnect.de] has joined #lnd 11:57 -!- fusion44 [~fusion44@p5483AD3E.dip0.t-ipconnect.de] has quit [Ping timeout: 276 seconds] 11:58 -!- fusion44 [~fusion44@128.90.23.242] has joined #lnd 11:59 < larafale> Hey guys, anyone knows why my lnd is trying to scan blocks ([INF] LNWL: Started rescan from block 0000000008ca11392fa91c4786e59823a002f4868bdb0c1385b12a2844cbc11f (height 20000)) even thought I'm using a distant bitcoind fullnode already synced ? 12:02 < larafale> how can i make sure lnd is fully connected to my distant bitcoind node via rpc ? 12:02 < PatBoy> close your node ^^ 12:07 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 12:07 -!- wampy_ [~wampy@gateway/tor-sasl/wampy] has joined #lnd 12:07 < mlz> larafale, i don't think you can, i think rpc is for local calls? 12:07 < larafale> @PatBoy just did, effectively lnd fail with my fullnode stopped. good tip :) so I'm connected to a bitcoind fully synced, but then lnd still log that it's scanning blocks 12:08 < mlz> yes lnd has to scan blocks 12:09 < PatBoy> :) 12:09 < larafale> @mlz ok so it's just a scan then, it's not downloading the blockchain right ? (because obviouly my bitcoind has the chain already) 12:09 < PatBoy> no it didnt download it.. just scanning 12:09 < mlz> right lnd doesn't download the chain 12:09 < PatBoy> dont take to long 12:09 < mlz> right 12:11 < larafale> that's weird because it's been running for a couple hours already, i've restarted the lnd deamon, and it keep log this : 12:11 < larafale> Started rescan from block 0000000008ca11392fa91c4786e59823a002f4868bdb0c1385b12a2844cbc11f (height 20000) for 1 address 12:11 < larafale> looks really long (current testnet height is 1293880) 12:11 < PatBoy> ooo i dont know i sync it on mainnet 12:12 < larafale> @PatBoy i'd like to make it work on tesnet first :) 12:13 < larafale> I'm stuck, i've tried removing no-macaroons but still 12:13 < larafale> i cant even connect to faucet, because i get this error 12:13 < larafale> chain backend is still syncing, server not active yet 12:14 < larafale> but my bitcoind is fully sync already 12:14 < larafale> damned :) 12:15 < mlz> maybe it can't sync to a remote bitcoind 12:16 < larafale> @mlz hope it's not that :( 12:16 < larafale> anyone here running lnd with a distant bitcoind testnet node ? 12:17 < mlz> larafale, on the machine that you have this lnd, try this: bitcoin-cli echo hello 12:17 < larafale> @mlz i dont have bitcoin-cli on the machine i'm running lnd 12:17 < larafale> only lnd & lncli 12:17 < mlz> that is why lnd isnot connected to any bitcoind 12:18 < mlz> you don't have the bitcoin.conf of bitcoind on the same machine with lnd? 12:19 < larafale> no, one server run bitcoind, the other lnd. 12:20 < larafale> but the connection seems to work 12:20 < larafale> because when i run "lncli getinfo", i see the last height of the chain. i assume that's my bitcoind returning the info 12:22 < larafale> but synced_to_chain is false 12:22 -!- cryptodechange [~cryptodec@host86-142-246-125.range86-142.btcentralplus.com] has joined #lnd 12:27 < mlz> larafale, this is the current testnet blockheight: "block_height": 1293881, 12:27 < mlz> what does your lnd say if you getinfo? 12:27 < larafale> it says that 12:27 < larafale> 1293881 12:28 < mlz> larafale, does your bitcoind have ZMQ? 12:28 < larafale> yes 12:29 < larafale> my bitcoind is fully working, txindexed, and accessible via rpc 12:29 -!- colatkinson [~colatkins@2620:0:2820:903:5ee0:c5ff:fe8c:502d] has joined #lnd 12:31 < larafale> @mlz by the way thx for helping out. the irc channel is my last resort 12:31 -!- wampy_ [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 12:31 < larafale> i've been on this all day, but still. 12:31 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 12:33 < mlz> larafale, i've never tried to connect lnd to a remote bitcoind and i'm not sure if it's the way to go, you might want to wait for someone who knows the answer for this issue 12:33 -!- rrol[m] [rrolmatrix@gateway/shell/matrix.org/x-wudinpaeslfxppue] has joined #lnd 12:34 < larafale> @roasbeef maybe invoking the god of lightning will show me light :) 12:37 < larafale> @mlz what i still did not get, is why lnd has to scan the chain ? 12:37 < larafale> the logs just printed " Catching up block hashes to height 30000, this might take a while" 12:38 -!- Styils [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 12:38 < larafale> what is that process doing ? 12:39 < larafale> it will take forever to catch testnet height. I thought using bitcoind already synced would have let me install lnd and ready right away 12:39 < mlz> but how does lnd know anything about txs on the chain? 12:39 < larafale> via the rcp call to bitcoind ? 12:39 < Styils> it has to connect to a full node, no? 12:40 < Styils> rpc, ye 12:40 < larafale> but i have a full node (it's bitcoind) 12:40 < mlz> larafale, have you tried "bitcoin-cli echo hello"? 12:41 < mlz> if it doesn't return "hello" then it means there's no rpc 12:41 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Ping timeout: 276 seconds] 12:42 < larafale> @mlz but bitcoin-cli is the client of bitcoind, which is installed on a server 12:42 < larafale> i have another server, where i wanted to have lnd, remotly connected to my bitcoind server 12:43 < larafale> so on my bitcoind server, yes bitcoin return "hello" 12:43 < larafale> but on the lnd server, bitcoin-cli is not installed 12:43 < larafale> which is what i want 12:44 -!- kkt2[m] [kkt2matrix@gateway/shell/matrix.org/x-nyemfzmfsruvocgb] has joined #lnd 12:44 -!- interfect[m] [interfectm@gateway/shell/matrix.org/x-xkrgikvejsgplsby] has joined #lnd 12:44 -!- georgeangel[m] [georgeange@gateway/shell/matrix.org/x-ojajsjqbkqpvppwb] has joined #lnd 12:44 -!- cjd[m] [cdelisle1@gateway/shell/matrix.org/x-zudhfzxvccrvmind] has joined #lnd 12:44 -!- pierce [x43matrixo@gateway/shell/matrix.org/x-iodlgsxxtbsmuyeh] has joined #lnd 12:44 -!- afdudley [afdudleyma@gateway/shell/matrix.org/x-lpstwbcankhhlibq] has joined #lnd 12:44 -!- shem[m] [shemmatrix@gateway/shell/matrix.org/x-yyqrlfeuowltkefu] has joined #lnd 12:45 < mlz> well from what i understand, if on the machine where you have lnd, bitcoin-cli can't return "hello" then it means lnd can't return rpc calls to bitcoind 12:46 < mlz> larafale, can you get lnd to open a channel? 12:46 < larafale> but my rpc credentials are set in my lnd.conf 12:46 < larafale> they point to my bitcoind rpc server 12:47 < larafale> @mlz no i'm stuck, it's looks like it's syncing, but i dont get why 12:47 < mlz> it's still searching for bitcoind? 12:47 < larafale> no no, it's fetching block hashes apparently 12:47 < mlz> what does the log say? 12:47 < larafale> " Catching up block hashes to height 30000, this might take a while" 12:47 < mlz> oh and how long has this been? 12:48 < mlz> so it's still trying to catch up to blocks 12:48 < larafale> like 4 hours 12:48 < mlz> but weird thing is when you do "lncli getinfo" it gives you the current block? 12:49 < larafale> but thi is exactly what i don't get. why is it syncing in the first place ? 12:49 < mlz> larafale, because it has to know txs onchain 12:49 -!- ChunkyPuffs [~ChunkyPuf@gateway/tor-sasl/chunkypuffs] has joined #lnd 12:51 < larafale> but does lnd store that on disk? my bitcoind is txindexed, lnd could simply rpc ask for it when needed. 12:55 < RusAlex> where can I spend my lightning bitcoins ?=) 12:56 < mlz> RusAlex, here: https://hodlmonkey.com/ 12:56 < mlz> RusAlex, bitrefill.com 12:57 < PatBoy> https://hodlmonkey.com/ .. i paid an invoice there this morning :) 12:57 < RusAlex> oh yes. bitrefill 12:57 < mlz> store.blockstream.com 12:57 < RusAlex> is great 13:01 < lndbot> mlz: I've decided I think I might just make an emoji LN store or something 13:01 < mlz> tyzbit haha go for it :D 13:02 < lndbot> Oooh or I could make an emoji bazaar where when your emoji is used you get paid for it 13:02 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 13:02 < lndbot> Let's everyone else make emojis for people to use 13:02 -!- colatkinson [~colatkins@2620:0:2820:903:5ee0:c5ff:fe8c:502d] has quit [Ping timeout: 276 seconds] 13:03 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 13:05 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 13:06 < Veggen> evening. 13:06 < mlz> good morning, Veggen 13:06 -!- cmdrt33 [~mrtee@p200300C503D0D900A8F232EC9F2D90E7.dip0.t-ipconnect.de] has quit [Quit: Leaving] 13:07 -!- fusion44 [~fusion44@128.90.23.242] has quit [Quit: Leaving.] 13:08 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 13:12 < mlz> Veggen, do you know if LND can use a remote bitcoind? 13:13 < PatBoy> RusAlex ... https://mainnet.yalls.org/ 13:15 < lndbot> yes it can 13:15 < lndbot> I've done it 13:15 < lndbot> You just need to have bitcoind listen on all interfaces for it's ZMQ 13:23 < yoo> question. do i actually required either a static ip or a dynamic dns service to keep a lnd node running? 13:24 < Veggen> mlz: I think so. 13:25 < mlz> tyzbit ok, so do you know what's going on with larafale's node? 13:26 < larafale> @mlz may be related with https://github.com/lightningnetwork/lnd/issues/444 13:26 < lndbot> yeah lnd is catching up like it said 13:27 < mlz> tyzbit but it's been hours 13:27 < lndbot> With btcd, it can search for lnd's addresses and just tell lnd what it needs to know... That's neutrino 13:27 < larafale> but catching up on what ? 13:27 < lndbot> With bitcoind it has to transfer more to lnd for it to do the work 13:28 < lndbot> I dunno about hours, but it definitely could take a little time 13:28 < lndbot> It's catching up on any unspent outputs for addresses it has 13:28 < mlz> larafale, catching up on scanning the chain 13:29 < larafale> so it took 1h to scan 10k blocks, i'm now at : Catching up block hashes to height 40000, this might take a while 13:29 < larafale> it's a long way to 1293886 :( 13:31 < mlz> testnet doesn't have as much data as mainnet 13:31 < zyp> larafale, what hardware is that on? 13:31 < mlz> tyzbit it's very slow for his node to scan, could it be because of the internet speed or something? 13:32 < larafale> digital ocean droplet, 1Go ram 13:32 < larafale> small but still 13:32 < mlz> ah that's very little ram 13:32 < mlz> my vps has 8GB ram, lnd can just zip by 13:32 < zyp> don't think ram is a huge concern, but it probably doesn't get much cpu 13:33 < zyp> or, well, caching the UTXO set in RAM should speed it up a lot, so that matters too 13:37 <@roasbeef> if you start bitcoind and lnd concurrently (from scrtch), then lnd doesn't know that hte current chain "tip" is 13:37 <@roasbeef> so better to just let the node sync, _then_ start ln 13:37 <@roasbeef> d 13:37 < mlz> roasbeef, his bitcoind is fully synced 13:37 <@roasbeef> oh but still bitcoind initial catch up can take a while 13:38 <@roasbeef> we need to manually fetch a lot of data 13:38 <@roasbeef> due to the lack of the RPC interface of bitcoind compared to btcd 13:38 < mlz> roasbeef, could you tell him why LND has to "catch up" and scan the chain 13:38 <@roasbeef> the wallet needs the headers 13:38 <@roasbeef> to be able to handle re-orgs of any size 13:38 <@roasbeef> if its a remote node, then that adds a lot of time due to round trip latency 13:38 < mlz> larafale, ^^ 13:54 < larafale> @roasbeef ok thx very much for the explanation. agree, roundtrip via rpc with low memory hardware especially if the rpc calls aren't batched is no good for speed. well in my case it take so long it's not viable. I hoped I could easely bootstrap lnd nodes & linked them to my different remote fullnode (bitcoin-core) 13:54 < larafale> @mlz thx a lot for your investigation, really appreciate :) 14:03 < RusAlex> when I need to openchannel do I need to have a white ip address ? 14:03 < RusAlex> or I can be inside of NAT ? 14:03 < mlz> larafale, haha np, i've learned something too, i should try to use a remote bitcoind to learn how to do this :D 14:04 < mlz> RusAlex, you can be behind NAT 14:04 < RusAlex> im having to open a channel 14:04 < RusAlex> I've connected to desired node, bitrefill 14:04 < RusAlex> but when I type openchannel it freezes 14:04 < mlz> cool, yea i like bitreffill 14:05 < RusAlex> 2018-04-22 23:04:48.367 [INF] FNDG: Starting funding workflow with 52.16.240.222:9735 for pendingID(1257518d3be62726d9b24ae78235194188576340d3c317003e6f0f0a5985ab4b) 14:05 < RusAlex> 2018-04-22 23:04:48.367 [INF] SRVR: Attempting to send msgs 1 to: 024a2e265cd66066b78a788ae615acdc84b5b0dec9efac36d7ac87513015eaf6ed 14:05 < mlz> hm 14:05 < RusAlex> and do not proceed 14:06 <@roasbeef> RusAlex: well if you can't accept incoming connections i you're behind a NAT 14:06 <@roasbeef> but there's a pending PR which can handle one level of NAT 14:06 <@roasbeef> beyond that'd we'd recommend using tor onion services 14:06 < mlz> roasbeef, but he's doing an outcoming tx 14:06 <@roasbeef> could be a delayed rejection of chan size? 14:07 < mlz> oh yea 14:07 <@roasbeef> larafale: yeh the issue is bticoind doesn't have a getheaders liek command 14:07 < mlz> i think the min chan size for bitrefill is 200000 sat 14:07 <@roasbeef> so we need to fetch them all 1 by 1 14:07 <@roasbeef> RusAlex: what commit are you running? 14:08 < RusAlex> oh...interesting question. 14:08 < RusAlex> go get -d github.com/lightningnetwork/lnd 14:09 < RusAlex> ok b0709b45f7af9314481d06e617b1cee088fd708e 14:09 < Veggen> roasbeef: What about payer choosing min liquidity for routing channels? 14:09 < RusAlex> this commit 14:09 < Veggen> so, "avoid <50k" ? 14:09 <@roasbeef> RusAlex: did you do make? 14:10 < Veggen> should help a bit on the dust channel issue. 14:10 <@roasbeef> huh? 14:10 <@roasbeef> dust channels is just not accepting them 14:10 <@roasbeef> peeps don't realize smaller channels aren't suuuper useful, until AMP is widely implemented 14:11 < RusAlex> @roasbeef not sure =) go get did everything 14:11 < Veggen> roasbeef: mmm, but there's currently some nodes floating around with >100 minimum size channels. 14:11 <@roasbeef> i mean, make sure that all the dependancies are proper 14:11 <@roasbeef> Veggen: they'll learn eventually lol 14:11 < Veggen> roasbeef: unless they are there to confuse routing algorithms and create FUD? 14:12 < RusAlex> roasbeef: I can open channels to local lnd node (another one) and just opened channel to rompert.com 14:12 < RusAlex> I think it's connected to bitrefill so I can send payment through it 14:13 <@roasbeef> Veggen: dunno, won't really confuse, we'll just ignore 14:13 <@roasbeef> RusAlex: could be something on their side, dunno 14:13 < mlz> RusAlex, don't open a channel to rompert.com, let him do it :D 14:14 < mlz> rompert would open a channel to everybody 14:14 < RusAlex> mlz: do not understand 14:14 < Veggen> yah..but, say you have 10k to transfer. Then you have a ton of 20k channels that half of them can't probably forward your TX. 14:14 < rompert> mlz: heh then i would end up with a node with only outbound capacity. quite useless :) 14:14 < mlz> haha 14:15 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 14:15 < mlz> im about to close channel with "pebble island", quite a useless channel there 14:15 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 14:15 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has quit [Read error: Connection reset by peer] 14:15 -!- melvster [~melvin@ip-86-49-18-198.net.upcbroadband.cz] has joined #lnd 14:16 < lndbot> personally, dust channels opened to me don't bother me much 14:16 < lndbot> I manage my node from Splunk data and probably eventually with lncli-web 14:16 < lndbot> one day our nodes will have hundreds of channels 14:16 < lndbot> I think some already do 14:17 < mlz> tyzbit i think half of channels on mainnet are tiny dusty useless channels 14:17 < lndbot> 20k sats is enough for micropayments 14:18 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #lnd 14:18 < lndbot> I'm fine with those, I want people to pay for articles with them 14:18 < lndbot> my grand plan is to have a browser extension that you can configure to autopay invoices as you browse, hitting your local LND's RPC 14:19 < lndbot> (and having client<->server use HTTP 402 to transparently handle payment reqs) 14:19 < lndbot> I think Blockstream already has something along those lines they're working on in hush-hush mode though, I've seen something called `nanopay` in some of their blog posts 14:21 < lndbot> also I am the suckiest dev ever so if that does end up existing, it probably won't be with much help from me - my Javascript and Go skills are atrocious 14:24 <@roasbeef> tyzbit: well their thing afaik jsut configures to some remote node 14:24 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 14:24 <@roasbeef> and afaik they have zero auth on their RPC system 14:24 <@roasbeef> well beyond filesystem permissions 14:24 <@roasbeef> of the socket 14:24 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 14:24 < lndbot> yeah, I know at the very least it'd be no small task to re-architect it from C-L to lnd 14:25 < lndbot> at best I could reuse the UI and some logic, assuming they even release it + the source 14:25 < jojeyh> is there any higher level material that details the current routing scheme used in lnd ? 14:25 <@roasbeef> the code 14:25 < jojeyh> lulz 14:25 < jojeyh> fair enough 14:26 < lndbot> but man, I work for a newspaper and I'd LOVE to be the first to have LN payments for our articles without the shitty ads, bullshit tracking, and garbage. You request premium.newspaper.com, your client pays the invoice, you get text + pictures and that's it. 14:28 < lndbot> I spun up c-lightning + wordpress + lightning charge on a dev kubernetes cluster just for grins :slightly_smiling_face: 14:28 < mlz> is it easy to do? 14:28 < lndbot> looking forward to that lightning-charge-like middleware for lnd though 14:28 < lndbot> if you already have some stuff in place, yeah 14:28 < mlz> thinking of how btcpay works with lnd, i'd like to look into it 14:28 <@roasbeef> eh, charge is required as their RPC is pretty bare 14:29 < lndbot> Docker makes stuff easy to do generally 14:29 <@roasbeef> lnd already gives you all the functionality 14:29 < lndbot> I might have my deployment configs around here somewhere I can pastebin, though IIRC I had to build some images myself 14:31 -!- jojeyh [~delphi@2602:306:b8b6:b970:480d:4d9:1a02:1755] has quit [Quit: Ex-Chat] 14:31 -github-lnd:#lnd- [lnd] tyzbit opened pull request #1117: allow building from child dir (master...docker-improv) https://git.io/vpOKq 14:31 < lndbot> whoops 14:32 -github-lnd:#lnd- [lnd] tyzbit closed pull request #1117: allow building from child dir (master...docker-improv) https://git.io/vpOKq 14:37 < mlz> haha what happened? 14:37 < lndbot> I wanted to trigger a new build of my lnd docker image, but accidentally opened a PR against the main repo rather than my own fork 14:39 < mlz> ah i see 14:51 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has quit [Remote host closed the connection] 14:56 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has joined #lnd 15:04 -!- spinza [~spin@196.212.164.26] has quit [Quit: Coyote finally caught up with me...] 15:14 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 15:14 -!- wampy_ [~wampy@gateway/tor-sasl/wampy] has joined #lnd 15:19 -!- wampy_ [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 15:19 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 15:24 -!- spinza [~spin@196.212.164.26] has joined #lnd 15:25 -!- Pioklo_ [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 240 seconds] 15:30 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Remote host closed the connection] 15:30 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 15:38 -!- CubicEarths [~cubiceart@xdsl-188-155-63-9.adslplus.ch] has quit [Remote host closed the connection] 15:41 -!- CubicEarths [~cubiceart@188.155.63.9] has joined #lnd 15:45 -!- marijnfs_ [~smuxi@2a01:c23:b81a:1c00:15b:4f4f:dd87:198] has quit [Ping timeout: 256 seconds] 15:54 -!- CubicEarths [~cubiceart@188.155.63.9] has quit [Ping timeout: 256 seconds] 15:59 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Remote host closed the connection] 16:00 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has joined #lnd 16:04 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Quit: Leaving] 16:04 -!- larafale [~larafale@ax213-1-82-66-157-194.fbx.proxad.net] has quit [Ping timeout: 240 seconds] 16:07 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 16:07 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 16:29 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 16:29 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 17:10 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 17:10 -!- Fr4nZ82 [571b9d6e@gateway/web/freenode/ip.87.27.157.110] has quit [Ping timeout: 260 seconds] 17:10 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 17:17 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 17:17 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 17:25 -!- richard87_ [~richard87@237.92-221-98.customer.lyse.net] has joined #lnd 17:27 -!- richard87 [~richard87@237.92-221-98.customer.lyse.net] has quit [Ping timeout: 264 seconds] 17:27 -!- richard87_ is now known as richard87 17:28 -!- grafcaps [~haroldbr@50.90.83.229] has joined #lnd 17:36 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has quit [Quit: drexl] 17:58 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 18:09 -!- yoo_ [68fe5fd4@gateway/web/freenode/ip.104.254.95.212] has joined #lnd 18:16 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 255 seconds] 18:17 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 18:18 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 18:21 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 18:28 < PatBoy> hi, is it normal "synced_to_chain": false, after un certain time ? 18:28 < PatBoy> my node is well synched 18:28 < PatBoy> if i stop lnd and restart it... it return to true 18:30 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 18:30 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 18:30 < yoo_> hmm i'm not sure about that myself 18:31 < PatBoy> 2018-04-22 21:29:39.936 [INF] NTFN: New block: height=519499, sha=0000000000000000003495bf6e0184a1f48e2153ad7f78cf979a3539c23d4347 18:31 < PatBoy> 2018-04-22 21:29:39.937 [INF] UTXN: Attempting to graduate height=519499: num_kids=0, num_babies=0 18:31 < PatBoy> i see to new block in lnd 18:32 < PatBoy> "synced_to_chain": true, 18:32 < PatBoy> nevermind .. it return to true itself 18:32 < mlz> are you running your node on a laptop? 18:32 < PatBoy> no 18:33 < PatBoy> an old i5 37xx i think 18:33 < mlz> desktop? 18:33 < PatBoy> 3570k 18:33 < PatBoy> yeah deskopt pc 18:34 < mlz> maybe when the computer goes to sleep, the node stops being synced to chain? 18:34 < PatBoy> nope this computer is up since year lol 18:34 < PatBoy> never sleep :P 18:35 < mlz> im not sure then, only when i ran c-lightning on my WSL Ubuntu, that node never got to the current block, not sure if it can happen to lnd 18:36 < PatBoy> okk 18:36 < mlz> but i do wonder if desktops/laptops can have some glitch 18:37 < PatBoy> win 7 os .. 64bits 18:37 < PatBoy> i dont think desktops or laptop can be a difference 18:37 < mlz> ah you're running lnd on windows.. i've done this too 18:38 < PatBoy> :) 18:41 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 19:00 -!- camulos [~user@36.69.76.30] has joined #lnd 19:15 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 19:15 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 19:25 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 19:25 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 19:26 -!- Soopaman [~soopaman@cpe-70-122-225-218.tx.res.rr.com] has joined #lnd 19:34 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has quit [Remote host closed the connection] 19:35 -!- cubancorona [cubancoron@gateway/vpn/privateinternetaccess/cubancorona] has joined #lnd 19:39 -!- Soopaman [~soopaman@cpe-70-122-225-218.tx.res.rr.com] has quit [Quit: Leaving.] 19:44 <@roasbeef> PatBoy: still synced? 19:45 <@roasbeef> tyzbit: reminds me to freshen up our docker set up a bit 19:45 < lndbot> yeah, you should set up auto builds on dockerhub too ;) 19:46 < lndbot> I don't have much experience with docker compose, but it'd be rad to get a compose file up with like 10 simnet nodes for testing different scenarios 19:46 <@roasbeef> well you can already do that 19:48 <@roasbeef> just isn't well documented enough i guess 19:49 <@roasbeef> once you have the initial cluster up, it's easy to stand up new instances and connecte them to each other 19:49 <@roasbeef> could use a bit of scripting around it to make setting up topologies easier 19:50 < lndbot> yeah, I know it's not hard, I was just talking about like a premade one, or if there's some way to specify "copies" of containers, then script them getting coins, opening channels etc 19:51 < lndbot> then when there's a scenario you wanna test, just bring up the sim cluster and it's ready to go 19:51 <@roasbeef> yeh that'd cool 19:51 <@roasbeef> have been wanting to bulild that for some time lol 19:53 < lndbot> I'll play around and see what I can do, no promises though 19:53 < lndbot> never used docker compose in any real fashion 19:54 <@roasbeef> https://github.com/lightningnetwork/lnd/tree/master/docker 19:56 < mlz> docker seems more complicated than just installing lnd straight in a system 19:56 <@roasbeef> well it can be easier for some people to run, as then the only dep for them is having docker already installed 19:56 <@roasbeef> the container will just script out initial installation like getting go installed 19:57 < lndbot> even better than that, if you already have the image there's no install 19:57 < lndbot> it's essentially download prebuilt image -> run it 19:58 <@roasbeef> yep 19:58 < lndbot> it's a little more work, but the containers are portable, lightweight, repeatably deployable, isolated from each other 19:58 < lndbot> I've never used LXC but they're similar, they just containerize the whole OS rather than just an app 19:59 < lndbot> example: if you wanna try lncli-web to control LND, just run `docker run -it -e SET_LNDHOST=[IP of lightning host]:10009 -v /tmp/config:/config --net=host tyzbit/lncli-web`, where /tmp/config just has your macaroons and cert 20:00 <@roasbeef> yeh we already have images that work and all 20:00 <@roasbeef> just not documented atm lol 20:00 < lndbot> yeah that PR I opened and immediately closed earlier might've actually been useful now that I think about it 20:01 < lndbot> just made your image use more relative paths 20:01 < lndbot> I set up my fork with that and it builds this https://hub.docker.com/r/tyzbit/lnd/ 20:03 < mlz> oh it's on LXC? 20:04 < lndbot> no, Docker 20:11 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 20:11 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 20:29 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 20:29 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 20:30 -!- sneakerhax [~sneakers@unaffiliated/sneakerhead] has joined #lnd 20:33 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 20:33 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 20:36 -!- Styils is now known as Styil 20:39 < mlz> tyzbit i had some bad experience with LXC when trying to build bitcoin on gitian 21:00 -!- Soopaman [~soopaman@cpe-70-122-225-218.tx.res.rr.com] has joined #lnd 21:02 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-lnqefyurumwedxha] has joined #lnd 21:03 -!- wampy_ [~wampy@gateway/tor-sasl/wampy] has joined #lnd 21:03 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 21:22 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Read error: Connection reset by peer] 21:23 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 21:28 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #lnd 21:32 -!- wampy_ [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 21:32 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 21:54 < lndbot> this script is almost done wooo 21:54 < lndbot> two nodes, three nodes and ten node configurations to start with 21:55 < lndbot> the ten node will have channels all over 21:58 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 21:59 -!- Soopaman [~soopaman@cpe-70-122-225-218.tx.res.rr.com] has quit [Quit: Leaving.] 22:15 -!- Relaed [~yaoyuan@203-179-90-205.cust.bit-drive.ne.jp] has quit [Ping timeout: 256 seconds] 22:22 -!- wampy_ [~wampy@gateway/tor-sasl/wampy] has joined #lnd 22:24 -!- wampy_ [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 22:24 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 22:25 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 22:25 < lndbot> hm, it looked like it worked but the channels aren't open even though the tx is confirmed 22:31 -!- Xantanium2 [~Xantanium@149.248.188.211] has quit [Read error: Connection reset by peer] 22:32 -!- Xantanium2 [~Xantanium@ip-149-248-188-211.fibre.fibrestream.ca] has joined #lnd 22:35 -!- Sentineo [~Undefined@unaffiliated/sentineo] has quit [Ping timeout: 240 seconds] 22:36 -!- Sentineo [~Undefined@unaffiliated/sentineo] has joined #lnd 22:48 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 23:00 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has quit [Quit: colatkinson] 23:01 -!- colatkinson [~colatkins@cpe-67-240-56-42.nycap.res.rr.com] has joined #lnd 23:05 -!- Relaed [~yaoyuan@203-179-90-205.cust.bit-drive.ne.jp] has joined #lnd 23:10 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 23:10 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 23:12 -!- wampy [~wampy@gateway/tor-sasl/wampy] has quit [Remote host closed the connection] 23:12 -!- wampy [~wampy@gateway/tor-sasl/wampy] has joined #lnd 23:34 -!- galileopy [~galileopy@unaffiliated/galileopy] has quit [Ping timeout: 260 seconds] 23:44 -!- marijnfs_ [~smuxi@2a01:c23:c01e:d700:15b:4f4f:dd87:198] has joined #lnd