--- Log opened Wed Oct 10 00:00:33 2018
00:07 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
00:35 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has joined #c-lightning
00:46 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 252 seconds]
02:17 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
03:23 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 252 seconds]
04:05 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
04:09 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 252 seconds]
04:59 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning
05:41 -!- farmerwampum [~farmerwam@88.202.178.98] has quit [Remote host closed the connection]
05:41 -!- bitdex [~bitdex@gateway/tor-sasl/bitdex] has quit [Quit: = ""]
05:52 -!- kabaum_ [~kabaum@h-13-35.A163.priv.bahnhof.se] has joined #c-lightning
07:38 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
07:39 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
08:19 -!- bitonic-cjp [~bitonic-c@a80-100-203-151.adsl.xs4all.nl] has quit [Quit: Leaving]
08:55 -!- RubenSomsen [sid301948@gateway/web/irccloud.com/x-otljjrrkatkedlpe] has joined #c-lightning
09:18 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection]
10:11 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
10:12 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
10:47 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning
11:03 -!- ebx [~ebx@unaffiliated/ebex] has joined #c-lightning
12:35 < molz> i just noticed now we have  "scratch_txid", what is it?
13:05 < jb55> molz: JSON API: `listpeers` has new field `scratch_txid`: the latest tx in channel.
13:10 < molz> jb55, i know that, but what is it?
13:18 < molz> they don't seem to exist, can't find on any explorers
13:18 < molz> "scratch_txid": "867d1b9365f133054359de38d28423f092d9a4c6e01c8c1e9682bc2ad1d0fb9f",
13:19 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
13:19 < molz> "scratch_txid": "c57ef2efb007fe4bfd58b099e3d269713122d87e95c356f08ba79e74d742c523",
13:20 < molz> "scratch_txid": "c03a196a708a56e11cb5e763af87878bb9b1f08b9f8546168b9650a35ac5d12a",
13:20 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
15:02 < jb55> molz: most likely it's the txid of the last unbroadcasted state
15:04 < molz> jb55, im not sure but one of them is in my channel to sleepyark, i've had no unbroacast tx on this node
15:04 < molz> they just don't make sense to me
15:04 < jb55> molz: yeah so you have a signed tx of the last valid state that you hold until you want to close the channel
15:05 < molz> what?
15:05 < molz> these are supposed to be onchain txid's, right?
15:05 < jb55> molz: a channel state (current bar tab balance between both nodes) is just a bitcoin tx that hasn't been broadcasted to the bitcoin network
15:06 < jb55> the onchain tx is the funding tx
15:06 < jb55> but then there are other tx's that represent the channel balance that you update between each other
15:07 < jb55> and when you unilaterally or cooperatively close you broadcast that state to the chain. I'm guessing that's what the scratch_txid is
15:07 < molz> wondering if i should close one channel right now to find out
15:08 < jb55> well when you do a cooperative close I think it would create a new state that might not match the current scratch_txid... 
15:09 < jb55> if my high level understanding of the protocol is accurate enough...
15:22 -!- justanotheruser [~justanoth@unaffiliated/justanotheruser] has joined #c-lightning
15:32 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #c-lightning
17:13 -!- belcher_ [~belcher@unaffiliated/belcher] has quit [Ping timeout: 252 seconds]
17:14 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Ping timeout: 252 seconds]
17:14 -!- antanst [~antanst@62.169.219.213] has quit [Quit: ZNC 1.7.1 - https://znc.in]
17:15 -!- belcher_ [~belcher@unaffiliated/belcher] has joined #c-lightning
17:39 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has joined #c-lightning
18:40 -!- jb55 [~jb55@S010660e327dca171.vc.shawcable.net] has quit [Quit: WeeChat 2.2]
20:06 -!- ebx [~ebx@unaffiliated/ebex] has quit [Remote host closed the connection]
20:51 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
20:52 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:53 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
20:54 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
20:58 -!- mn3monic [jsz@unaffiliated/mn3monic] has quit [Excess Flood]
20:58 -!- mn3monic [jsz@unaffiliated/mn3monic] has joined #c-lightning
21:06 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has quit [Read error: Connection reset by peer]
21:07 -!- Victorsueca [~Victorsue@unaffiliated/victorsueca] has joined #c-lightning
21:57 -!- ken2812221 [~ken281222@110.50.135.178] has quit [Remote host closed the connection]
21:57 -!- ken2812221 [~ken281222@110.50.135.178] has joined #c-lightning
22:58 -!- antanst [~antanst@62.169.219.213] has joined #c-lightning
23:27 -!- ken2812221 [~ken281222@110.50.135.178] has quit [Read error: Connection reset by peer]
23:28 -!- ken2812221 [~ken281222@110.50.135.178] has joined #c-lightning
23:43 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 252 seconds]
23:46 -!- thorie [~thorie@71.19.150.176] has joined #c-lightning
--- Log closed Thu Oct 11 00:00:33 2018