--- Day changed Tue Apr 02 2019 00:04 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 246 seconds] 00:17 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Ping timeout: 256 seconds] 00:18 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 00:18 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds] 00:20 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 00:22 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd 00:51 -!- shtirlic [~shtirlic@ec2-18-185-133-40.eu-central-1.compute.amazonaws.com] has quit [Quit: ZNC - http://znc.in] 01:05 -!- shtirlic [~shtirlic@ec2-18-185-133-40.eu-central-1.compute.amazonaws.com] has joined #lnd 01:14 -!- shtirlic [~shtirlic@ec2-18-185-133-40.eu-central-1.compute.amazonaws.com] has quit [Quit: ZNC - http://znc.in] 01:15 -!- shtirlic [~shtirlic@ec2-18-185-133-40.eu-central-1.compute.amazonaws.com] has joined #lnd 01:19 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 01:24 -!- StopAndDecrypt_ [~StopAndDe@96.44.189.226] has quit [Ping timeout: 246 seconds] 01:30 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #lnd 01:31 -!- libertyprime [~libertypr@101.98.42.91] has joined #lnd 03:15 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 03:28 -!- shtirlic [~shtirlic@ec2-18-185-133-40.eu-central-1.compute.amazonaws.com] has quit [Quit: ZNC - http://znc.in] 03:29 -!- shtirlic [~shtirlic@ec2-18-185-133-40.eu-central-1.compute.amazonaws.com] has joined #lnd 03:53 -!- libertyprime [~libertypr@101.98.42.91] has quit [Ping timeout: 252 seconds] 04:21 -!- jchia_ [~jchia@58.32.64.12] has quit [Read error: Connection reset by peer] 04:21 < molz> Veggen, are the counterparties online? 04:22 -!- jchia_ [~jchia@45.32.62.73] has joined #lnd 04:23 -!- jchia_ [~jchia@45.32.62.73] has quit [Remote host closed the connection] 04:24 -!- jchia_2 [~jchia@58.32.64.12] has joined #lnd 04:30 < Veggen> molz, yup. 04:41 < molz> Veggen, testnet? 04:47 < Veggen> of course. 04:48 < Veggen> just testing the restore functionality, really. 04:48 < molz> so are those txs still in waiting close? 04:48 < Veggen> yup. 04:49 < molz> which nodes did you have channels with? if you can post the nodekeys i can check 05:00 < Akihabara> hi guys. my btcd is still syncing. height is around june 2016...its been a week already!!! isnt it toooo slow??? 05:22 < Veggen> 023f76b9c7f0aeaef5302b39126f028b75fda2ac6afa960c18c060d3677b2240b4 with channel point 8660ebcadf3d3295ba74b0b17db2effc6054065faab2018feba55b5bd99ec7dd:0 is one. 05:22 < Veggen> (molz) 05:26 -!- spaced0ut [~spaced0ut@unaffiliated/spaced0ut] has joined #lnd 05:37 < Veggen> ok, created an issue. 05:37 -!- jchia_2 [~jchia@58.32.64.12] has quit [Quit: Leaving.] 05:38 -!- shtirlic [~shtirlic@ec2-18-185-133-40.eu-central-1.compute.amazonaws.com] has quit [Quit: ZNC - http://znc.in] 05:39 -!- shtirlic [~shtirlic@ec2-18-185-133-40.eu-central-1.compute.amazonaws.com] has joined #lnd 05:45 < molz> sorry Veggen got busy here.. sec 05:47 -!- jchia_2 [~jchia@58.32.64.12] has joined #lnd 05:47 < molz> Veggen, ok im going to open a channel to that node and test 05:50 < molz> Akihabara, yes you have been told btcd is much slower to sync than bitcoin core, is there a reason you want to sync a btcd??????? 05:50 < molz> let's put more !!!!! and ????? so btcd can sync faster 05:50 < molz> :P 06:04 < molz> sweeper works nicely, it swept a dust amt of 600 sat that sat in pendingchannels for a few weeks: https://testnet.smartbit.com.au/tx/6a3a626f179f0ace3d8d8452b852c0bd522fd90dc181b4981118d0258415234f 06:09 < Akihabara> moly i just followed the instructions 06:10 < Akihabara> i shall change to bitcoin core then immediatelly 06:16 < molz> Akihabara, what instructions? 07:00 < Veggen> molz, any results? 07:45 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 07:48 < molz> Veggen, "[lncli] unable to restore chan backups: rpc error: code = Unknown desc = unable to unpack chan backup: unable to connect to 023f76b9c7f0aeaef5302b39126f028b75fda2ac6afa960c18c060d3677b2240b4@52.36.54.59:9735 to complete SCB restore: already connected to peer: 52.36.54.59:9735" 07:48 < molz> I opened two channels to this one node and one channel to my c-lightning node 07:58 < Veggen> hmm. Not sure if case was similar. 08:10 -!- david___ [041c3d89@gateway/web/freenode/ip.4.28.61.137] has joined #lnd 08:10 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Read error: Connection reset by peer] 08:11 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 08:11 -!- david___ [041c3d89@gateway/web/freenode/ip.4.28.61.137] has quit [Client Quit] 08:18 < molz> i think it's the problem with that node 08:19 < molz> i just tried to get my desktop eclair app to open a channel to that node but it was in waiting then disappeared 08:20 < molz> woot 08:21 -!- Pioklo_ [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 08:22 < molz> the two channels got resolved in 'restorechanbackup' i got my money back!!! :D 08:22 < molz> Veggen, it gave me that error but the channels still closed 08:22 < Veggen> hm. 08:25 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Ping timeout: 250 seconds] 08:25 < molz> hm but the channel to my c-lightning node didnot close 08:27 < molz> yesterday i tested on another c-lightning node that's running an older version and the channel closed but this one is on v0.7.0 which is newer 08:52 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 09:16 < Talkless> Only two more tasks left, whoo-hoo! https://github.com/lightningnetwork/lnd/milestone/9 10:18 -!- jrick [~jrick@unaffiliated/jrick] has quit [Ping timeout: 268 seconds] 10:21 -!- jrick [~jrick@unaffiliated/jrick] has joined #lnd 12:15 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 12:22 -!- libertyprime [~libertypr@101.98.42.91] has joined #lnd 12:27 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 12:28 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lnd 12:29 -!- libertyprime [~libertypr@101.98.42.91] has quit [Ping timeout: 250 seconds] 13:08 -!- libertyprime [~libertypr@118.149.88.158] has joined #lnd 13:16 < Akihabara> moly there is an installation manual on the internet and it uses the btcd 13:16 < Akihabara> but now im trying again with bitcoind and i see it does sync with over 30-40mbps 13:16 < molz> Akihabara, can you post the link? 13:21 -!- jrick [~jrick@unaffiliated/jrick] has quit [Ping timeout: 268 seconds] 13:24 -!- Ulmo [~qm@2001:5a8:0:1::40b] has joined #lnd 13:25 -!- Ulmo [~qm@2001:5a8:0:1::40b] has quit [Client Quit] 13:25 -!- Ulmo2 [~qm@2001:5a8:0:1::40b] has joined #lnd 13:26 -!- Ulmo2 [~qm@2001:5a8:0:1::40b] has quit [Client Quit] 13:27 -!- Ulmo1010 [47cca2b3@gateway/web/freenode/ip.71.204.162.179] has joined #lnd 13:27 < Ulmo1010> Hello. 13:28 < Ulmo1010> What does this mean in the log: sequence of lines beginning with: Received UpdateFulfilHTLC, Received CommitSig, Adding preimage=, Sending RevokeAndAck, Sending CommitSig, Received RevokeAndACk, ChannelLink, Close completed SETTLE circuit, Tearing down open circuit with SETTLE pkt, Closed complete SETTLE circuit 13:29 < Ulmo1010> Does that mean my payment was made, or was not made? The balance is missing from my channel, and in ZapWallet it says that the payment was made. 13:29 < Ulmo1010> but Bitrefill says the payment did not get made. 13:30 < molz> justin ^^ 13:30 < Akihabara> molly i will try and find it. i closed the tab a week ago 13:32 < Akihabara> so now the bitcoind, doesnt create a bitcoin.conf. so i created manually and added just one line to point the datadir. is it ok, or do i have to add more configuration in the file? 13:33 < Ulmo1010> oh damn double checking my assumption. Let me verify my log is related to the payment. Lines get jumbled. (I've complained about log clarity by this author before to no avail.) 13:35 < molz> Akihabara, look at the topic of this channel 13:36 < molz> Ulmo1010, zap has their own slack, have you asked them for help there? 13:36 < Akihabara> moly : follow the link? 13:36 < molz> Akihabara, sorry? 13:36 < Akihabara> topic of the channel : there is a link 13:36 < molz> you want me to read it for you? 13:37 < Akihabara> no 13:37 < Akihabara> lol 13:39 < Ulmo1010> Yes, I think it's related; the payment_preimage is related to the above lines with the following: "2161170:2019-04-02 12:54:28.202 [DBG] PEER: Received UpdateFulfillHTLC(chan_id=562d933322fe9be4ef0d91529801308e6d20c74178bd3be161e432fcd5cc010e, id=54, pre_image=390de5b6b5bfcc3db8d16352e81ce2116655af797ffd59bf572607e0f9e4fe80) from 138.68.14.104:9735" 13:40 < Ulmo1010> I got confused because the chan_id ending in ...cc010e is not in the listpayments path as a node. Hum... I suppose this channel ID is not the node. Will square down a bit more. 13:42 < Ulmo1010> Adding confusion, the remote_pubkey for the first hop in the listpayments path is in my listchannels, but the channel_point and chan_id do not match ...cc010e. 13:45 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 13:48 < lndbot> Does it show up in listpayments? If you have the preimage and the invoice you can provide that to me and I can verify 13:49 -!- jrick [~jrick@unaffiliated/jrick] has joined #lnd 13:50 < Ulmo1010> Yes: "payment_preimage": "390de5b6b5bfcc3db8d16352e81ce2116655af797ffd59bf572607e0f9e4fe80", "payment_hash": "4546cff16dfdb348647c84d9343f5a82c01cf207d3205d7ff842c058005aa1ca", 13:50 < Ulmo1010> invoice lnbc25246u1pw280fcpp5g4rvlutdlke5serusnvng066stqpeus86vs96llcgtq9sqz6589qdphgf5hgun9ve5kcmpqx43kzvmzvsensdpkvfskxwpsxqcrgc33xg6nzvgcqzpgxqrp9sfppj5pzkk533ecahqt7jgf4sdkdccnme22cl6re7jq5dfn3dk9upy4r7jfhxsnar6k2hme0tkqf6fhan5lyscyt4pe2dp6tpu7lqfvnuzj6psmakv6ncj9q5v2667x03st9th9gey2cqwc6kp5, order# 5ca3bd3846bac80004b12511 13:50 < lndbot> Will check up! 13:52 < Ulmo1010> molz, thanks. Not yet. I didn't know that. I'm seeing similar data in my LND command line, so using that here. Zap is a frontend to LND so I can do it that way. 13:52 < lndbot> ah okay should be good now, temporary issue, sorry about that 13:52 < Ulmo1010> Bitrefill just updated its screen with "The refill delivery has been confirmed by the operator". For future reference, I wonder what happened. 13:53 < Ulmo1010> Thank you Justin 13:53 < Ulmo1010> ! 13:53 < molz> yay, bitrefill is #1 merchant! :D 13:54 < lndbot> Didn't subscribe the invoices properly when it attempted I think or too soon and I didn't properly retry, re subscribed and sent all missed notifications. 13:55 < lndbot> ah yeah, it's cause I restarted it, and RPC commands don't respond for like 5+ minutes still x) 13:55 < Ulmo1010> That's all sensible. 13:56 < Ulmo1010> That explains why I got 38 of these in my log after I made the payment before it completed: " HSWC: Closed completed FAIL circuit for 4546cff16dfdb348647c84d9343f5a82c01cf207d3205d7ff842c058005aa1ca" 14:00 < Ulmo1010> I got 14 of these after I sent payment before it succeeded: "[ERR] CRTR: Attempt to send payment 4546cff16dfdb348647c84d9343f5a82c01cf207d3205d7ff842c058005aa1ca failed: TemporaryChannelFailure(update=(*lnwire.ChannelUpdate)(0x........." 14:03 < Ulmo1010> And 5 "UnknownNextPeer". (14+5)*2=38. Those counts add up correctly. 14:04 < Akihabara> moly bitcoind is so much faster than btcd!!! over 20gb downloaded in a few minutes 14:05 < lndbot> holy moly 14:17 -!- jrick [~jrick@unaffiliated/jrick] has quit [Ping timeout: 245 seconds] 14:19 -!- jrick [~jrick@unaffiliated/jrick] has joined #lnd 15:15 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has quit [Ping timeout: 244 seconds] 15:29 -!- Ulmo1010 [47cca2b3@gateway/web/freenode/ip.71.204.162.179] has quit [Quit: Thank you Molz & Justin (via LNDBot)!] 15:31 -!- CubicEarth [~CubicEart@c-67-168-1-172.hsd1.wa.comcast.net] has joined #lnd 16:08 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Ping timeout: 245 seconds] 16:49 -!- Pioklo_ [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 245 seconds] 16:59 <@roasbeef> molz: hmm yeh I think we shouldn't return an error if we can't connect right then, and should instead do it in teh background 17:00 <@roasbeef> tho, with the way we try to connect it should be perm, so async and not return anything back 17:01 < molz> roasbeef, but that node did close those two channels 17:02 < molz> roasbeef, i also had a channel with my c-lightning node which is in their latest version 0.7.0 and this node didn't close the channel 17:16 < molz> roasbeef, so.. that error is confusing, why did it result in that error message? the node (023f76b9c7f0aeaef5302b39126f028b75fda2ac6afa960c18c060d3677b2240b4) is an LND node 17:18 < molz> (SideShift AI testnet, owned by Andreas) wondering what version/commit he's running 17:30 <@roasbeef> justin: i think y'all will also dig the new sendpaymetn API stuff we're working on, it'll be a diff endpoint all together prob, just to move ppl into this new model 17:30 <@roasbeef> molz: dunno what version, but you can check the logs to see what happened there, they may be on an older version or they just removed the canneel or w/e 17:31 <@roasbeef> ah already connected, ok yeh that's an easy one we can patch 17:31 <@roasbeef> that's the only othe rerror path there that makes sense 17:32 < molz> ny results? 17:32 < molz> Veggen, "[lncli] unable to restore chan backups: rpc error: code = Unknown desc = unable to unpack chan backup: unable to connect to 023f76b9c7f0aeaef5302b39126f028b75fda2ac6afa960c18c060d3677b2240b4@52.36.54.59:9735 to complete SCB restore: already connected to peer: 52.36.54.59:9735" 17:32 <@roasbeef> wat? 17:32 < molz> oops sorry 17:32 < molz> was trying to copy only partial of it 17:33 < molz> so it said "unable to connect to" but then said "already connected to peer" 17:33 < molz> why is that lol 17:33 < molz> and i did try to reconnect to that node, it also said "already connected.." 17:34 <@roasbeef> yeh just a weird message 17:34 <@roasbeef> we shuold ignore that error 17:35 <@roasbeef> about to put up a PR for that ina bit 17:39 < lndbot> nice, have a writeup about the new api or proposed features. Was talking to eclair recently and they're also releasing one out looked good! 17:39 < lndbot> Should probably just deprecate the old one ;P 17:40 < lndbot> I mean they're also working on new one* 17:40 <@roasbeef> releasing one out? 17:40 <@roasbeef> as in modifying their api? 17:41 < molz> you guys have to know it's a pain in the butt for some windows users to just even try 'eclair-cli' on command-line, unlike lnd :D 17:41 <@roasbeef> what's diff about their cli molz ? 17:41 < molz> roasbeef, their desktop app is an app, no executables for cli 17:42 <@roasbeef> but there's a console iirc? 17:42 < molz> well for windows we use Git Bash 17:42 < molz> no problem for linux 17:42 <@roasbeef> i mean a console in their GUI, has been a while since i've used it tho 17:42 < lndbot> yeah, modifying, excuse my poor wording 17:43 <@roasbeef> ah gotcha, yeh iirc they used json-rpc? 17:43 < molz> roasbeef you mean the app GUI? 17:43 <@roasbeef> basically the new one will be: look up payment (streaming), and then start payment 17:43 <@roasbeef> so you lookup first, see if it's done or not, if not, then start it 17:43 <@roasbeef> lookup is streaming, so you'll continue to get updates w.r.t the status 17:43 <@roasbeef> this is the current draft at least 17:46 < lndbot> awesome yeah, that's great, everything I would want is that, similar to what eclair is working on, fire-and-forget api, query status or get real-time updates via a websocket 17:47 < molz> roasbeef, what about the c-lightning in the current version does not comply to our SCB 17:50 < lndbot> anyway as a side note, awesome to see increase volume of people paying with lightning over this fee spike 17:51 < lndbot> same with number of people paying over lightning 17:57 <@roasbeef> molz: they won't always send over the data, we store it on disk to ensure we'll always send it 17:57 <@roasbeef> justin: nice 17:58 < molz> roasbeef, so i force closed the channel on c-lightning node, still waiting to see if the fund goes back to lnd node 17:58 <@roasbeef> force closed manually? 17:58 < molz> yes 17:58 < molz> will the fund go back to lnd node? 18:12 -!- achow101_ [~achow101@unaffiliated/achow101] has joined #lnd 18:12 -!- achow101 [~achow101@unaffiliated/achow101] has quit [Remote host closed the connection] 18:12 -!- drolmer [~drolmer@unaffiliated/drolmer] has quit [Quit: adios] 18:12 -!- drolmer [~drolmer@unaffiliated/drolmer] has joined #lnd 18:15 -!- phantomcircuit [~phantomci@192.241.205.97] has quit [Ping timeout: 246 seconds] 18:17 -!- phantomcircuit [~phantomci@192.241.205.97] has joined #lnd 18:25 <@roasbeef> if you forcec losed manually, then you have the state? 18:25 <@roasbeef> you can't force close yourself with just teh SCB 18:33 < molz> roasbeef, on lnd node, i don't have that force closed channel in 'pendingchannels' 18:33 <@roasbeef> you can't force close from an SCB 18:59 -!- achow101_ is now known as achow101 19:02 -!- achow101 is now known as achow101_ 19:02 -!- achow101_ is now known as achow101 19:18 -!- david___ [6bc71ba4@gateway/web/freenode/ip.107.199.27.164] has joined #lnd 19:20 -!- david___ [6bc71ba4@gateway/web/freenode/ip.107.199.27.164] has quit [Client Quit] 20:13 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 20:43 -!- tynes [~tynes@30.50.237.35.bc.googleusercontent.com] has joined #lnd 21:10 -!- libertyprime [~libertypr@118.149.88.158] has quit [Ping timeout: 255 seconds] 21:12 -!- libertyprime [~libertypr@118.149.88.158] has joined #lnd 21:22 -!- aerth [~aerth@gateway/tor-sasl/aerth] has quit [Ping timeout: 256 seconds] 21:23 -!- libertyprime [~libertypr@118.149.88.158] has quit [Ping timeout: 246 seconds] 21:27 -!- aerth [~aerth@gateway/tor-sasl/aerth] has joined #lnd 21:30 -!- libertyprime [~libertypr@118.149.88.158] has joined #lnd 21:46 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection] 21:46 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd 22:51 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 23:29 -!- fda [080758c3@gateway/web/freenode/ip.8.7.88.195] has joined #lnd 23:29 -!- fda [080758c3@gateway/web/freenode/ip.8.7.88.195] has quit [Client Quit] 23:36 -!- windsok [~windsok@unaffiliated/windsok] has quit [Remote host closed the connection] 23:45 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lnd 23:53 -!- dave_uy [~dave_uy@108.61.193.26] has quit [Quit: The Lounge - https://thelounge.github.io] 23:54 -!- dave_uy [~dave_uy@108.61.193.26] has joined #lnd 23:54 -!- windsok [~windsok@rarepepe.cash] has joined #lnd 23:54 -!- windsok [~windsok@rarepepe.cash] has quit [Changing host] 23:54 -!- windsok [~windsok@unaffiliated/windsok] has joined #lnd