--- Day changed Sat Jul 25 2015
00:13 -!- akrmn [~akrmn@192.95.51.167] has quit [Quit: Leaving.]
01:30 -!- CJP [~CJP@a83-163-77-195.adsl.xs4all.nl] has joined #lightning-dev
01:41 < CJP> Hi
01:49 -!- bedeho [~bedeho@ti0128a400-3195.bb.online.no] has quit [Ping timeout: 264 seconds]
02:40 -!- Guest4710 [~c@93.182.179.229] has joined #lightning-dev
03:35 -!- bedeho [~bedeho@ti0128a400-3195.bb.online.no] has joined #lightning-dev
04:03 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev
04:08 < Guest4710> Referring to the HTLC sender redeemscript in rusty's latest paper: If Bob gains knowledge of R after the timeout, he will be able to spend the HTLC output from the commitment transaction because Alice is encumbered by the CSV. Is this right? Shouldn't Alice be guaranteed to be able to get back the HTLC funds if the timeout has expired, granted that the commitment transaction hasn't been invalidate
04:08 < Guest4710> d?
04:11 < rusty> Guest4710: A good question!
04:11 < rusty> Guest4710: If Bob knows R *and* Alice broadcasts her commit tx, sure.
04:12 < rusty> Guest4710: Alice should be sure to remove the now-expired HTLC before she can no longer profit from learning R.
04:20 -!- bedeho [~bedeho@ti0128a400-3195.bb.online.no] has quit [Ping timeout: 244 seconds]
04:23 < rusty> go1111111: nice... I've replied on-forum.  It's late here though, I think I need to re-read tomorrow to make sure I'm not missing something!
04:24 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has left #lightning-dev []
04:25 < Guest4710> Hmm.. need to think this through to get it. Your answer relies on both parties settling on a new commitment tx, right? But if they don't settle for whatever reason and Alice want to pull her funds, then Bob will be able to get the HTLC output even if he gained knowledge of R after the timeout.
06:04 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has joined #lightning-dev
06:19 -!- CodeShark [~textual@cpe-76-167-237-202.san.res.rr.com] has quit [Ping timeout: 240 seconds]
06:39 -!- Janaka-Steph [~Janaka-St@che77-1-82-238-24-26.fbx.proxad.net] has quit [Quit: My Mac Pro has gone to sleep. ZZZzzz…]
06:48 -!- CJP [~CJP@a83-163-77-195.adsl.xs4all.nl] has quit [Quit: Ik ga weg]
07:39 -!- Janaka-Steph [~Janaka-St@che77-1-82-238-24-26.fbx.proxad.net] has joined #lightning-dev
07:45 -!- bedeho [~bedeho@ti0128a400-3195.bb.online.no] has joined #lightning-dev
07:57 -!- bedeho [~bedeho@ti0128a400-3195.bb.online.no] has quit [Ping timeout: 244 seconds]
07:59 -!- bedeho [~bedeho@ti0128a400-3195.bb.online.no] has joined #lightning-dev
08:03 -!- Janaka-Steph [~Janaka-St@che77-1-82-238-24-26.fbx.proxad.net] has quit [Quit: Textual IRC Client: www.textualapp.com]
09:11 -!- Luke-Jr [~luke-jr@unaffiliated/luke-jr] has quit [Read error: Connection reset by peer]
09:11 -!- Luke-Jr [~luke-jr@unaffiliated/luke-jr] has joined #lightning-dev
09:29 -!- bedeho [~bedeho@ti0128a400-3195.bb.online.no] has quit [Ping timeout: 252 seconds]
09:31 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has quit [Remote host closed the connection]
09:38 -!- bsm117532 [~bsm117532@static-108-21-236-13.nycmny.fios.verizon.net] has joined #lightning-dev
10:47 -!- bedeho [~bedeho@ti0128a400-3195.bb.online.no] has joined #lightning-dev
11:06 -!- bedeho [~bedeho@ti0128a400-3195.bb.online.no] has quit [Ping timeout: 246 seconds]
12:29 < go1111111> as described before, my asymmetric anchor tx idea required two txs to be confirmed in sequence. I think I have a fix so it now takes the same amount of time as in Rusty's original scheme: https://bitcointalk.org/index.php?topic=1134319.msg11969780#msg11969780
12:30 < go1111111> basically, the anchor tx now contains two outputs, one of negligable value that is only used so that Bob can make his tx outside of the LN channel depend on it
12:30 < go1111111> so he doesn't have to worry about that tx being confirmed without the anchor being confirmed
12:48 -!- CodeShark [~textual@cpe-76-167-237-202.san.res.rr.com] has joined #lightning-dev
12:55 -!- bedeho [~bedeho@ti0128a400-3195.bb.online.no] has joined #lightning-dev
12:59 -!- Guest71952 [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has quit [Ping timeout: 246 seconds]
13:02 -!- maaku [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has joined #lightning-dev
13:03 -!- maaku is now known as Guest74139
13:48 -!- ghtdak [~ghtdak@173-10-78-132-BusName-Washington.hfc.comcastbusiness.net] has joined #lightning-dev
13:53 -!- ghtdak [~ghtdak@173-10-78-132-BusName-Washington.hfc.comcastbusiness.net] has quit [Quit: Leaving.]
14:43 -!- bedeho [~bedeho@ti0128a400-3195.bb.online.no] has quit [Ping timeout: 244 seconds]
17:49 < go1111111> ^scratch that.. I no longer think the asymmetric anchor idea as originally described required more time. updated the bitcointalk post to reflect that. let me know if i'm missing something.
18:38 < CodeShark> my client disconnected - I missed a bit of the earlier discussion
18:40 < CodeShark> it would help to make some diagrams :)
18:52 < CodeShark> I think it works, go1111111 
21:15 -!- jtimon [~quassel@200.Red-79-148-174.dynamicIP.rima-tde.net] has quit [Ping timeout: 244 seconds]
21:31 -!- Guest74139 [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has quit [Ping timeout: 255 seconds]
21:31 -!- maaku [~quassel@50-0-37-37.dsl.static.fusionbroadband.com] has joined #lightning-dev
21:32 -!- maaku is now known as Guest58000