core-lightning/wire/extracted_onion_exp_enctlv.patch

--- wire/extracted_onion_wire_csv	2020-02-25 05:52:39.612291156 +1030
+++ -	2020-03-20 15:11:55.763880895 +1030
--- wire/onion_exp_wire.csv.~1~	2021-11-17 10:56:59.947630815 +1030
+++ wire/onion_exp_wire.csv	2021-11-17 10:59:39.304581244 +1030
@@ -8,6 +8,10 @@
 tlvtype,tlv_payload,payment_data,8
 tlvdata,tlv_payload,payment_data,payment_secret,byte,32
 tlvdata,tlv_payload,payment_data,total_msat,tu64,
+tlvtype,tlv_payload,encrypted_recipient_data,10
+tlvdata,tlv_payload,encrypted_recipient_data,encrypted_data,byte,...
+tlvtype,tlv_payload,blinding_point,12
+tlvdata,tlv_payload,blinding_point,blinding,point,
 tlvtype,obs2_onionmsg_payload,reply_path,2
 tlvdata,obs2_onionmsg_payload,reply_path,first_node_id,point,
 tlvdata,obs2_onionmsg_payload,reply_path,blinding,point,
EXPERIMENTAL: onion TLV field for enctlv for blinding. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2020-04-11 04:50:51 +02:00			`--- wire/extracted_onion_wire_csv 2020-02-25 05:52:39.612291156 +1030`
			`+++ - 2020-03-20 15:11:55.763880895 +1030`
spec: import latest onionmessage spec, based on routeblinding. This is from 6e99c5feaf60cb797507d181fe583224309318e9 We renamed the enctlv field to encrypted_recipient_data in the spec, and the new onion_message is message 513. We don't handle it until the next patch. Two renames: 1. blinding_seed -> blinding_point. 2. enctlv -> encrypted_recipient_data. We don't do a compat cycle for our JSON APIs for these experimental features only used by our own plugins, we just rename. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-11-30 04:06:04 +01:00			`--- wire/onion_exp_wire.csv.~1~ 2021-11-17 10:56:59.947630815 +1030`
			`+++ wire/onion_exp_wire.csv 2021-11-17 10:59:39.304581244 +1030`
			`@@ -8,6 +8,10 @@`
EXPERIMENTAL: onion TLV field for enctlv for blinding. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2020-04-11 04:50:51 +02:00			`tlvtype,tlv_payload,payment_data,8`
			`tlvdata,tlv_payload,payment_data,payment_secret,byte,32`
			`tlvdata,tlv_payload,payment_data,total_msat,tu64,`
spec: import latest onionmessage spec, based on routeblinding. This is from 6e99c5feaf60cb797507d181fe583224309318e9 We renamed the enctlv field to encrypted_recipient_data in the spec, and the new onion_message is message 513. We don't handle it until the next patch. Two renames: 1. blinding_seed -> blinding_point. 2. enctlv -> encrypted_recipient_data. We don't do a compat cycle for our JSON APIs for these experimental features only used by our own plugins, we just rename. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-11-30 04:06:04 +01:00			`+tlvtype,tlv_payload,encrypted_recipient_data,10`
			`+tlvdata,tlv_payload,encrypted_recipient_data,encrypted_data,byte,...`
			`+tlvtype,tlv_payload,blinding_point,12`
			`+tlvdata,tlv_payload,blinding_point,blinding,point,`
connectd: restore obs2 onion support. I removed these prematurely: we haven't had a release since introducing them! This consists of reverting d15d629b8bbbf3e36fc69f75991de18cc6a6c93e "plugins/fetchinvoice: remove obsolete string-based API." and plugins/fetchinvoice: remove obsolete string-based API. "onion_messages: remove obs2 support." Some minor changes due to updated fromwire_tlv API since they were removed, but not much. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-EXPERIMENTAL: REVERT: Removed backwards compat with onion messages from v0.10.1. 2022-03-28 01:10:54 +02:00			`tlvtype,obs2_onionmsg_payload,reply_path,2`
			`tlvdata,obs2_onionmsg_payload,reply_path,first_node_id,point,`
			`tlvdata,obs2_onionmsg_payload,reply_path,blinding,point,`