--- Day changed Wed Aug 22 2018 00:04 -!- doml3_13333337 [~Drolmer@unaffiliated/drolmer] has joined #c-lightning 00:07 -!- DrOlmer [~Drolmer@unaffiliated/drolmer] has quit [Ping timeout: 244 seconds] 00:40 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection] 03:49 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-umziebdmhmgdqidu] has joined #c-lightning 03:49 < Lightblock_> hi everyone 03:50 < Lightblock_> how do you guys define the total capacity of some channel? Do we have to sum up the "satoshis" parameter which is returned in both json objects? 03:51 < Lightblock_> or just one "satoshis" parameter is relevant for the total channel capacity? a bit puzzled here 03:55 < blockstream_bot> [Christian Decker, Blockstream] The total channel capacity is the number of satoshis that funded the channel, i.e., the value field of the funding transaction's output 03:56 < blockstream_bot> [Christian Decker, Blockstream] That is however not the available capacity since that's encumbered by the reserve, which may not be identical on both sides, so there the story diverges a bit 03:58 < Lightblock_> yes, I understand, available capacity is something different, I guess to know the actual capacity you simply need to try sending the payment through this channel 03:59 < Lightblock_> I would rephrase my question a bit then, what does "satoshis" parameter stand for in c-lightning channel info json object? 04:50 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning 05:20 -!- meshcollider [meshcollid@gateway/shell/elitebnc/x-wgvbdtbctoyeevjj] has joined #c-lightning 06:20 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""] 06:22 -!- Lightblock_ [uid302821@gateway/web/irccloud.com/x-umziebdmhmgdqidu] has quit [Quit: Connection closed for inactivity] 07:20 -!- Guest11272 is now known as sturles 08:04 -!- DrOlmer [~Drolmer@unaffiliated/drolmer] has joined #c-lightning 08:07 -!- doml3_13333337 [~Drolmer@unaffiliated/drolmer] has quit [Ping timeout: 252 seconds] 08:38 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has joined #c-lightning 08:40 < Chris_Stewart_5> Why is the behavior here for c-lightning to disconnect the peer? 08:40 < Chris_Stewart_5> https://pastebin.com/EJn8ix8g 08:40 < Chris_Stewart_5> cdecker: ^ 09:12 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 09:13 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 09:33 -!- Zenton [~user@54.104.135.37.dynamic.jazztel.es] has quit [Ping timeout: 272 seconds] 10:10 -!- RubenSomsen [uid301948@gateway/web/irccloud.com/x-fxwvybykfobltvyt] has quit [Quit: Connection closed for inactivity] 10:52 < blockstream_bot> [Hugo Doyon, Blockstream] Is there anyone using spruned in mainnet? (1 month ago tried it and have some issues so I had to rollback. I am now planning to give a second try) 11:29 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has quit [Ping timeout: 240 seconds] 11:33 -!- CubicEarth [~CubicEart@c-73-181-185-197.hsd1.wa.comcast.net] has joined #c-lightning 12:50 -!- grubles [~grubles@unaffiliated/grubles] has quit [Quit: Leaving] 13:31 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 13:56 -!- farmerwampum [~farmerwam@104.129.28.10] has joined #c-lightning 13:59 -!- farmerwampum_ [~farmerwam@104.129.28.10] has quit [Ping timeout: 276 seconds] 13:59 -!- farmerwampum [~farmerwam@104.129.28.10] has quit [Client Quit] 14:00 -!- farmerwampum [~farmerwam@104.129.28.10] has joined #c-lightning 14:08 -!- grafcaps [~haroldbr@104.137.194.255] has joined #c-lightning 14:09 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 14:10 <@cdecker> Chris_Stewart_5: we prefer to disconnect too often rather than trying to recover, but you're right, in this case there is little reason to 14:10 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 14:10 <@cdecker> Hugo: yes, I'm using spruned, but I had to hack it a bit to return the same error codes that bitcoind does, otherwise we have some funny bugs 14:11 <@cdecker> I'll try to bundle them up and submit them upstream 14:18 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 14:19 -!- Chris_Stewart_5 [~chris@unaffiliated/chris-stewart-5/x-3612383] has quit [Ping timeout: 252 seconds] 14:34 -!- DrOlmer [~Drolmer@unaffiliated/drolmer] has quit [Ping timeout: 240 seconds] 14:48 -!- DrOlmer [~Drolmer@unaffiliated/drolmer] has joined #c-lightning 14:59 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection] 15:15 < blockstream_bot> [Hugo Doyon, Blockstream] Excellent Christian! I will keep an eyes on spruned repo 15:17 < blockstream_bot> [Hugo Doyon, Blockstream] FYI I found this tutorial for sPRUNED mode : https://gist.github.com/Stadicus/a05c3c5ac6a63cdcfe1aae2b77f17cba 15:19 < blockstream_bot> [Hugo Doyon, Blockstream] sPruned will drop cost of operation of a node operator by 50 % at least 15:25 < blockstream_bot> [Hugo Doyon, Blockstream] or dramatically increase scaling throughput depending of the standpoint 16:05 -!- grubles [~grubles@unaffiliated/grubles] has joined #c-lightning 16:05 -!- doml3_13333337 [~Drolmer@unaffiliated/drolmer] has joined #c-lightning 16:07 -!- grubles [~grubles@unaffiliated/grubles] has quit [Client Quit] 16:08 -!- DrOlmer [~Drolmer@unaffiliated/drolmer] has quit [Ping timeout: 264 seconds] 16:09 -!- grubles [~grubles@gateway/tor-sasl/grubles] has joined #c-lightning 16:12 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 16:14 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 16:17 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 16:56 -!- grafcaps [~haroldbr@104.137.194.255] has quit [Ping timeout: 265 seconds] 16:58 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning 17:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 17:22 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 17:59 -!- Zenton [~user@54.104.135.37.dynamic.jazztel.es] has joined #c-lightning 18:20 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Read error: Connection reset by peer] 19:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning 19:33 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning 19:37 -!- keymone [~keymone@ip1f13761c.dynamic.kabel-deutschland.de] has joined #c-lightning 20:08 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer] 20:09 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.1] 20:09 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning 20:31 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has quit [Ping timeout: 272 seconds] 21:43 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning 22:11 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 240 seconds] 23:51 -!- jonasschnelli_ [~jonasschn@unaffiliated/jonasschnelli] has joined #c-lightning 23:52 -!- jonasschnelli_ is now known as jonasschnelli