--- Day changed Sat Jan 26 2019 00:01 -!- lnostdal [~lnostdal@77.70.119.51] has quit [Ping timeout: 240 seconds] 00:33 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 00:39 -!- lnostdal [~lnostdal@77.70.119.51] has joined #lnd 00:43 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Remote host closed the connection] 00:45 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has joined #lnd 01:22 < e4xit> I am looking at the gRPC documentation for 'newaddress' (https://api.lightning.community/?python#newaddress) where it says it can take an address type. The address type can be either p2wkh or np2wkh. Passing those as strings (as you would to lncli) does not work, however passing int (e.g. 1 or 2) seems to change the address type... It seems that perhaps the RPC documentation used to show AddressType parameters 01:22 < e4xit> but the hyperlink is broken. Does anyone know where I can find how to pass the address type to the RPC? 01:23 -!- thomasan_ [~thomasand@2605:a601:b021:f00:a946:f6f5:403b:7e21] has joined #lnd 01:23 -!- pioklo [~Pioklo@118-40.echostar.pl] has joined #lnd 01:34 -!- thomasan_ [~thomasand@2605:a601:b021:f00:a946:f6f5:403b:7e21] has quit [Remote host closed the connection] 01:37 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 01:51 < e4xit> also just wondering, are the DNS seeds down? 02:04 -!- kexkey [~kexkey@199.229.249.116] has quit [Ping timeout: 244 seconds] 02:18 -!- belcher [~belcher@unaffiliated/belcher] has joined #lnd 02:22 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 02:22 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 02:50 -!- pioklo [~Pioklo@118-40.echostar.pl] has quit [Quit: Leaving] 03:49 -!- libertyprime [~libertypr@101.98.42.91] has quit [Ping timeout: 268 seconds] 04:11 -!- takinbo [sid19838@gateway/web/irccloud.com/x-vyuvelisdlbcrdve] has quit [Quit: Connection closed for inactivity] 04:17 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has quit [Ping timeout: 256 seconds] 04:20 -!- dermoth [~dermoth@gateway/tor-sasl/dermoth] has joined #lnd 04:55 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Ping timeout: 272 seconds] 05:02 -!- Talkless [~Talkless@hst-227-49.splius.lt] has joined #lnd 05:26 -!- sh_smith [~sh_smith@cpe-76-174-26-91.socal.res.rr.com] has quit [Remote host closed the connection] 06:42 < lndbot> Hey all, I'm looking for some help with the following message when trying to open a new channel with a push amount. I'm trying to get the channel to be balanced right in the middle of its full capacity 06:43 < lndbot> ``` bitcoin@RaspiBolt:/home/pi $ lncli walletbalance { "total_balance": "1084672", "confirmed_balance": "1084672", "unconfirmed_balance": "0" } bitcoin@RaspiBolt:/home/pi $ lncli openchannel --node_key 03a8355790b89f4d96963019eb9413b9a2c884691837ac976bacfe25a5212892d7 --local_amt 420001 --push_amt 420000 [lncli] rpc error: code = Unknown desc = Funder balance too small (-2019000) with fee=2020 sat, minimum=1146 sat required ``` 06:43 < lndbot> It looks like I have enough on-chain funds. I'm not sure what the error message means 06:46 -!- drexl [~drexl@cpc130676-camd16-2-0-cust445.know.cable.virginm.net] has joined #lnd 06:57 -!- takinbo [uid19838@gateway/web/irccloud.com/x-qerinmpzwzsmzeoc] has joined #lnd 07:15 < Veggen> vinda.rd: push_amt is taken from the local amount. So local_amt is really total amt. 07:16 < Veggen> but, please remember: with push you give BTC to the other node 07:36 < lndbot> Ah that makes sense. Not sure why I hadn't thought of that. Thanks for the push heads up. That's exactly what I'm trying to do 09:32 -!- Dean_Guss [~dean@gateway/tor-sasl/deanguss] has quit [Ping timeout: 256 seconds] 10:27 -!- manantial [~tecnecio@92.58.58.54] has joined #lnd 10:27 -!- manantial [~tecnecio@92.58.58.54] has quit [Changing host] 10:27 -!- manantial [~tecnecio@unaffiliated/manantial] has joined #lnd 10:38 -!- gethh [uid264798@gateway/web/irccloud.com/x-qnqiebyaiffsbvmx] has quit [Quit: Connection closed for inactivity] 10:47 -!- deusexbeer [~deusexbee@080-250-075-168-dynamic-pool-adsl.wbt.ru] has joined #lnd 11:32 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #lnd 12:16 -!- thomasan_ [~thomasand@2605:a601:b021:f00:85ba:35dd:8aea:493c] has joined #lnd 12:18 -!- thomasan_ [~thomasand@2605:a601:b021:f00:85ba:35dd:8aea:493c] has quit [Remote host closed the connection] 12:37 -!- libertyprime [~libertypr@101.98.42.91] has joined #lnd 13:34 -!- libertyprime [~libertypr@101.98.42.91] has quit [Ping timeout: 240 seconds] 13:54 -!- Talkless [~Talkless@hst-227-49.splius.lt] has quit [Quit: Konversation terminated!] 14:06 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has joined #lnd 14:15 -!- manantial [~tecnecio@unaffiliated/manantial] has quit [Remote host closed the connection] 14:37 -!- ghost43 [~daer@gateway/tor-sasl/daer] has quit [Ping timeout: 256 seconds] 14:37 -!- ghost43 [~daer@gateway/tor-sasl/daer] has joined #lnd 15:13 -!- hex17or [~hex17or@HSI-KBW-091-089-197-016.hsi2.kabel-badenwuerttemberg.de] has joined #lnd 15:15 < hex17or> So what is the channel behavior during reboots or loss of internet - at times, I have to power cycle my modem to resolve some internet issues (thanks ISP!). What happens to open channels then? Are they force closed upon loss of internet to my node? Also, if my node happens to reboot, are the channels force closed? 15:16 < lndbot> Should be fine 15:16 < lndbot> Your peer can force close at any time though 15:18 < hex17or> Ok. I will be trying this on testnet shortly. Have a cloud node set up with a few open channels that should be confirmed shortly. I'll try rebooting the node and also taking it offline for sometime. 15:18 < hex17or> If it holds up then I can think of adding lnd to my local BTC full node as well. 15:19 < lndbot> Sounds good 15:19 < lndbot> If you aren’t planning on keeping high uptime, make your channels in private mode 15:20 < hex17or> Oh.. didn't know about that! let me read up on it. 15:21 -!- libertyprime [~libertypr@185.86.69.111.dynamic.snap.net.nz] has joined #lnd 15:24 < hex17or> SO private channels aren't announced to the network So in case my node has some downtime, 15:25 < hex17or> it essentially isn't broadcast to all 15:26 < lndbot> Right 15:26 -!- libertyprime [~libertypr@185.86.69.111.dynamic.snap.net.nz] has quit [Ping timeout: 250 seconds] 15:27 < Veggen> loss of internet, or some downtime for example for upgrades, shold be fine. 15:27 < Veggen> but of course you should try to run it 24/7. 15:28 < hex17or> Sure 24x7 is the goal. But I've seen that at times, I need to power cycle my modem due to network issues. But looks like that shoulnd't be much of an issue. 15:29 < Veggen> oh, no. of course, if you end up being down more than up, it could be an issue :) 15:29 < lndbot> Being offline sometimes doesn’t sound like a big problem to me 15:29 < Veggen> not safety-wise, but people might be tired of having channels with someone that is never there. 15:29 < molz> hex17or, one of the things that can make you lose your node, hence your channels and btc is if your hardware gets toasted 15:30 < hex17or> Just wondering if it is a matter of "lightning etiquette" to wait for a particular amount of time before acting upon an offline peer node/channel? 15:31 < hex17or> i.e. benefit of doubt that the peer node is undergoing some maintenance? 15:31 < molz> i'd give them two weeks 15:31 < Veggen> hex17or: well. Anyone is free to close a channel at any time, but personally I wait at least a week or two :) 15:32 < Veggen> maybe even a month. No issue with that. Timing can always be bad, you could have a power outage while on vacation, etc. 15:33 < hex17or> Veggen that's true. 15:33 < lndbot> If you’re a public node, being down for weeks isn’t great 15:33 < Veggen> alexbosworth: of course not. 15:33 < lndbot> Private nodes like mobile phones can be expected to be offline for weeks and months 15:35 < Veggen> hmmm. any github masters? I have a local diff with a PR of another person, anyway to create a PR to a PR or such? ;) 15:35 < hex17or> alexbosworth Yes, I noticed that with the Eclair mobile app; opened a channel b/w Eclair on mobile and a cloud node and I see that the mobile node is offline when my mobile is on standby. 15:35 < Veggen> added a comment and a patch as a file attachment, but if there's a better way... 15:36 < Veggen> (been improoving the letsencrypt-PR, now it works more seamlessly, by creating the old certificates as before) 15:39 -!- github-lnd [github-lnd@gateway/service/github.com/x-fjdogytfimrdpqhq] has joined #lnd 15:39 -github-lnd:#lnd- [lnd] dchirikov opened pull request #2542: Extended autocompletion in bash for lncli (master...bash_autocompletion) https://git.io/fh6Y2 15:39 -!- github-lnd [github-lnd@gateway/service/github.com/x-fjdogytfimrdpqhq] has left #lnd [] 15:39 -!- deusexbeer [~deusexbee@080-250-075-168-dynamic-pool-adsl.wbt.ru] has quit [Remote host closed the connection] 15:40 -!- melvster [~melvin@ip-86-49-18-190.net.upcbroadband.cz] has quit [Ping timeout: 244 seconds] 15:40 -!- deusexbeer [~deusexbee@080-250-075-168-dynamic-pool-adsl.wbt.ru] has joined #lnd 15:50 -!- pioklo [Pioklo@ip-91.246.70.194.skyware.pl] has quit [Ping timeout: 245 seconds] 15:52 -!- libertyprime [~libertypr@101.98.42.91] has joined #lnd 15:58 < hex17or> Also, just to confirm - since lnd v0.5-beta, dynamic IP issued by the ISP is no longer an issue thanks to the periodic polling in lnd to determine if the external IP has changed and to send an announce if yes? 16:03 < Veggen> hex17or: nat parameter works for some at least, I think :) 16:03 < Veggen> but not an issue? dunno, I'd not like it switching daily at least. Should be at least semi-stable. 16:06 < hex17or> yeah, I think my IP lease from my ISP renews every 2 to 3 days with a new external IP I guess 16:07 < hex17or> so this functionality would help keep my node in the network 16:07 < Veggen> ...even if you have active connections? 16:08 < hex17or> that's what I could make out from the release notes of v0.5-beta 16:08 < hex17or> unless I am mistaken? 16:09 < Veggen> mmm, don't run 0.5-beta. It's ancient. Run at least 0.5.1, 0.5.2 should be out soon :) 16:10 < molz> we have 0.5.2rc1 now 16:10 < Veggen> nat=1 would help, I guess. 16:10 < hex17or> yeah I am testing 0.5.1, but I guess this functionality was released with 0.5-beta :) 16:11 < hex17or> great to hear that 0.5.2 is around the corner! 16:18 < Veggen> well, night. 16:24 -!- hex17or [~hex17or@HSI-KBW-091-089-197-016.hsi2.kabel-badenwuerttemberg.de] has quit [Quit: leaving] 16:39 -!- qubenix [~qubenix@66.172.11.228] has quit [Quit: quit] 16:48 -!- qubenix [~qubenix@66.172.11.228] has joined #lnd 16:57 -!- github-lnd [github-lnd@gateway/service/github.com/x-ksodqcwspxnygefk] has joined #lnd 16:57 -github-lnd:#lnd- [lnd] alexbosworth opened pull request #2543: trivial: typo fix (master...patch-9) https://git.io/fh6se 16:57 -!- github-lnd [github-lnd@gateway/service/github.com/x-ksodqcwspxnygefk] has left #lnd [] 18:00 -!- libertyprime [~libertypr@101.98.42.91] has quit [Ping timeout: 240 seconds] 18:01 -!- libertyprime [~libertypr@101.98.42.91] has joined #lnd 18:23 -!- libertyprime [~libertypr@101.98.42.91] has quit [Ping timeout: 240 seconds] 18:34 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has joined #lnd 18:38 <@roasbeef> 0.5.2-beta-rc2 up nao 18:45 -!- thomasan_ [~thomasand@2605:a601:b021:f00:5de2:d000:3d52:b500] has joined #lnd 18:48 -!- thomasan_ [~thomasand@2605:a601:b021:f00:5de2:d000:3d52:b500] has quit [Remote host closed the connection] 18:48 <@roasbeef> also hit a 19hr btcd mainnet sync the other day 18:48 <@roasbeef> flame graphz ftw 18:48 <@roasbeef> still need to make som utxo cache tweaks, and pipeline blocks more, past 2016 or so cpu is idle just waiting for blocks to arrive 19:01 -!- libertyprime [~libertypr@101.98.42.91] has joined #lnd 19:02 -!- thomasan_ [~thomasand@136.52.18.22] has joined #lnd 19:07 -!- thomasan_ [~thomasand@136.52.18.22] has quit [Remote host closed the connection] 19:30 -!- botka [~nodebot@static.171.39.76.144.clients.your-server.de] has quit [Remote host closed the connection] 19:30 -!- botka [~nodebot@static.171.39.76.144.clients.your-server.de] has joined #lnd 20:00 -!- thomasan_ [~thomasand@136.52.18.22] has joined #lnd 20:04 -!- thomasan_ [~thomasand@136.52.18.22] has quit [Remote host closed the connection] 21:22 -!- libertyprime [~libertypr@101.98.42.91] has quit [Ping timeout: 250 seconds] 21:31 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Ping timeout: 256 seconds] 21:32 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lnd 21:47 -!- DeanGuss [~dean@gateway/tor-sasl/deanguss] has quit [Remote host closed the connection] 22:37 -!- grubles [~grubles@unaffiliated/grubles] has quit [Remote host closed the connection] 23:12 -!- libertyprime [~libertypr@101.98.42.91] has joined #lnd 23:39 -!- manantial [~tecnecio@unaffiliated/manantial] has joined #lnd 23:43 -!- gethh [uid264798@gateway/web/irccloud.com/x-nidrsppbopskqrhe] has joined #lnd