Re: [Lightning-dev] [DRAFT] Multi-cell-hop onion with TLV (and example for multi-part-payment)

2018-11-29 Thread ZmnSCPxj via Lightning-dev
Good morning Rusty, > > On another topic, how about: > > > > - type 6: `application_data` > > length: variable > > value: unknown > > > > > > Writer MUST only use for final hop, and only if it knows that the final hop > > has a specific application that it is compatible with. > >

Re: [Lightning-dev] [DRAFT] Multi-cell-hop onion with TLV (and example for multi-part-payment)

2018-11-28 Thread Rusty Russell
ZmnSCPxj writes: > Good morning Rusty, > >> There's a kinda-neat intersection between the "use TLV" proposal and the >> "multi-cell-onion" idea, so I want to make a concrete proposal (wording >> needs formalization): >> >> Multi-cell structure: >> >> 1. `realm` (or `per_hop_type` if you prefer)

Re: [Lightning-dev] [DRAFT] Multi-cell-hop onion with TLV (and example for multi-part-payment)

2018-11-27 Thread ZmnSCPxj via Lightning-dev
Good morning Rusty, > There's a kinda-neat intersection between the "use TLV" proposal and the > "multi-cell-onion" idea, so I want to make a concrete proposal (wording > needs formalization): > > Multi-cell structure: > > 1. `realm` (or `per_hop_type` if you prefer) meaning expanded. > 2.

[Lightning-dev] [DRAFT] Multi-cell-hop onion with TLV (and example for multi-part-payment)

2018-11-27 Thread Rusty Russell
There's a kinda-neat intersection between the "use TLV" proposal and the "multi-cell-onion" idea, so I want to make a concrete proposal (wording needs formalization): Multi-cell structure: 1. `realm` (or `per_hop_type` if you prefer) meaning expanded. 2. Lower 4 bits is `num_extra_cells` to use