--- Log opened Fri May 29 00:00:36 2020
00:44 -!- lxer [~lx@ip5f5bf473.dynamic.kabel-deutschland.de] has joined #c-lightning
00:49 < lxer> How can I increase the "our_amount_msat" in a channel? fundchannel just returns "Peer already CHANNELD_NORMAL"   
01:07 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
01:12 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
01:21 -!- kristapsk_ is now known as kristapsk
01:33 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
01:33 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
01:44 < m-schmoock> In a python testcase for a plugin I have 4 nodes simple a circular setup with same amounts each channel and routing fees turned off. Now I try to circular route everything (receivable) in one chunk, I end up in a situation that my outgoing channel has exactly 9741msat too little capacity for the operation. Am I correct that this the commitment fee of the sender that still applies, and the 
01:44 < m-schmoock> "receivable amount" in the other direction doesnt apply for this fundee pays fees margin?
01:44 < m-schmoock> just trying to get my head around this
01:45 < m-schmoock> *founder
01:48 -!- rusty1 [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
01:49 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 272 seconds]
02:05 < m-schmoock> I think my assumption is correct. thanks for listening/reading, sometimes it helps to just write down the problem :D
02:17 -!- rusty1 [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
02:18 <@cdecker> lxer: you can only have one channel with each peer. This is to encourage peer diversity guarding against single points of failure. You can open a channel with some other node, and pay indirectly through a multi-hop route, or rebalance the channel you want to have more outgoing capacity on.
02:19 <@cdecker> m-schmoock: yes, that'd be the funder paying the on-chain fees, therefore keeping some funds on its end to ensure timely settlement
02:21 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds]
02:29 < darosior> lxer: and you increase your part of the amount in the channel by receiving payments through it :-) (Either you get paid or you use circular payments to increase your part in this channel while decreasing your part in another one. See drain or rebalance plugins)
02:31 < lxer> but If I get paid, I still don't know in what channel it will end up. 
02:31 < zmnscpxj_> correct
02:32 < zmnscpxj_> you can hint to the payer, though the payer is free to ignore hints
02:34 <@cdecker> What are you trying to achieve lxer? If you have other channels that can be used to receive funds, why would you want to have more outgoing capacity on that specific channel?
02:35 <@cdecker> Unless you are trying to send a larger payment than any single channel has capacity for (working on MPP sending atm, so that'll be easier in future)
02:41 < lxer> not trying anything in specific, just trying to balance my side of a channel. I assumed the best situation would be to have some funding on both sides, isn't that true?
02:41 < zmnscpxj_> jitrebalance should make that a non-issue most of the time
02:42 < zmnscpxj_> for some definition of "should"
03:02 <@cdecker> Yep, with jitrebalance and MPP sending/receiving the individual channel's capacity becomes way less important. The aggregate capacity across all channels will be used optimally, and individual channels become way less important for the correct operation of nodes.
03:03 < m-schmoock> cdecker: on the plugins repo on github, when you click on "details" of a travis check, one gets to the github travis overview page of the job not the travis link directly.  meaning here: https://github.com/lightningd/plugins/pull/118/checks?check_run_id=719876732    and not here: https://travis-ci.com/github/lightningd/plugins/builds/168721069 
03:03 < m-schmoock> this is a bit inconvinient,. and if I remember correctly we do this otherwise on the main cln repo
03:04 < m-schmoock> not sure if you can/want make this the same
03:04 < m-schmoock> CI nit ^^
03:06 <@cdecker> Yes, Travis-ci.org is migrating all open-source projects over to their enterprise platform travis-ci.com which seems to hook into github through actions rather than the old hook + commit_status. Sadly that added the interstitial page there, which I find rather inconvenient as well.
03:06 <@cdecker> Sadly there is no way to migrate back to travis-ci.org...
03:06 < m-schmoock> okay, now we know theres a reason for this stupid intermediate page ^^
03:09 <@cdecker> Sorry about that, it's the first repo I had the option and didn't know the implications :-(
03:09 <@cdecker> Even worse is that if travis-ci continues with the migration, then all repos will end up with that interstitial page
03:16 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
03:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
03:38 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Quit: Leaving]
04:03 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
04:04 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
04:06 < lxer> ok, so if I want to increase a channel balance, these would be the steps, right?  1. send BTC to the address  2. wait for lock in  3. open a random channel and fund it with the amount. 4. rebalance using the plugin (probably using multiple invoices, if the amount is more than funds on the other side)
04:08 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
04:31 -!- cltrbreak_MAD2 [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
04:31 -!- cltrbreak_MAD2 [~ctrlbreak@159.2.182.106] has joined #c-lightning
04:34 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
04:34 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
04:35 <@cdecker> The you can use the drain plugin to achieve a specific distribution without manually doing invoices + pay (it'll chunk the rebalancings efficiently)
04:36 <@cdecker> Presumably you do steps 1 through 3 anyway, since you don't want to depend on a single peer being available
04:36 <@cdecker> And then the capacity on that one channel is less important anyway
04:37 <@cdecker> (the desire to balance channels ahead of time is a red herring if you ask me: no point in balancing them until you know you're going to forward a payment, and then the jitrebalance plugin does its magic automatically, with all the information to perform optimally)
04:38 <@cdecker> Keeping channels balanced without the need for it is just a waste of fees if you ask me
04:48 -!- k3tan [~pi@unaffiliated/k3tan] has quit [Ping timeout: 260 seconds]
04:48 < lxer> ok. I'll think about it.  But still, there should be a user-friendly way to simply add some btc to an existing channel.
04:49 -!- k3tan [~pi@unaffiliated/k3tan] has joined #c-lightning
04:50 <@cdecker> That is no possible with the current protocol specification: once a channel is setup it's total capacity is set in stone
04:51 <@cdecker> Once we specify the splice-in and splice-out ideas we can close and reopen in a single tx with changing capacities, but that's a long way down the roadmap
06:35 < zmnscpxj> yes, lots of fiddly bits
06:47 <@cdecker> Yeah, felt like a really easy thing to do when I came up with splicing back in 2016, oh how times have changed :-)
06:47 <@cdecker> It just takes time to appreciate the complexity in these things 
06:47 < zmnscpxj> :)
07:30 -!- kexkey [~kexkey@37.120.205.235] has joined #c-lightning
07:38 -!- Amperture [~amp@65.79.129.113] has joined #c-lightning
08:12 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
08:51 -!- Amperture [~amp@65.79.129.113] has quit [Quit: Leaving]
09:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
09:24 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
09:24 -!- vasild_ is now known as vasild
09:24 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 246 seconds]
09:32 -!- b42 [~mmilata@b42.cz] has quit [Ping timeout: 244 seconds]
09:40 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
09:41 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
09:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
09:46 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
09:52 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
09:53 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has joined #c-lightning
09:54 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Ping timeout: 240 seconds]
09:54 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Ping timeout: 240 seconds]
09:55 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
09:55 -!- zmnscpxj [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Ping timeout: 240 seconds]
09:56 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
09:59 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Ping timeout: 240 seconds]
10:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Remote host closed the connection]
10:05 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
10:05 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
10:05 -!- vasild [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
10:08 -!- b42 [~mmilata@b42.cz] has joined #c-lightning
10:40 -!- asoltys [~root@s207-81-214-2.bc.hsia.telus.net] has joined #c-lightning
11:32 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
11:33 -!- kristapsk_ is now known as kristapsk
11:35 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Quit: WeeChat 2.7.1]
11:42 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
11:55 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
11:55 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
12:06 -!- cltrbreak_MAD2 [~ctrlbreak@159.2.182.106] has quit [Remote host closed the connection]
12:07 -!- cltrbreak_MAD2 [~ctrlbreak@159.2.182.106] has joined #c-lightning
12:15 -!- kristapsk_ [~KK@gateway/tor-sasl/kristapsk] has joined #c-lightning
12:15 -!- kristapsk [~KK@gateway/tor-sasl/kristapsk] has quit [Remote host closed the connection]
12:16 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
12:19 -!- kristapsk_ is now known as kristapsk
13:33 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has quit [Ping timeout: 258 seconds]
13:34 -!- harrigan [~harrigan@ptr-93-89-242-235.ip.airwire.ie] has joined #c-lightning
14:28 -!- zmnscpxj_ [~zmnscpxj@gateway/tor-sasl/zmnscpxj] has quit [Remote host closed the connection]
15:03 -!- lxer [~lx@ip5f5bf473.dynamic.kabel-deutschland.de] has quit [Ping timeout: 240 seconds]
15:33 -!- belcher [~belcher@unaffiliated/belcher] has quit [Quit: Leaving]
15:38 -!- belcher [~belcher@unaffiliated/belcher] has joined #c-lightning
16:10 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Remote host closed the connection]
16:16 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 256 seconds]
16:34 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
16:39 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
16:42 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
16:47 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 240 seconds]
18:01 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has left #c-lightning []
18:01 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-txhnryyccoeyadae] has joined #c-lightning
18:40 -!- gojiHmPFPN [~textual@c-73-47-220-190.hsd1.ma.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:44 -!- mdunnio [~mdunnio@208.59.170.5] has joined #c-lightning
18:48 -!- mdunnio [~mdunnio@208.59.170.5] has quit [Ping timeout: 256 seconds]
18:48 -!- gojiHmPFPN [~textual@c-73-47-220-190.hsd1.ma.comcast.net] has joined #c-lightning
19:13 -!- gojiHmPFPN [~textual@c-73-47-220-190.hsd1.ma.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
19:19 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
20:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
20:45 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
20:48 -!- gojiHmPFPN [~textual@c-73-47-220-190.hsd1.ma.comcast.net] has joined #c-lightning
21:15 -!- gojiHmPFPN [~textual@c-73-47-220-190.hsd1.ma.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
21:20 -!- vasild_ [~vd@gateway/tor-sasl/vasild] has joined #c-lightning
21:23 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Remote host closed the connection]
21:24 -!- vasild [~vd@gateway/tor-sasl/vasild] has quit [Ping timeout: 240 seconds]
21:24 -!- vasild_ is now known as vasild
23:07 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Ping timeout: 240 seconds]
23:10 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #c-lightning
23:46 -!- berndj [~berndj@azna.co.za] has quit [Quit: ZNC - http://znc.in]
23:47 -!- berndj [~berndj@azna.co.za] has joined #c-lightning
23:48 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has quit [Remote host closed the connection]
23:58 -!- mrostecki [~mrostecki@gateway/tor-sasl/mrostecki] has joined #c-lightning
--- Log closed Sat May 30 00:00:37 2020