--- Log opened Thu Oct 11 00:00:33 2018
00:28 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has joined #c-lightning
01:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
02:56 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 244 seconds]
02:57 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
04:05 -!- reallll [~belcher@unaffiliated/belcher] has joined #c-lightning
04:08 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 245 seconds]
04:44 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has joined #c-lightning
06:02 <@cdecker> jb55, molz: the scratch_txid is used for a number of use-cases (unilateral close, sweeps, collaborative closes), but for active channels it'll show the txid of the latest commit transaction
06:11 < molz> cdecker, i just closed a few channels on my testnet node, for co-op closing it shows a different TXID than the scratch ID, but for force-closing it shows the scratch ID
06:14 < molz> cdecker, im just curious what's the purpose to have the scratch_id, how useful is it, it's kinda confusing (for newbies im sure) to see all the "ids" from "listpeers" 
07:15 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
07:41 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
08:02 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has joined #c-lightning
08:20 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has quit [Quit: Leaving]
08:32 -!- antanst [~antanst@62.169.219.213] has quit [Quit: ZNC 1.7.1 - https://znc.in]
08:32 -!- antanst [~antanst@62.169.219.213] has joined #c-lightning
09:36 -!- reallll is now known as belcher
09:59 <@cdecker> It's mainly intended as a debugging help so we can better identify the resolutions and better help users
10:14 < molz> cdecker, ok i just noticed it seems my c-lightning node just force closed a channel and I can find the closing tx right away by using the scratch_id
10:14 < molz>           "status": [
10:14 < molz>             "CHANNELD_NORMAL:update_fee 22477 outside range 253-12690",
10:14 < molz>             "ONCHAIN:Tracking our own unilateral close",
10:14 < molz>             "ONCHAIN:All outputs resolved: waiting 75 more blocks before forgetting channel"
10:43 < molz> is there a command to close all channels?
11:03 -!- booyah_ [~bb@193.25.1.157] has joined #c-lightning
11:03 -!- booyah [~bb@193.25.1.157] has quit [Read error: Connection reset by peer]
11:53 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 250 seconds]
11:58 -!- booyah_ is now known as booyah
12:59 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
13:07 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
13:08 -!- michaelsdunn1 [~michaelsd@unaffiliated/michaelsdunn1] has quit [Remote host closed the connection]
13:08 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
13:09 -!- kexkey [~kexkey@173.209.53.188] has joined #c-lightning
13:28 -!- kexkey [~kexkey@173.209.53.188] has quit [Ping timeout: 250 seconds]
14:12 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]
14:13 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
14:17 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 246 seconds]
17:10 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
18:00 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
18:01 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
18:18 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
18:18 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
19:31 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 244 seconds]
19:39 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
20:08 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 252 seconds]
20:42 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
21:05 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-ltpznmxuggwqiery] has quit [Ping timeout: 244 seconds]
21:05 -!- blockstream_bot [blockstrea@gateway/shell/sameroom/x-giqiwofmcgvcwxpn] has joined #c-lightning
21:06 -!- Jbaczuk [~Jbaczuk@ec2-18-237-204-133.us-west-2.compute.amazonaws.com] has quit [Ping timeout: 244 seconds]
21:07 -!- Jbaczuk [~Jbaczuk@ec2-18-237-204-133.us-west-2.compute.amazonaws.com] has joined #c-lightning
21:38 -!- Amperture [~amp@24.136.5.183] has quit [Remote host closed the connection]
21:38 -!- Amperture [~amp@24.136.5.183] has joined #c-lightning
23:44 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 252 seconds]
--- Log closed Fri Oct 12 00:00:34 2018