--- Log opened Thu Apr 11 00:00:41 2019
03:51 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
04:04 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
04:23 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
08:28 < m-schmoock> cdecker: jup, will fix the breaking tests. other than that, okay? I do not know a lot about fee and channel reserve calculation (other than dustlimit * 2). Is it possible that 10k sat is a bad minimal value in the near future du to rising fees? or is 10k a reasonable value?
08:32 < m-schmoock> Also I noted that the limit applies not only for incoming channels, as there is always a second channel in the other direction. So setting a value of 10k will prevent both, incoming and outgoing channels to this value. When I as a node initiate a channel with less than the minimal value, the other channel in the other direction to me will also have too litle funds and hence the operation will 
08:32 < m-schmoock> fail. I think this is correct, as channels are always in both directions
08:33 < m-schmoock> there could be an if-statement that will allow this, if the opening was initated by me, but it is not there yet. what do you think?
08:35 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning
08:38 <@cdecker> Nah, let's keep it simple. I think the 10k limit is ok, but want others to pitch in as well, that's why I haven't ack'd it yet
08:39 < m-schmoock> kk. postet the questsion on github so this does not get lost...
09:04 -!- stadicus [~stadicus@dhclient-91-190-22-198.flashcable.ch] has joined #c-lightning
12:39 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
12:46 -!- ArmadilloMan_ [808a41b8@gateway/web/freenode/ip.128.138.65.184] has joined #c-lightning
12:55 -!- ArmadilloMan_ [808a41b8@gateway/web/freenode/ip.128.138.65.184] has quit [Ping timeout: 256 seconds]
12:58 -!- stadicus [~stadicus@dhclient-91-190-22-198.flashcable.ch] has quit [Ping timeout: 268 seconds]
13:13 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]
13:33 < m-schmoock> cdecker: addressed that broken test... im done here for the time being ;) going on to the channel_accept hook again
14:13 -!- khs9ne [~xxwa@unaffiliated/mn3monic] has joined #c-lightning
15:13 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-hzkyddkvwyqesimc] has left #c-lightning []
15:15 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-hzkyddkvwyqesimc] has joined #c-lightning
15:22 -!- spinza [~spin@155.93.246.187] has quit [Quit: Coyote finally caught up with me...]
15:24 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 250 seconds]
15:34 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-hzkyddkvwyqesimc] has quit [Remote host closed the connection]
15:35 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-vejiwpsbnzlvovxp] has joined #c-lightning
16:10 -!- spinza [~spin@155.93.246.187] has joined #c-lightning
16:21 -!- Netsplit *.net <-> *.split quits: gwillen, jasonzhouu, harding
16:27 < ctrlbreak> Cool... just discovered a 58GB debug log file... as a bunch of nonesense was rapidly repeating.  Oy.
16:28 -!- Netsplit over, joins: harding, gwillen, jasonzhouu
16:57 < ctrlbreak> Anyone have any idea what was happening here?  Over 1 million incrementing commitsigs just rolling through and chewing GBs of logs on my node.   https://pastebin.com/raw/H1pW0sXV
19:13 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has joined #c-lightning
19:17 -!- EagleTM [~EagleTM@unaffiliated/eagletm] has quit [Ping timeout: 252 seconds]
20:28 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
--- Log closed Fri Apr 12 00:00:42 2019