--- Log opened Fri Aug 06 00:00:30 2021
00:21 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has joined #c-lightning
00:39 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 258 seconds]
03:53 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
04:39 -!- k3tan [~pi@user/k3tan] has quit [Ping timeout: 272 seconds]
04:41 -!- k3tan [~pi@user/k3tan] has joined #c-lightning
07:52 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed]
07:52 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
08:29 -!- nathanael [~nathanael@user/nathanael] has quit [Quit: connection reset by purr]
08:29 -!- nathanael [~nathanael@user/nathanael] has joined #c-lightning
09:41 -!- early [~early@static.38.6.217.95.clients.your-server.de] has quit [Quit: Leaving]
09:42 -!- early [~early@static.38.6.217.95.clients.your-server.de] has joined #c-lightning
09:53 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed]
10:32 -!- guy69 [~guy69@bras-base-toroon474qw-grc-87-174-93-72-251.dsl.bell.ca] has joined #c-lightning
10:32 < guy69> Hi all. I'm setting up a c-lightning node for first time... not getting too far
10:32 < guy69> I am on the net; see peers, can connect to them
10:33 < guy69> and I paid 1ML for a channel, which has at least 1 or 2 btc confirmations
10:33 < guy69> but "The total incoming capacity is still insufficient even if the payer had MPP capability."
10:33 < guy69> hints?
10:36 < mschmoock> guy69: default setting for a channel to be active (unless otherwise configured) is 6 confirmations
10:37 < mschmoock> you can set that in your   ~/.lightning/config    via i.e.   funding-confirms=2
10:37 < guy69> getinfo says I have an "num_active_channels" tho
10:37 < mschmoock> its active but not yet in CHANNELD_NORMAL state
10:37 < mschmoock> which it will be after 6 confirms
10:38 < guy69> ok, makes sense
10:38 < mschmoock> you can set that lower value and restart lightningd  ;)
10:38 < guy69> is there a command to look at my own channels, not the world's like "listchannels"
10:38 < mschmoock> keep in mind  funding-confirms=2  is a rather low value
10:38 < mschmoock> guy69:     lightning-cli listpeers
10:39 < mschmoock> or install the "summary" plugin which has a decent overview   https://github.com/lightningd/plugins/tree/master/summary 
10:39 < guy69> cool, I had done that a few times before making the channel. It's shown there w/ status "CHANNELD_NORMAL"
10:40 < mschmoock> hm, than you should be able to use the channel
10:40 < guy69> rgiht. must have gotten some confirmations during our chat
10:40 < mschmoock> maybe the payers gossipn still needs to be synced to that new channel
10:41 < mschmoock> so it actually knows you have a channel that is big enough, otherwise some error like this may happen
10:41 < mschmoock> give it a coupl of minutes, I believe 7 minutes per hop or so
10:41 < guy69> I ahve a mobile wallet here that I"m trying to send from, and it still says: not enough inbound capacity
10:42 < mschmoock> so if payer and receiver (new channel) are 4 hops away you need like 30 minutes
10:42 < mschmoock> guy69: on the mobile it says not enough inbound capacity but you want to send?  
10:43 < guy69> yes. mobile is separate walelt
10:43 < mschmoock> (if you want to send you need outbound liq on that mobile)
10:43 < mschmoock> which is why this message doesnt make sense
10:43 < guy69> it's some sort of hosted solution... "blue wallet"
10:43 < guy69> btw: my channel: 694505x2961x0
10:43 < mschmoock> but, assuming your sending from mobile, it may say that because it does not see big enough channels for the receiver,
10:44 < mschmoock> i cannot see that channel yet :D
10:44 < mschmoock> so wait a bit ...
10:44 < mschmoock> lnc listchannels 694505x2961x0
10:44 < mschmoock> { "channels": []
10:44 < mschmoock> }
10:44 < mschmoock> as said, 7 minutes per hop in the LN network topology
10:44 < mschmoock> (after funding confirms reached)
10:45 < mschmoock> thats just how channels are announced
10:45 < guy69> I will chill then.
10:45 < mschmoock> :D
10:45 < guy69> but, general question: I'm a merchant selling things... do I need to tell customers to mess with channels and such? or just show them an bolt12 invoice?
10:46 < mschmoock> just give them bolt11 qinvoice
10:46 < mschmoock> having inbound channels is your job
10:46 < guy69> so on the first day will they be fustrated?
10:46 < mschmoock> I can open a channel to you if you need
10:46 < mschmoock> guy69: nope
10:46 < mschmoock> you have channel open they can use
10:46 < mschmoock> they dont need to do special foo, just a LN wallet with a balance
10:47 < mschmoock> (which is the same for any monetary network)
10:48 < guy69> Let's see if I can do this right:    02ed622fe2a747c0148d5bebeacca54754b2881c4023a610477ac69d37408693bf@134.195.196.69:9735   ... I also have tor if you'd prefer
10:48 < mschmoock> i prefer without tor
10:49 < mschmoock> opened it :D
10:50 < guy69> Thanks! You must be 02a4aae2e021b0785f2f2a7c9dc9089361995085298598992bf69f11302a5dbd2c
10:50 < mschmoock> i have enough liquidity so your clients will be fine I guess
10:50 < mschmoock> guy69: psst ;)
10:51 < mschmoock> no problem
10:51 < mschmoock> gotta go, just ask if you have further questions I read later
10:51 < guy69> Should I include that on my checkout page? (the pubkey / ip / port) thing
10:51 < guy69> Thanks for you help!! TTYL
10:52 < mschmoock> guy69: hm, some ppl do. can help if your low in liquidity so user open new channels to you, but I dound anyone will so you can leave it and care for liquidity on yorself
10:52 < mschmoock> *doubt
10:53 < mschmoock> thing is, if your node gets older, your liqidity grows
10:53 < mschmoock> if you spend your LN liquidity without closeing the channel, you get even more inbound liquidity with the channels you already have
10:53 < guy69> maybe I'll just put the links in the blog post announcing lightning and grow from there... as a merchant, selling BTC products, I'm sure liquidity won't be an issue long term
10:53 < mschmoock> manageable. just dont close and setup a new new, then you will restart at 0
10:54 < mschmoock> cu l8er
10:54 < guy69> thx again
11:18 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
15:59 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Client closed]
16:07 -!- jonatack [~jonatack@user/jonatack] has joined #c-lightning
16:08 -!- guy69 [~guy69@bras-base-toroon474qw-grc-87-174-93-72-251.dsl.bell.ca] has quit [Quit: Client closed]
16:18 -!- lxer [~lx@ip5f5bf666.dynamic.kabel-deutschland.de] has quit [Ping timeout: 245 seconds]
16:28 -!- openoms_ [~quassel@gateway/tor-sasl/openoms] has joined #c-lightning
16:28 -!- openoms [~quassel@gateway/tor-sasl/openoms] has quit [Ping timeout: 244 seconds]
18:01 -!- aechu [~major@gateway/tor-sasl/major] has quit [Ping timeout: 244 seconds]
18:03 -!- aechu [~major@gateway/tor-sasl/major] has joined #c-lightning
18:39 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
19:00 -!- rusty [~rusty@103.93.169.121] has quit [Quit: Leaving.]
19:00 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
19:06 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 250 seconds]
19:44 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
19:44 -!- belcher_ [~belcher@user/belcher] has joined #c-lightning
19:48 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 258 seconds]
20:16 -!- jonatack [~jonatack@user/jonatack] has quit [Ping timeout: 246 seconds]
21:19 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
21:52 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 256 seconds]
22:02 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
22:43 -!- rusty [~rusty@103.93.169.121] has quit [Read error: No route to host]
22:44 -!- rusty [~rusty@103.93.169.121] has joined #c-lightning
23:34 -!- rusty [~rusty@103.93.169.121] has quit [Ping timeout: 258 seconds]
--- Log closed Sat Aug 07 00:00:31 2021