--- Day changed Sun Nov 11 2018 00:01 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 00:05 -!- anorth [~anorth@216-71.dsl.iskon.hr] has joined #lnd 00:54 -!- frib [~dynorsau@pool-108-29-120-95.nycmny.fios.verizon.net] has quit [Quit: Leaving] 01:05 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 01:07 -!- anorth [~anorth@216-71.dsl.iskon.hr] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 01:08 -!- anorth [~anorth@216-71.dsl.iskon.hr] has joined #lnd 01:14 -!- attilio [~attilio@cm-84.212.250.111.getinternet.no] has joined #lnd 01:49 -!- anorth [~anorth@216-71.dsl.iskon.hr] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…] 01:58 -!- aielima [~aielima@gateway/tor-sasl/aielima] has joined #lnd 01:59 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 02:00 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 02:02 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Client Quit] 02:02 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 02:06 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Client Quit] 02:07 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 02:07 < BashCo> how can I force lnd to rescan starting at a certain blockheight? 02:11 < Veggen> think you'll have to rescan from the genesis block for now, but I guess it's on the roadmap to limit it to wallet birthday, at least. 02:16 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 245 seconds] 02:17 < Talkless> BashCo: yeah I thought about the same thing. If I know my lnd wallet was created two months before, why scan whole blockchain..? 02:27 < BashCo> Okay, now can I force a rescan from block 0 then? 02:27 < BashCo> *how 02:28 < Veggen> there's a tool in btcwallet called dropwtxmgr 02:28 < Veggen> dropwtxmgr --db=/path/to/wallet.db 02:29 < Veggen> let me find a more complete tutorial :) 02:29 < Talkless> https://github.com/lightningnetwork/lnd/issues/1494#issuecomment-421908735 BashCo 02:30 < Talkless> I did this too to avoid having 6 forever-pending channels (that tried to spend anready spent utxo), but it didn't helped me :/ 02:31 < Veggen> different problem. those txes are not in wallet.db but in channel.db I guess... 02:49 < BashCo> my original problem was that I had an unconfirmed balance due to a couple pending channels that never closed properly. `blocks_til_maturity` was negative 10000 or something 02:51 < BashCo> so I restored my seed to a new wallet, it completely rescanned, and my balance was confirmed. (maybe I node went down and caused an issue) So I wanted to try rescanning with the original wallet since it has all my payment history. 02:52 < BashCo> so I started looking for `lncli rescan blockheight` 03:09 -!- bitconner [~conner@203.221.127.245] has quit [Ping timeout: 252 seconds] 03:13 -!- aielima [~aielima@gateway/tor-sasl/aielima] has quit [Remote host closed the connection] 03:13 -!- aielima [~aielima@gateway/tor-sasl/aielima] has joined #lnd 03:20 -!- bitconner [~conner@203.221.127.245] has joined #lnd 03:26 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Ping timeout: 268 seconds] 04:11 < BashCo> Electrum claims my lnd seed fails the bip39 checksum. How can I dump the mpk with lnd? 04:27 < Veggen> lnd doesn't use same seed. 04:28 < Veggen> can't import to anything but lnd, I believe. 04:40 < BashCo> odd. I assumed it would work because the description of the create command says the mnemonic is derived from BIP39. 04:41 < BashCo> But restoring the wallet to Electrum is beside the point. I just want to dump my mpk because the wallet is doing weird things that I don't understand. 05:05 < Veggen> Weird things how? 05:05 < Veggen> unconfirmed balance? 05:05 < Veggen> that's a known (and quite annoing :) bug, fixing is in the works. 05:17 < Veggen> Hmm....watching alexbosworths "channel management" talk... 05:19 < Veggen> are we using "current uptime" or "last channel update" as a metric for which channel to route? I imagine that if you select channels that have seen a recent update, your chance of a successful route increases quite a bit. 05:23 -!- anorth [~anorth@216-71.dsl.iskon.hr] has joined #lnd 05:24 -!- math_ [~mario@p4FCB3DE6.dip0.t-ipconnect.de] has joined #lnd 05:24 < BashCo> restoring the wallet seems to have resolved the unconfirmed issue at the cost of purging my tx history. So I try to send the entire balance to an external wallet, but there's no `sendall` which accounts for the required fee. 05:26 < BashCo> when I reduced the send amount enough to account for the fee, it pretended to send by deducting the amount from walletbalance, but didn't broadcast anything. Needed to restart lnd to clear that out. 05:27 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #lnd 05:27 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 264 seconds] 05:28 < BashCo> so at this point I just want to dump my mpk or private keys and import them to another wallet. 05:28 -!- CryptoSigmund [~CryptoSig@ppp-88-217-100-227.dynamic.mnet-online.de] has joined #lnd 05:31 -!- lukedashjr is now known as luke-jr 05:32 -!- drolmer_ is now known as drolmer 05:37 < drolmer> I have some pending_open channels whose TX is non-existent, and some pending_close that haven't matured yet.... if I use the dropwtxmgr (and `unlock --recovery_window=9999`) will the wallet lose the non-matured balances? 06:21 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #lnd 06:22 < Talkless> drolmer: dropwtxmgr didn't helped for me 06:22 < Talkless> (don't know anything about that unlock) 06:23 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 268 seconds] 06:26 -!- lukedashjr is now known as luke-jr 06:31 -!- lukedashjr [~luke-jr@unaffiliated/luke-jr] has joined #lnd 06:31 < drolmer> Talkless: thx 06:31 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 246 seconds] 06:32 < Talkless> drolmer: there's bug report: https://github.com/lightningnetwork/lnd/issues/1494 06:33 < Talkless> Veggen says maybe we should deal with channel.db..? 06:35 -!- anorth [~anorth@216-71.dsl.iskon.hr] has quit [Quit: Textual IRC Client: www.textualapp.com] 06:35 -!- lukedashjr is now known as luke-jr 06:35 < Veggen> hmm..forever pending open. those will be fixed soonish, I believe. 06:36 < Veggen> if not already fixed in master. 06:37 < Talkless> fixed to not appear, or they will actually dissapear? :) 06:37 < Veggen> fixed to not appear :) 06:37 < Talkless> aww :( 06:37 < Veggen> you might try to force-close them, even though they are pending open. 06:37 < Talkless> so how to dealn with these 6 lingering souls I have in "pendingchannels" ? 06:38 < Talkless> oh, interesting, worth try 06:38 < Veggen> that made them go away last time I had such an issue. 06:39 < molz> Talkless, restarting lnd doesn't make them go away? 06:39 < Veggen> hmm. Need to pay this one a visit in june :) https://inbitcoin.it/it/press/la-prima-transazione-lightning-network-europa-e-stata-eseguita-t/ 06:39 < Talkless> molz: Ive did dropw..., ldn rescaned, multiple reboots done, no, they do not dissapear. 06:41 < Veggen> https://inbitcoin.it/en/press/first-lightning-network-transaction-europe-has-been-executed-thr/ for those not understanding italian :) 06:41 < Talkless> Veggen: fore-closing did this: 06:41 < Talkless> [ERR] CNCT: ChannelArbitrator(f22b0cf0fb8841fa6218145d91a9e5b8212e7d62658890ed5698fd39fecdab16:1 06:41 < Talkless> ): unable to broadcast close tx: Transaction rejected: output already spent 06:42 < Veggen> yup...but did the channel go away? 06:42 < Talkless> yay, it did! 06:42 < Talkless> thanks Veggen 06:42 < Talkless> gonna do 5 more :) 06:42 < Veggen> no problem. 06:47 < molz> i've never had this problem on mainnet or testnet but other issues 06:47 < molz> i'm testing bitcoind with the new zmq PR that got merged 06:48 < Talkless> feels good.. my lnd is clean now, thanks again Veggen :) 06:50 < molz> Talkless, hm i saw your issue where you said "I still see 6 pending channels with non-existing channel_point's" Does it mean those channel_points weren't on your screen or just weren't on explorers? 06:50 < Talkless> wherent on explorers 06:50 < Talkless> my local bitcoind didn't found them 06:50 < Talkless> and lnd log says these outputs where already spen 06:50 < Talkless> spent 06:51 < Talkless> basically, lnd tried to double-spend or smth. 06:52 < Talkless> drolmer: try force-closing channels 06:57 < molz> yea it sounds that your bitcoind somehow didn't know about those txs and it's alarming not just one tx but six 07:01 < Veggen> molz: most likely the fee estimation bug we had? 07:01 < Veggen> how current is your LND? 07:01 < Veggen> (Talkless) 07:01 < Talkless> Veggen: you mean commit? Maybe a week old 07:02 < Talkless> molz: my bitcoind was on load, and I believe it dropped RPC connections 07:02 < Talkless> if I recall that, that was quiiiite some time ago 07:03 < Talkless> Veggen: 0.5.0-beta commit=v0.5-beta-295-gb6009850635cf966eb3bd637de5da89cb9262589 07:03 < Veggen> oh, hmm. at what commit was your 6 bad channels created? 07:03 < molz> well we've had issue with zmq but now there's hope it's fixed in bitcoin master 07:03 < Veggen> (approximately) 07:03 < Talkless> Veggen: IDK that was long time ago 07:03 < Veggen> ok. 07:04 < Talkless> before 0.5 I believe 07:04 < Veggen> then it was probably the same bug I was hitting at that time. 07:04 < Talkless> Veggen: due to RPC issues? 07:04 < Veggen> that is fixed in 0.5, though we have a fresh set of bugs :) 07:04 < Talkless> heh 07:05 < Talkless> Veggen: I have issue when paying to Bitrefill, payment hangs forevder https://github.com/lightningnetwork/lnd/issues/2141 07:05 < Talkless> I thought it's because high load after lnd is restartet, but doesn't seem tha case 07:05 < Talkless> satoshis.place works fine, for example. 07:05 < Veggen> happens to me too. 07:05 < Veggen> needs to get better :) 07:05 < molz> probably bitrefill node was having issue 07:06 < Talkless> That's kinda big issue, as wen we will have AMP, the more routes are used, the more we will hit these lingering nodes :/ 07:06 < Veggen> yup, or some node at the way. 07:06 < Talkless> lnd could use some heuristics to not use "problematic" path again, as it froze me 3 or more times... 07:06 < Veggen> talkless: we need to be better at detecting those, and learning from it and avoiding it when routing. 07:06 < Talkless> note shure if it's possible to detect that something's "problematic" 07:07 < molz> satoshis node goes down a lot too.. because it's hosted on a rpi lol 07:07 < molz> i had a channel with sp for a while, not anymore 07:09 < Talkless> molz: what's your current payment / chaintxn ratio? 07:09 < Talkless> echo "scale=2; $(lncli listpayments | fgrep payment_hash -c) / $(lncli listchaintxns | fgrep tx_hash -c )" | bc 07:10 < Talkless> getinfo could have this statistics? :) 07:10 < Talkless> how much onchain txns saved 07:10 < Talkless> mine is 0.42 :( 07:10 < Talkless> all these issues and force-closing and produces quite some tx for me 07:11 < Veggen> mine is 324 07:11 < Veggen> eh, 3.24 07:12 < Talkless> wow, awesome B) 07:17 < molz> Talkless, i don't have one, i retired my old node 07:17 < molz> i have another node with no channel 07:17 < Talkless> h 07:17 < Talkless> oh 07:18 < molz> tired of dealing with inactive channels, flappy nodes, 07:21 < molz> closing txs in pending forever and coins dont come back to wallet whether they're dust or not 07:22 < molz> but im still running nodes on testnet, we're going to get to the bottom of all issues 07:25 < Talkless> Veggen: about that upcomming lightning app, will it be safe to use it over net, access your own node? 07:25 < Talkless> or it's more like for lan.. controlling your lnd on this computer or in lan? 07:25 < Talkless> or one just opens RPC port with some authentication..? 07:33 < Veggen> the lightning app is meant as standalone with internal LND. 07:34 < Veggen> I guess you could use it to control a remote one, though, with not too many modifications... 07:34 < Veggen> safe? well, as safe as it is to open up rpc to where the app is running. 07:35 < Veggen> I'd try avoiding open up rpc to the world, even if its macaroon authenticated. 07:36 < Veggen> (only to places you control that are meant to use it) 07:37 < Talkless> oh internal lnd, got it. 07:38 < Talkless> I like idea of having 24/7 arm node to comtribute to the network, but not sure how one could use it on the go. SSH with pubkey auth and cli.. from phone terminal app? c'mon :) 07:39 < molz> currently some people use Zap on their iphone to access their lnd node 07:39 < Veggen> And Shango or something for Android. 07:40 < molz> there's also a wrapper called "thin client" for this 07:40 < molz> oh really 07:43 < Talkless> oh right Zap, forgot about that 07:43 -!- Giszmo [~leo@190.162.241.129] has joined #lnd 07:51 -!- jchia_2 [~jchia@58.32.68.242] has joined #lnd 08:04 -!- bitconner [~conner@203.221.127.245] has quit [Ping timeout: 252 seconds] 08:30 -!- bitconner [~conner@203.221.127.245] has joined #lnd 08:35 -!- bitconner [~conner@203.221.127.245] has quit [Ping timeout: 272 seconds] 09:11 < BashCo> jeez. In order to retrieve all my funds from lnd without leaving any dust behind, I had to write a script that reduced the amount of `sendcoins` by 1 satoshi for every attempt until one was finally accepted. Took 2500 cycles. 09:11 < BashCo> how do you guys normally do this in the absence of a `sendall` command? 09:11 < lndbot> I do it by 50 because it will round a bit 09:12 < lndbot> Might be losing out on some satoshis though 09:16 -!- bitconner [~conner@203.213.82.158] has joined #lnd 09:21 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 272 seconds] 09:39 < waxwing> yeah sweep is kinda a needed feature in a wallet. 09:46 < molz> waxwing, we need your listunspent merged! :D 09:47 -!- TheFuzzStone[m] [thefuzzsto@gateway/shell/matrix.org/x-pjqjbykstugzcuoh] has joined #lnd 09:47 < waxwing> molz, well, i think it was marked for 0.5.2 ..i *think* it's ready although there were a bunch of fiddly details. 10:33 -!- deusexbeer [~deusexbee@080-250-077-159-dynamic-pool-adsl.wbt.ru] has quit [Quit: Konversation terminated!] 11:03 -!- bitconner [~conner@203.213.82.158] has joined #lnd 11:08 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 250 seconds] 11:17 -!- marijnfs [~marijnfs@2a01:c22:6e03:3700:725b:cf7f:9fc3:b854] has joined #lnd 11:20 < Talkless> molz: listunspent? 11:28 < molz> yea, waxwing has a PR for listunspent 11:30 < molz> https://github.com/lightningnetwork/lnd/pull/1984 11:31 < molz> if you have too many utxo's that would help to count the inputs when you do a withdraw all 11:31 < molz> when we still don't have that command 11:31 < molz> and then we can use the way waxwing showed me how to calc vsize and figure out the fee 11:32 < molz> but i did this manually once, counting the utxo and figured the vsize, and i got the fee exactly :D 11:32 < molz> pretty fun to do it 11:33 < molz> here's how to count the vsize of a tx: 12 + (40*n) + 0.25*(109*n) + (32*m) where n is the number in and m is the number out 11:33 < waxwing> there's so much to do on the LN stuff it's not really surprising that the basic wallet doesn't have absolutely everything you want :) 11:34 -!- bitconner [~conner@203.213.82.158] has joined #lnd 11:41 -!- marijnfs [~marijnfs@2a01:c22:6e03:3700:725b:cf7f:9fc3:b854] has quit [Ping timeout: 252 seconds] 11:43 -!- marijnfs [~marijnfs@2a03:8600:1001:1013::1015] has joined #lnd 11:44 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 272 seconds] 12:01 -!- melvster [~melvin@ip-86-49-18-46.net.upcbroadband.cz] has quit [Ping timeout: 268 seconds] 12:02 -!- melvster [~melvin@ip-86-49-18-46.net.upcbroadband.cz] has joined #lnd 12:08 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 12:12 < molz> yup haha :) 12:16 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 12:53 < stevenroose> roasbeef: am I correct thinking lnd reuses the p2p networking logic from btcd? 12:55 -!- bitconner [~conner@203.213.82.158] has joined #lnd 13:00 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 246 seconds] 13:03 -!- bitconner [~conner@203.213.82.158] has joined #lnd 13:04 -!- CryptoSigmund- [~CryptoSig@ppp-88-217-100-227.dynamic.mnet-online.de] has joined #lnd 13:05 -!- CryptoSigmund- [~CryptoSig@ppp-88-217-100-227.dynamic.mnet-online.de] has quit [Remote host closed the connection] 13:05 -!- CryptoSigmund- [~CryptoSig@ppp-88-217-100-227.dynamic.mnet-online.de] has joined #lnd 13:07 -!- CryptoSigmund [~CryptoSig@ppp-88-217-100-227.dynamic.mnet-online.de] has quit [Ping timeout: 240 seconds] 13:07 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 245 seconds] 13:11 -!- CryptoSigmund- [~CryptoSig@ppp-88-217-100-227.dynamic.mnet-online.de] has quit [Remote host closed the connection] 13:12 -!- CryptoSigmund- [~CryptoSig@ppp-88-217-100-227.dynamic.mnet-online.de] has joined #lnd 13:24 -!- grafcaps [~haroldbr@75.112.211.230] has quit [Ping timeout: 268 seconds] 13:34 -!- bitconner [~conner@203.213.82.158] has joined #lnd 13:38 -!- colatkinson [~colatkins@pool-108-14-231-114.nycmny.fios.verizon.net] has joined #lnd 13:39 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has quit [Ping timeout: 244 seconds] 13:39 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 245 seconds] 13:40 -!- colatkinson [~colatkins@pool-108-14-231-114.nycmny.fios.verizon.net] has quit [Read error: Connection reset by peer] 13:40 -!- colatkinson [~colatkins@pool-108-14-231-114.nycmny.fios.verizon.net] has joined #lnd 13:45 -!- grafcaps [~haroldbr@047-227-079-209.res.spectrum.com] has joined #lnd 13:47 -!- colatkinson [~colatkins@pool-108-14-231-114.nycmny.fios.verizon.net] has quit [Quit: colatkinson] 13:55 -!- grafcaps [~haroldbr@047-227-079-209.res.spectrum.com] has quit [Ping timeout: 240 seconds] 14:00 -!- CryptoSigmund- [~CryptoSig@ppp-88-217-100-227.dynamic.mnet-online.de] has quit [Ping timeout: 252 seconds] 14:07 -!- CryptoSigmund- [~CryptoSig@ppp-88-217-100-227.dynamic.mnet-online.de] has joined #lnd 14:12 -!- grafcaps [~haroldbr@75.112.211.230] has joined #lnd 14:16 -!- grafcaps [~haroldbr@75.112.211.230] has quit [Ping timeout: 252 seconds] 14:17 -!- CryptoSigmund- [~CryptoSig@ppp-88-217-100-227.dynamic.mnet-online.de] has quit [Quit: Leaving] 14:38 -!- marijnfs [~marijnfs@2a03:8600:1001:1013::1015] has quit [Ping timeout: 252 seconds] 14:58 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 15:02 -!- melvster [~melvin@ip-86-49-18-46.net.upcbroadband.cz] has quit [Ping timeout: 244 seconds] 15:04 -!- bitconner [~conner@203.213.82.158] has joined #lnd 15:30 -!- bitconner [~conner@203.213.82.158] has quit [Ping timeout: 252 seconds] 15:43 -!- bitconner [~conner@220-244-36-124.static.tpgi.com.au] has joined #lnd 15:55 -!- aielima [~aielima@gateway/tor-sasl/aielima] has quit [Remote host closed the connection] 16:04 -!- stiell [~stian@fsf/member/stiell] has quit [Ping timeout: 245 seconds] 16:12 -!- stiell [~stian@fsf/member/stiell] has joined #lnd 16:20 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 252 seconds] 16:40 <@roasbeef> stevenroose: no 16:41 <@roasbeef> BashCo: negative 1k maturity is usually due to low fees if it's a lingering channel, there's a fix to revamp the way we batch sweeps internally to fix that 16:41 <@roasbeef> BashCo: see import or rescan won't help with that, it's in a special script on chain 16:42 <@roasbeef> BashCo: create totally doesn't say it's bip39, it's diff entirely a new scheme all together, just uses an overlapping word list 16:43 <@roasbeef> drolmer: pending open w/ no close, would mean it was never broadcast, if was never broadcast by the initiator (if not you), then we'l forgte it eventually 17:09 < qubenix> wpaulino: you around? 17:16 < wpaulino> qubenix: what's up 17:17 < wpaulino> the tor address filtering that you saw doesn't apply when using the connect rpc 17:17 < wpaulino> only applies to reestablishing persistent conns to peers on startup 17:17 < wpaulino> so if you connect manually even if tor is disabled it will try it 17:18 < qubenix> first, if i set tor.active=1 lnd no longer listens 17:18 < wpaulino> ah yeah forgot about that 17:18 < qubenix> second, when trying to connect to my onions without tor.active=1 it doesn't even try 17:19 < qubenix> i see a curl to my onions in the logs, but nothing from lncli connect 17:19 < wpaulino> lncli doesn't filter it 17:19 < qubenix> i see it's initated on one side and just hangs, but nothing on the receiving side 17:20 < wpaulino> the thing is it uses the system's default resolver since tor isn't active 17:20 < wpaulino> which can't reach onion addrs 17:20 < qubenix> it can on mine, i can curl them from same vm 17:21 < qubenix> and the receiving end gets a invalid handshake in the logs, but not throuhg lncli 17:23 < wpaulino> not sure what it could be then, just know we don't do any filtering when manually connecting to addresses 17:25 < qubenix> ok, i'll keep digging. thanks for your help. 17:27 < wpaulino> would help out but don't have that setup to test it 17:27 < wpaulino> you're saying lncli just hangs? 17:27 < wpaulino> and how do you see the connect initiated? tor logs? 17:27 < qubenix> just started my nodes up and right now i'm getting "no suitable address" error 17:30 < wpaulino> qubenix: seems related https://github.com/golang/go/issues/13705 17:30 < wpaulino> PR #2120 is the proper fix, would just wait for that to get in 17:30 < wpaulino> can push for it once 0.5.1 is out 17:31 < qubenix> that error was new. what usually happens with srvr=trace it says connecting to blabla.onion but then never any follow up. 17:31 < qubenix> and on the other end nothing 17:33 < wpaulino> yeah because you're attempting to resolve an onion addr with the default resolver, which go doesn't allow 17:34 < qubenix> oh, how can i fix that? 17:35 < wpaulino> again, PR #2120 will fix it by allowing lnd to use the tor resolver 17:36 < qubenix> ok, you want me to close my issue then? 17:36 < wpaulino> no need, can close it once the PR is merged 17:37 < qubenix> ok, when i get a chance i'll test that pr and see if it helps 17:37 < qubenix> thx again 17:38 < wpaulino> qubenix: cool, np 17:48 < qubenix> this is so strange: from 2 nodes on the same vm, reliably one gives the 'no suitable address' error and the other just curly brackets with no error. 17:49 < qubenix> yesterday they both just did curly brackets o.O 17:56 < qubenix> nm, i must've chopped a letter during copy/paste. now they both do curly brackets again. 17:58 <@roasbeef> curly brackts? 17:58 <@roasbeef> patebin le error? 18:01 < qubenix> lncli connect curly brackets from my attempts to connect my onion nodes. i pasted my onion address incorrect so i was getting a different error that threw me for a loop for a minute. 18:02 <@roasbeef> ? 18:02 < wpaulino> curly brackets being an empty response, which means the connection attempt succeeded 18:02 <@roasbeef> oh 18:02 <@roasbeef> that means it worked 18:02 <@roasbeef> lol 18:02 <@roasbeef> could say "yerp, we connected" 18:03 < qubenix> but it doesn't succeed, it doesn't show anything on the receive side at all with srvr=trace. 18:05 < qubenix> and on the initiation side it only shows the connecting to nodekey@onion msg but no follow up 18:06 < qubenix> im running with 2120, how is it supposed to help? still doesn't listen when i have tor.active=1 18:08 < qubenix> seems to only help if im letting lnd set up my onion, but that's another issue because Whonix filters the control port with onion-grater 18:10 < qubenix> so if i have tor.v3=1 it fails with an error about no control cookie path found (even though it's accessible in default spot which is given to apps in an env var, the Tor best practices way) 18:11 < wpaulino> qubenix: 2120 only works if it's a remote tor server, which i'm assuming is your case 18:12 < qubenix> it is my case. i have tor.active=1 and tor.socks=ip:port. no listening. 18:12 < wpaulino> perhaps there's a bug in the PR then, haven't looked at it 18:13 -!- grafcaps [~haroldbr@75.112.211.230] has joined #lnd 18:13 < wpaulino> tor.v3 fails becasue the cookie is on the remote server, which we can't access 18:13 < qubenix> wpaulino: have you seen this: https://trac.torproject.org/projects/tor/wiki/doc/Tor_friendly_applications_best_practices 18:14 < qubenix> no, the cookie is accessible the response you get is just filtered, which is best practice 18:16 < qubenix> wpaulino: this is on the vm with lnd: http://termbin.com/foot 18:17 -!- grafcaps [~haroldbr@75.112.211.230] has quit [Ping timeout: 252 seconds] 18:17 < wpaulino> if the tor server is run on another computer, it won't be able to read the cookie file... 18:17 < wpaulino> everything is set up assuming tor is running locally 18:17 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #lnd 18:17 < qubenix> http://termbin.com/foot 18:18 < qubenix> why can the same user cat the cookie then? 18:18 < wpaulino> is lnd also running on this host? 18:18 < qubenix> yes, of course 18:19 < wpaulino> as well as tor? 18:19 < qubenix> lnd isn't even trying the default spot, it's asking the control port and failing when the response is filtered 18:19 < qubenix> https://www.whonix.org/wiki/Dev/Whonix_friendly_applications_best_practices 18:19 < qubenix> see there about control port filtering 18:20 -!- Styils [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 18:21 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Read error: Connection reset by peer] 18:21 < qubenix> theres a lot to be gleaned from the environment too: http://termbin.com/tkuj 18:23 -!- ken2812221 [~ken281222@110.50.135.219] has quit [Ping timeout: 272 seconds] 18:37 <@roasbeef> waxwing: so have the same need right now, might extened SignOutputRaw to attempt to look up the key based on the script 18:37 <@roasbeef> as ComputeInputScript does 19:13 -!- bitconner [~conner@220-244-36-124.static.tpgi.com.au] has quit [Ping timeout: 272 seconds] 19:18 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 268 seconds] 19:20 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #lnd 19:23 -!- colatkinson [~colatkins@pool-108-14-231-114.nycmny.fios.verizon.net] has joined #lnd 19:39 -!- colatkinson [~colatkins@pool-108-14-231-114.nycmny.fios.verizon.net] has quit [Quit: colatkinson] 19:40 < qubenix> wpaulino: http://termbin.com/8l3k < lnd's failed comms with control port and what a success looks like. btw bitcoind is using the control port for its onion address on this vm. 19:46 -!- Styils [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Ping timeout: 276 seconds] 19:47 -!- colatkinson [~colatkins@pool-108-14-231-114.nycmny.fios.verizon.net] has joined #lnd 20:39 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Remote host closed the connection] 20:58 -!- Giszmo [~leo@190.162.241.129] has quit [Ping timeout: 246 seconds] 21:24 -!- Giszmo [~leo@ip-213-236-219-201.nextelmovil.cl] has joined #lnd 21:46 -!- colatkinson [~colatkins@pool-108-14-231-114.nycmny.fios.verizon.net] has quit [Quit: colatkinson] 21:47 -!- bitconner [~conner@175.45.73.99] has joined #lnd 21:49 -!- Giszmo [~leo@ip-213-236-219-201.nextelmovil.cl] has quit [Ping timeout: 240 seconds] 21:55 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 21:57 <@roasbeef> qubenix: is the cookie on the same machine? 21:57 <@roasbeef> also waht vesion of tor? 21:58 <@roasbeef> we first try to find the cookie and get the version so we can know if we can do v3 or not 21:58 <@roasbeef> btw thx for putting our tor integration thru the works! 22:04 <@roasbeef> ah no auth there 22:04 <@roasbeef> so we should just go ahead and try to connect, if auth is null, and the control file isn't actually specified 22:08 -!- Giszmo [~leo@190.162.241.129] has joined #lnd 22:16 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Remote host closed the connection] 22:17 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 22:20 < qubenix> roasbeef: exactly, for security whonix (and other privacy systems) filters the control port using onion-grater. 22:24 -!- bitconner [~conner@175.45.73.99] has quit [Ping timeout: 264 seconds] 22:24 -!- bitconner [~conner@175.45.73.99] has joined #lnd 22:29 -!- bitconner [~conner@175.45.73.99] has quit [Ping timeout: 252 seconds] 22:29 -!- Deadlyelder [~textual@158.64.79.8] has joined #lnd 22:52 -!- Deadlyel_ [~textual@158.64.79.8] has joined #lnd 22:52 -!- Deadlyelder [~textual@158.64.79.8] has quit [Ping timeout: 272 seconds] 23:01 -!- grafcaps [~haroldbr@75.112.211.230] has joined #lnd 23:08 -!- grafcaps [~haroldbr@75.112.211.230] has quit [Ping timeout: 240 seconds] 23:10 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds] 23:12 -!- Styils [Styil@gateway/vpn/privateinternetaccess/styil] has joined #lnd 23:12 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd 23:15 -!- Styil [Styil@gateway/vpn/privateinternetaccess/styil] has quit [Ping timeout: 244 seconds] 23:30 -!- Deadlyelder [~textual@158.64.79.7] has joined #lnd 23:31 -!- Deadlyel_ [~textual@158.64.79.8] has quit [Ping timeout: 264 seconds] 23:36 -!- Deadlyel_ [~textual@158.64.79.8] has joined #lnd 23:38 -!- Deadlyelder [~textual@158.64.79.7] has quit [Ping timeout: 240 seconds] 23:57 -!- kalle [~kalle@2a00:801:e0:30:8987:49c1:c531:fb11] has quit [Quit: Leaving]