core-lightning/wire/extracted_peer_05_newonion.patch

--- peer_wire.csv	2021-08-25 12:41:02.876254003 +0930
+++ peer_wire.csv.raw	2021-08-25 13:42:31.991693809 +0930
@@ -320,3 +210,11 @@
 msgdata,gossip_timestamp_filter,chain_hash,chain_hash,
 msgdata,gossip_timestamp_filter,first_timestamp,u32,
 msgdata,gossip_timestamp_filter,timestamp_range,u32,
+msgtype,obs2_onion_message,387,option_onion_messages
+msgdata,obs2_onion_message,blinding,point,
+msgdata,obs2_onion_message,len,u16,
+msgdata,obs2_onion_message,onionmsg,byte,len
+msgtype,onion_message,513,option_onion_messages
+msgdata,onion_message,blinding,point,
+msgdata,onion_message,len,u16,
+msgdata,onion_message,onionmsg,byte,len
wire: import new onion message spec. One change from the obsolete version handling, gossipd will no longer send forwarding onion msgs to lightningd, but will forward it directly. That was the effect before, anyway. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-09-21 23:15:26 +02:00			`--- peer_wire.csv 2021-08-25 12:41:02.876254003 +0930`
			`+++ peer_wire.csv.raw 2021-08-25 13:42:31.991693809 +0930`
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			`@@ -320,3 +210,11 @@`
common: remove support for pre v0.10.2 onionmessages. Temporarily disable sendpay_blinding test which uses obsolete onionmsg; there's still some debate on the PR about how blinded HTLCs will work. Changelog-EXPERIMENTAL: onionmessage: removed support for v0.10.1 onion messages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-11-30 04:06:04 +01:00			`msgdata,gossip_timestamp_filter,chain_hash,chain_hash,`
			`msgdata,gossip_timestamp_filter,first_timestamp,u32,`
			`msgdata,gossip_timestamp_filter,timestamp_range,u32,`
common: rename current onion message structures to obs2_. Yes, we changed the spec again. Hopefully for the last time! Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2021-11-30 04:06:04 +01:00			`+msgtype,obs2_onion_message,387,option_onion_messages`
			`+msgdata,obs2_onion_message,blinding,point,`
			`+msgdata,obs2_onion_message,len,u16,`
			`+msgdata,obs2_onion_message,onionmsg,byte,len`
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			`+msgtype,onion_message,513,option_onion_messages`
			`+msgdata,onion_message,blinding,point,`
			`+msgdata,onion_message,len,u16,`
			`+msgdata,onion_message,onionmsg,byte,len`