--- Day changed Sun Jun 17 2018 00:59 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 264 seconds] 01:00 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has quit [Ping timeout: 240 seconds] 01:03 -!- StopAndDecrypt [~StopAndDe@c-73-215-253-208.hsd1.nj.comcast.net] has joined #c-lightning 01:03 -!- StopAndDecrypt [~StopAndDe@c-73-215-253-208.hsd1.nj.comcast.net] has quit [Changing host] 01:03 -!- StopAndDecrypt [~StopAndDe@unaffiliated/stopanddecrypt] has joined #c-lightning 01:18 -!- jojeyh [~delphi@2602:306:b8b6:b970:30d8:d7c2:d20:7f35] has joined #c-lightning 02:43 -!- Victor_sueca is now known as Victorsueca 02:51 -!- tiagotrs [~user@p3EE2DA15.dip0.t-ipconnect.de] has joined #c-lightning 02:51 -!- tiagotrs [~user@p3EE2DA15.dip0.t-ipconnect.de] has quit [Changing host] 02:51 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 03:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 03:15 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 256 seconds] 03:17 -githubby:#c-lightning- [lightning] rustyrussell opened pull request #1595: Bolt updates (no code changes) (master...bolt-updates) https://git.io/vhMl5 03:25 -!- miner-joe [3ecabfb7@gateway/web/freenode/ip.62.202.191.183] has joined #c-lightning 04:45 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:44 -!- tiagotrs [~user@p3EE2D3F5.dip0.t-ipconnect.de] has joined #c-lightning 05:44 -!- tiagotrs [~user@p3EE2D3F5.dip0.t-ipconnect.de] has quit [Changing host] 05:44 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 05:55 -!- fusion45 [~fusion44@31.6.9.47] has joined #c-lightning 06:45 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 06:46 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 09:13 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:15 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 09:28 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…] 09:29 -!- contrapumpkin [~copumpkin@haskell/developer/copumpkin] has joined #c-lightning 09:31 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 248 seconds] 09:39 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 10:27 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Remote host closed the connection] 10:27 -!- CubicEarths [~cubiceart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 10:41 -!- kabaum [~kabaum@94.234.32.159] has joined #c-lightning 10:53 -!- tiagotrs [~user@p3EE2D131.dip0.t-ipconnect.de] has joined #c-lightning 10:53 -!- tiagotrs [~user@p3EE2D131.dip0.t-ipconnect.de] has quit [Changing host] 10:53 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 11:29 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 264 seconds] 11:58 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 11:59 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 12:02 -!- _mr_e [488bcd0c@gateway/web/freenode/ip.72.139.205.12] has joined #c-lightning 12:07 -!- _mr_e [488bcd0c@gateway/web/freenode/ip.72.139.205.12] has quit [Ping timeout: 260 seconds] 12:15 -!- fusion45 [~fusion44@31.6.9.47] has quit [Quit: Leaving.] 12:40 -!- _mr_e [488bc96c@gateway/web/freenode/ip.72.139.201.108] has joined #c-lightning 12:40 -!- kabaum [~kabaum@94.234.32.159] has quit [Read error: Connection reset by peer] 12:40 < _mr_e> Hello, I've been trying to set up a node for receiving lightning payments. I set up a docker node using: https://github.com/ElementsProject/lightning-charge. I funded and opened 3 channels, one being the asinq node. I've been able to successfully send a lightning payment to starblocks, however anytime i try to pay an invoice TO my node I am unable to find any routes. What could be wrong? 12:44 < grubles> are you on testnet or mainnet 12:45 < grubles> starblocks is a fake demo site on testnet 12:45 < grubles> oh wait. sorry i misread. 12:51 -!- tiagotrs [~user@unaffiliated/tiagotrs] has joined #c-lightning 13:05 < _mr_e> testnet 13:05 < _mr_e> my payment to starblocks was successful 13:06 < _mr_e> the problem is when I try to pay my own nodes invoice 13:06 < _mr_e> I tried to pay my node from my own node and it gets a routing error 13:06 < _mr_e> i also tried to pay it from exclair android wallet 13:06 < _mr_e> i was able to pay starblocks both from my node and from my eclair wallet 13:51 -!- _mr_e [488bc96c@gateway/web/freenode/ip.72.139.201.108] has quit [Ping timeout: 260 seconds] 13:53 -!- miner-joe [3ecabfb7@gateway/web/freenode/ip.62.202.191.183] has quit [Quit: Page closed] 14:38 < molz> you can't pay yourself 14:39 < molz> oh he's gone 14:39 < rusty> Probably no incoming capacity, if he made all the channels from the destination. 14:40 < molz> rusty, there's still some issue with c-lightning related to 'data loss protection' ? 14:42 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 14:42 < rusty> molz: the "android lightning wallet" (or whatever name it is) requires the data loss protection feature to establish a channel, which won't be in c-lightning until 0.6.1 14:42 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 14:43 < molz> oh .. ok 14:48 -!- Drolmer [~Drolmer@unaffiliated/drolmer] has joined #c-lightning 15:10 < blockstream_bot> [Chang Li, Blockstream] hi guys, i set up a lightning node a while ago and openned 208 channels, today i only have 108 channels... not sure if the channels were closed manually by the counter party or if i didnt something wrong 15:10 < blockstream_bot> [Chang Li, Blockstream] this is on mainnet 15:13 < molz> your node probably closed out channels with LND nodes due to disagreement in fees 15:13 < blockstream_bot> [Chang Li, Blockstream] i didnt change fee setting 15:14 < blockstream_bot> [Chang Li, Blockstream] it was default value 15:15 < blockstream_bot> [Chang Li, Blockstream] my node is called First Block Capital on the mainnet 15:19 < molz> it's from the code 15:20 < blockstream_bot> [Daniel Williams, Blockstream] yes there was a brief large influx of transactions that caused fees to temporarily rise, and cause channels to close 15:20 < blockstream_bot> [Chang Li, Blockstream] Ah i see, good to knwo! 15:23 < blockstream_bot> [Chang Li, Blockstream] I also saw there is an updated version of lightnig now, but not sure if its possible to just install the upgrade on top of the current node or do i need to setup the newer version from the scratch 15:24 < blockstream_bot> [Chang Li, Blockstream] sorry for the noob questions 15:24 < blockstream_bot> [Chang Li, Blockstream] and thanks guys! 15:25 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 248 seconds] 15:27 < blockstream_bot> [Daniel Williams, Blockstream] no you should just be able to `git pull` and then `make` 15:27 < blockstream_bot> [Daniel Williams, Blockstream] might have to run `./configure` prior to `make` i think 15:28 < blockstream_bot> [Chang Li, Blockstream] Thanks Daniel! 15:29 < blockstream_bot> [Daniel Williams, Blockstream] no problem! 15:31 < blockstream_bot> [Daniel Williams, Blockstream] also, for those on IRC: we have a Blockstream Slack instance up now. head here for an invite: http://blockstream.herokuapp.com/ 15:39 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-lpqjmyesfpjeissi] has joined #c-lightning 16:08 < ctrlbreak> Is this normal? 16:08 < ctrlbreak> 2018-06-17T23:07:55.453Z lightning_gossipd(19216): Compacting gossip_store with 18221 entries, 18446744073709551612 of which are stale 16:08 < ctrlbreak> 2018-06-17T23:07:55.454Z lightning_gossipd(19216): Compaction completed: dropped 1 messages, new count 18220 16:08 < ctrlbreak> over and over... etc. 16:09 -!- tiagotrs [~user@unaffiliated/tiagotrs] has quit [Ping timeout: 256 seconds] 17:11 -!- _mr_e [63e63289@gateway/web/freenode/ip.99.230.50.137] has joined #c-lightning 17:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 17:55 -!- Drolmer [~Drolmer@unaffiliated/drolmer] has quit [Quit: Leaving] 18:07 < _mr_e> hi, i can't seem to be able to access the logs of this chat. Did anyone respond to my question previously? 18:08 -!- deusexbeer [~deusexbee@095-129-169-151-dynamic-pool-adsl.wbt.ru] has joined #c-lightning 18:17 < rusty> _mr_e: Sorry, yes, no logs yet :( Here are the responses which matter: 18:17 < rusty> (07:08:36) molz: you can't pay yourself 18:17 < rusty> (07:09:01) rusty: Probably no incoming capacity, if he made all the channels from the destination. 18:41 < _mr_e> ok so I can't pay myself 18:42 < _mr_e> but, I have been trying to pay from eclair wallet, to my node 18:43 < _mr_e> I am connected to three nodes, one of which is the acinq node 18:43 < _mr_e> my android eclair wallet has a channel with acinq, and my node has a channel with acinq 18:43 < _mr_e> my node is up on kubernetes 18:44 < _mr_e> could it be some kind of firewall issue 18:44 < _mr_e> node has three channels open, all well connected nodes 18:49 -!- meshcollider [uid246294@gateway/web/irccloud.com/x-lpqjmyesfpjeissi] has quit [Quit: Connection closed for inactivity] 18:54 < _mr_e> so what is the best way to make sure you can receive payments on testnet 18:54 < _mr_e> are their any documents you can point me to? 18:54 < _mr_e> is this maybe easier to test on livenet? 18:56 < rusty> If channels are funded and have enough confirms, you should be able to pay; can't be a firewall issue. 18:57 < rusty> _mr_e: give me your node id and address, and I'll try to create a channel and send a payment from my testnet node? 18:59 < _mr_e> have you used kubernetes before? 18:59 < rusty> _mr_e: nope! 18:59 < _mr_e> so because my node is on kubernetes, it doesn't really have a public exposed ip address 18:59 < _mr_e> as of now, i have to make the connection 18:59 < _mr_e> but 18:59 < _mr_e> i can expose 18:59 < rusty> _mr_e: then nobody will be able to create a channel to you, so you'll have no incoming capacity. 19:00 < _mr_e> so the only way to receive is for someone else to connect to you 19:00 < _mr_e> i can't receive through the channel I opened to them? 19:00 < rusty> _mr_e: unless you manually push funds out, yes. 19:01 < rusty> _mr_e: for now, yes. We use a simple model where the person connecting funds the channel, so they hold all the money initially. 19:01 < _mr_e> so how would a service like satoshis place, or an exchange, or even a regular user begin accepting lightning payments? 19:02 < _mr_e> you have to first go out and find people to create an outgoing connection to you? 19:03 < _mr_e> so I set up node using: https://github.com/ElementsProject/lightning-charge 19:04 < _mr_e> i have 9112 exposed on a load balancer ip 19:04 < _mr_e> what would I need to expose so that you can connect to me? 19:06 < rusty> _mr_e: OK, so ideally you advertise that address, using 'announce-addr=load-balancer-ip:9112' in your .lightningd/config or '--announce-addr=load-balancer-ip:9112' on the cmdline. 19:06 < rusty> (obv, subsitute that floating IP for load-balancer-ip here :) 19:06 < rusty> And restart. Your node announcement will float out into the network, and we should all see it soon. 19:08 < _mr_e> is there an environment variable? 19:09 < rusty> _mr_e: um, not that I know of, unless charge does some magic? 19:12 < rusty> but creating a config file is pretty easy, once you find the lightning directory... 19:15 < _mr_e> so 9112 is the charged port, what is the port for clightning? 19:15 < _mr_e> or can i choose any with that arg 19:16 < _mr_e> is it 9735 19:16 < rusty> _mr_e: default is 9735, yes. In that case, you can jsut use announce-addr=load-balancer-ip 19:21 < _mr_e> ok, can you see my node @ 35.188.149.80 19:21 < rusty> _mr_e: what is your node id? 19:23 < rusty> _mr_e: But no, I get connection refused on port 9735 on that IP address. 19:23 < _mr_e> 02ac05912f89e43b88de3472e8c3003bdc91d8af1eb7ad95f1e675f0b6a626b98c 19:29 < rusty> _mr_e: thanks, but that port is not open. 19:30 < _mr_e> hmm, i wonder if this docker image doesn't actually have lightningd running.... 19:30 < _mr_e> which is strange, it's seems it's whole purpose is for accepting payments... 19:35 < _mr_e> i have the env var set: 19:35 < _mr_e> - name: LN_PATH value: /data/lightning 19:35 < _mr_e> so inside /data/lightning I should have a file named "config" 19:35 < _mr_e> with "announce-addr=load-balancer-ip" 19:36 < _mr_e> "announce-addr=35.188.149.80" 19:36 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 245 seconds] 19:38 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 19:38 < rusty> _mr_e: seems like, but do double check, it should have files like this in it: gossip_store lightning-rpc lightningd.sqlite3 hsm_secret 19:39 < _mr_e> yes it does 19:39 < rusty> _mr_e: Right,that's the one then! 19:40 < _mr_e> lightning 17 Jun 2018, 22:35:59 2018-06-18T02:35:59.579Z lightning-client Lightning client connected lightning 17 Jun 2018, 22:35:59 HTTP server running on 0.0.0.0:9112 lightning 17 Jun 2018, 22:35:58 2018-06-18T02:35:58.940Z lightning-client Connecting to /data/lightning/lightning-rpc lightning 17 Jun 2018, 22:35:58 2018-06-18T02:35:58.631Z lightning-client Lightning client connected lightning 17 Jun 2018, 22:35:58 2018-06-18T02: 19:40 < rusty> Mind you, that won't fix the problem of plumbing that port through... 19:40 < _mr_e> port is exposed 19:45 < _mr_e> Does anything stand out in how this docker image is starting lightningd? 19:45 < _mr_e> https://github.com/ElementsProject/lightning-charge/blob/master/bin/docker-entrypoint.sh 20:21 < rusty> _mr_e: hmm, still connection refused from that port. And nothing in there suppresses listening. Are there firewall rules somewhere? 20:27 < _mr_e> no, it should be wide open:( 20:27 < _mr_e> tcp? 20:31 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 20:32 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 20:44 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 21:01 < _mr_e> i can access charged at 9112 no problem 21:01 < _mr_e> it's the same load balancer exposing both ports 21:19 < _mr_e> can you see it now? 21:25 < molz> you can scan your port to see if it's open 21:31 < _mr_e> i just tried an nmap 21:32 < _mr_e> it showed no open ports 21:32 < _mr_e> which is impossible because I absolutely can communicate with 9112 21:40 < _mr_e> did a specific port scan, says 9112 is open and 9735 is closed... unbelievable 21:40 < _mr_e> i've checked everything, both are literally opened the exact same way 21:43 < _mr_e> I've noticed in my listpeers that all three nodes I'm connected to have 21:43 < _mr_e> "their_channel_reserve_satoshis": 0, 21:43 < _mr_e> this must be why i can't receive? 21:43 < _mr_e> does anybody have a node with funds that I can try to connect to instead? 21:47 < _mr_e> is it possible lightningd is bound to localhost and not 0.0.0.0 21:47 < _mr_e> is there a flag to set this? 21:57 < rusty> _mr_e: Gah, sorry. You'll need bind-address= too... which is a magic address which means bind to IPv4 and v6. 21:58 < rusty> _mr_e: I *forgot* that announce-address disables the automatic binding :( 21:58 < rusty> ie. 'bind-address=' in that config file. 21:58 * rusty is an idiot... 22:05 < _mr_e> ahhhh 22:05 < _mr_e> haha 22:05 < _mr_e> so just bind-address= 22:06 < _mr_e> not bind-address=0.0.0.0 22:06 < _mr_e> ? 22:06 < rusty> Well, 0.0.0.0 means IPv4 only, which may be fine for you 22:07 < _mr_e> ok 22:07 < _mr_e> so if i try to connect to your node and you have funds will it work? 22:07 < _mr_e> or do you have to connect to me? 22:07 < rusty> _mr_e: I have to fund a channel to you... 22:08 < _mr_e> is that going to be something fixable in future updates? that seems fairly awkward 22:08 < rusty> Connecting now... well, it didn't immediately die this time! 22:08 < _mr_e> no hold on 22:08 < _mr_e> the ip has changed 22:08 < _mr_e> i'm setting that config now 22:08 < rusty> Ah! 22:10 < _mr_e> lightning config file line 4: bind-address=: unrecognized option 22:12 < rusty> s/address/addr/ 22:12 < rusty> My bad... 22:12 < rusty> (THe documentation is correct, my multitasking isnt'!) 22:13 < _mr_e> where is the documentation on this? I don't see this stuff mentioned anywhere 22:13 < _mr_e> so it's bind-addr? 22:14 < rusty> Yep... 22:15 < rusty> _mr_e: man -l docs/lightningd-config.5 ? 22:15 < rusty> Or, if installed, maybe just 'man lightning-config' 22:15 < rusty> I mean man lightningd-config 22:17 < _mr_e> ok let's see: 35.184.56.193 22:18 < rusty> _mr_e: connected! OK, let me fund a channel 22:18 < _mr_e> w00h00 22:18 < rusty> _mr_e: txid a21baef868cce28fb009e42980db47a7e6614d459881a5eb6dc360f38c39b551 22:19 < rusty> _mr_e: of course, now we hope someone is mining on testnet! 22:20 < _mr_e> :) 22:20 < _mr_e> so I'm really surprised that I can't connect to a well connected node and begin receiving payments... is this something that will work in the future or is it a limitation of LN? 22:21 < rusty> _mr_e: Current limitation. 22:22 < rusty> _mr_e: for simplicity, person initiating channel pays all the funds. So there's no incoming capacity. 22:22 < rusty> Speaking of which, let me go on a starblocks binge... 23:02 -!- justan0theruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.0] 23:02 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning