Re: [Lightning-dev] Multi-frame sphinx onion format

2019-02-24 Thread Christian Decker
ZmnSCPxj writes: > Good morning Christian, Rusty, and list, > You can take this a step further and make the realm 0 byte into a > special type "0" which has a fixed length of 1299 bytes, with the > length never encoded for this special type. It would then define the > next 1299 bytes as the "V",

Re: [Lightning-dev] Multi-frame sphinx onion format

2019-02-23 Thread ZmnSCPxj via Lightning-dev
Good morning Christian, Rusty, and list, > There is however a third option, namely make the entire payload a > TLV-set and then use the old payload format (`short_channel_id`, > `amt_to_forward`, `outgoing_ctlv_value`) as a single TLV-value with 20 > bytes of size. That means we have only 2 bytes

Re: [Lightning-dev] Multi-frame sphinx onion format

2019-02-22 Thread Christian Decker
Rusty Russell writes: > There are two ways to add TLV to the onion: > 1. Leave the existing fields and put TLV in the padding: >* [`8`:`short_channel_id`] >* [`8`:`amt_to_forward`] >* [`4`:`outgoing_cltv_value`] >* [`12`:`padding`] > 2. Replace existing fields with TLV (eg. 2=short

Re: [Lightning-dev] Multi-frame sphinx onion format

2019-02-21 Thread Rusty Russell
Subnote on this, there's a query on TLV format (1 byte type, 1 byte+ len). There are two ways to add TLV to the onion: 1. Leave the existing fields and put TLV in the padding: * [`8`:`short_channel_id`] * [`8`:`amt_to_forward`] * [`4`:`outgoing_cltv_value`] * [`12`:`padding`] 2. Replac