--- Day changed Sun Dec 11 2016
00:33 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-nkbyamsttgmvejgy] has joined #lightning-dev     
02:48 -lightningrfc:#lightning-dev- [lightning-rfc] cdecker opened pull request #50: bolt04: Add  (master...patch-03) https://git.io/v1oW1
03:07 -githubby:#lightning-dev- [lightning] cdecker opened pull request #101: ci: Replacing Travis-CI with Gitlab-CI (master...gitlab-ci) https://git.io/v1olg
06:27 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-nkbyamsttgmvejgy] has quit [Quit: Connection closed for inactivity]     
06:30 -!- BashCo [~BashCo@unaffiliated/bashco] has quit []     
06:33 -!- arubi [~ese168@gateway/tor-sasl/ese168] has quit [Remote host closed the connection]     
06:33 -!- arubi [~ese168@gateway/tor-sasl/ese168] has joined #lightning-dev     
06:43 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #lightning-dev     
07:09 -!- AaronvanW [~ewout@207pc74.sshunet.nl] has joined #lightning-dev     
07:09 -!- AaronvanW [~ewout@207pc74.sshunet.nl] has quit [Changing host]     
07:09 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has joined #lightning-dev     
07:29 -!- shesek [~shesek@bzq-84-110-57-45.red.bezeqint.net] has quit [Ping timeout: 260 seconds]     
07:45 -!- lclc__ [~lclc__@16.14.107.92.dynamic.wline.res.cust.swisscom.ch] has joined #lightning-dev     
07:47 -!- shesek [~shesek@bzq-84-110-57-94.red.bezeqint.net] has joined #lightning-dev     
08:31 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #lightning-dev     
08:40 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Quit: laurentmt]     
09:06 -!- lclc__ [~lclc__@16.14.107.92.dynamic.wline.res.cust.swisscom.ch] has quit [Quit: This computer has gone to sleep]     
09:12 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-fbjjhbsxmvzzhqzy] has joined #lightning-dev     
10:54 -!- BW^- [~Bwbwbwbwb@unaffiliated/bw-/x-2460362] has joined #lightning-dev     
10:54 < BW^-> how well does Lightning work now?
10:54 < BW^-> how far is it?
10:57 -!- vorksholk [ae1cac5c@gateway/web/freenode/ip.174.28.172.92] has quit [Ping timeout: 260 seconds]     
10:59 -!- laurentmt [~Thunderbi@176.158.157.202] has joined #lightning-dev     
10:59 -!- laurentmt [~Thunderbi@176.158.157.202] has quit [Client Quit]     
11:07 < BW^-> why is the multiple-party lightning taking time to get going, how far is it now? are there algorithmic problems?
11:15 < BW^-> what's the most recent blog post or video that summarizes where it's at now?
11:19 -!- JackH [~laptop@79-73-186-159.dynamic.dsl.as9105.com] has joined #lightning-dev     
11:24 -!- lclc__ [~lclc__@pub082136074188.dh-hfc.datazug.ch] has joined #lightning-dev     
11:32 < BW^-> why is the malleability fix neeed for lightning to work?
11:33 -!- BW^- [~Bwbwbwbwb@unaffiliated/bw-/x-2460362] has quit [Read error: Connection reset by peer]     
11:34 -!- BW^- [~Bwbwbwbwb@unaffiliated/bw-/x-2460362] has joined #lightning-dev     
11:48 -!- JackH [~laptop@79-73-186-159.dynamic.dsl.as9105.com] has quit [Remote host closed the connection]     
11:49 -!- BW^- [~Bwbwbwbwb@unaffiliated/bw-/x-2460362] has quit [Quit: BW^-]     
12:41 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev     
13:10 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]     
13:58 -!- akrmn [~akrmn@210.red-83-56-221.dynamicip.rima-tde.net] has joined #lightning-dev     
14:19 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 260 seconds]     
14:22 -!- lclc__ [~lclc__@pub082136074188.dh-hfc.datazug.ch] has quit [Quit: This computer has gone to sleep]     
14:40 -!- belcher [~belcher@unaffiliated/belcher] has joined #lightning-dev     
14:51 -!- AaronvanW [~ewout@unaffiliated/aaronvanw] has quit [Quit: Ex-Chat]     
15:08 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev     
15:24 -lightningrfc:#lightning-dev- [lightning-rfc] rustyrussell pushed 1 new commit to master: https://git.io/v1oxQ
15:24 -lightningrfc:#lightning-dev- lightning-rfc/master 669babb Christian Decker: bolt04: Added reference to RFC 2104...
16:07 -lightningrfc:#lightning-dev- [lightning-rfc] rustyrussell closed pull request #48: [trivial] Some minor fixes (master...small-fixes) https://git.io/v1rGV
16:08 -lightningrfc:#lightning-dev- [lightning-rfc] rustyrussell pushed 1 new commit to master: https://git.io/v1KvI
16:08 -lightningrfc:#lightning-dev- lightning-rfc/master 2f998f3 Rusty Russell: BOLT 3: make upper bits of commit tx locktime and sequence explicit....
16:13 -lightningrfc:#lightning-dev- [lightning-rfc] rustyrussell opened pull request #51: BOLT 4, BOLT 8: use libsecp256k1-style ECDH. (master...libsecp256k1-style-ecdh) https://git.io/v1KvW
16:19 -!- belcher [~belcher@unaffiliated/belcher] has quit [Ping timeout: 265 seconds]     
16:28 -!- belcher [~belcher@unaffiliated/belcher] has joined #lightning-dev     
16:39 < roasbeef> rusty2: for the state hints, the top bit needs to be set in order to disable sequence-locks behavior 
16:39 < rusty2> roasbeef: ack, true.  Damn, I knew I shouldn't have just pushed it.  Ack...
16:39 < roasbeef> rusty2: tob bit in the sequence num* 
16:42 < rusty2> roasbeef: right, s/upper 8 bits are zero/upper 8 bits are 0x80/
16:43 < rusty2> in "`txin[0]` sequence:"
16:46 < rusty2> roasbeef: https://github.com/rustyrussell/lightning-rfc/tree/fix-bolt-3-seqnum-rusty-is-an-idiot ?
17:06 < rusty2> roasbeef: ack and I'll push, then we can pretend it didn't happen :)
17:07 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-fbjjhbsxmvzzhqzy] has quit [Quit: Connection closed for inactivity]     
17:31 -lightningrfc:#lightning-dev- [lightning-rfc] rustyrussell opened pull request #52: Bolt 7 cleanups (master...bolt-7-cleanups) https://git.io/v1KIR
17:42 -!- PaulCapestany [~PaulCapes@2604:5500:17:2ea:80ba:b743:538a:b5ae] has joined #lightning-dev     
18:00 < roasbeef> rusty2: nice, looks good to me
18:27 -lightningrfc:#lightning-dev- [lightning-rfc] rustyrussell pushed 1 new commit to master: https://git.io/v1Kmk
18:27 -lightningrfc:#lightning-dev- lightning-rfc/master 125b9a3 Rusty Russell: BOLT 3: Fix commitment transaction input sequence number....
18:49 < rusty2> roasbeef, cdecker: hmm, did we not specify the actual plaintext format and sematics of the route info anywhere?  In particular, we need amount to forward, and may want the ts of the last route announce we received.
18:49 -!- rusty2 is now known as rusty     
18:51 < roasbeef> rusty: yeah we need: amt to forward, time lock value, target chain. currently in my code the payloads are blank, but iirc decker has a format which y'all use atm but isn't currently specified
18:52 -!- rusty [~rusty@pdpc/supporter/bronze/rusty] has quit [Quit: Leaving.]     
18:52 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has joined #lightning-dev     
18:54 < rusty2> Also, I have been trying to come up with a provable failure scheme, where each hop on return validates that the next hop has signed the failure message and committed to the onion it was sent.  This allows the originating node to publish the failure message (which then MUST be a newer channel update, or an intermittent failure msg).
18:55 < roasbeef> rusty2: so prob something along the lines of: [8:amt_to_forward][2:cltv_value][1:target_chain][9:unused_with_v0_vesion_on_header]
18:56 < roasbeef> publish the failure message as in broadcast it to the network? 
18:57 < rusty2> roasbeef: we're currently u8 realm; u64 amount; u8 remainder[11]
18:57 < rusty2> roasbeef: we should probably put the expected cltv in there, ISTR there was an issue if we don't.
18:58 < rusty2> roasbeef: yeah, the idea is that the only reasons to fail an HTLC are (1) it violates published requirements (eg. amount too low, fee too low), (2) it's using an old publication, or (3) this channel is transiently limited.
18:58 < roasbeef> by originating node do you mean the source of the payment, or the hop # that the failure occured at?
18:59 < rusty2> roasbeef: source of payment. I means that if a node is just blackholing the network, you can prove it.
18:59 < rusty2> roasbeef: (this is probably not a v1.0 thing)
19:01 < rusty2> So, failure messages are all actually channel_update messages.
19:17  * rusty2 creates a couple of issues to track these...
20:10 -!- BW^- [~Bwbwbwbwb@124.158.208.190] has joined #lightning-dev     
20:10 -!- BW^- [~Bwbwbwbwb@124.158.208.190] has quit [Changing host]     
20:10 -!- BW^- [~Bwbwbwbwb@unaffiliated/bw-/x-2460362] has joined #lightning-dev     
20:15 -!- rusty2 [~rusty@pdpc/supporter/bronze/rusty] has quit [Ping timeout: 250 seconds]     
20:25 -!- BW^- [~Bwbwbwbwb@unaffiliated/bw-/x-2460362] has quit [Read error: Connection reset by peer]     
20:29 -!- Madars [~null@unaffiliated/madars] has joined #lightning-dev     
20:54 -!- wasi [~wasi@gateway/tor-sasl/wasi] has quit [Ping timeout: 245 seconds]     
21:17 -!- wasi [~wasi@gateway/tor-sasl/wasi] has joined #lightning-dev     
21:45 -!- wasi [~wasi@gateway/tor-sasl/wasi] has quit [Ping timeout: 245 seconds]     
21:51 -!- BW^- [~Bwbwbwbwb@unaffiliated/bw-/x-2460362] has joined #lightning-dev     
21:51 < BW^-> cdecker: there?
22:00 -!- wasi [~wasi@gateway/tor-sasl/wasi] has joined #lightning-dev     
22:12 -!- BW^- [~Bwbwbwbwb@unaffiliated/bw-/x-2460362] has quit [Read error: Connection reset by peer]     
23:00 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-jmntxozuayuobkqa] has joined #lightning-dev     
23:19 -!- lclc__ [~lclc__@pub212004089088.dh-hfc.datazug.ch] has joined #lightning-dev