mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2025-02-22 14:42:40 +01:00
Code Issues Projects Releases Wiki Activity
core-lightning/wire/extracted_peer_05_newonion.patch

13 lines
549 B
Diff
Raw Normal View History

wire: update to BOLT 17ceba42dc6607b637a713a9bc051f63c1357edd "BOLT 4: onion message support." We don't need to patch it in anymore, now it's merged. However, we do move the message itself from onion_wire.csv to peer_wire.csv (we should get more sophisticated with our parsing, but this works for now!). The resulting peer_wire.csv is identical, the onion_wire.csv file is slightly reordered. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2023-09-12 13:53:19 +09:30
FIXME: This is actually from BOLT 4, but we remove it from onion_wire.csv and put it here.
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-22 06:45:26 +09:30
--- peer_wire.csv 2021-08-25 12:41:02.876254003 +0930
+++ peer_wire.csv.raw 2021-08-25 13:42:31.991693809 +0930
onionmessages: remove obsolete onion message parsing. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-09-29 13:19:03 +09:30
@@ -320,3 +210,7 @@
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 13:36:04 +10:30
msgdata,gossip_timestamp_filter,chain_hash,chain_hash,
msgdata,gossip_timestamp_filter,first_timestamp,u32,
msgdata,gossip_timestamp_filter,timestamp_range,u32,
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 13:36:04 +10:30
+msgtype,onion_message,513,option_onion_messages
+msgdata,onion_message,blinding,point,
+msgdata,onion_message,len,u16,
+msgdata,onion_message,onionmsg,byte,len
Reference in a new issue Copy permalink