mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-12-28 01:24:42 +01:00
Code Issues Projects Releases Wiki Activity
0fd8a6492e
core-lightning/wire/onion_wire.csv

110 lines
5.0 KiB
Plaintext
Raw Normal View History

wire: split onion messages from peer wire messages. The recent update to BOLT #4 includes failure message specifications, which are completely orthogonal to the normal ones. Don't include them in the gen_peer_wire_csv. This onion_defs.h file assumes we are using 2-byte failure codes as per the onion-failmsg-cleanup branch. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-01-06 04:10:35 +01:00
#include <wire/onion_defs.h>
bolt: Update to latest bolt, including TLV onion format. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-02 05:24:25 +02:00
tlvtype,tlv_payload,amt_to_forward,2
tlvdata,tlv_payload,amt_to_forward,amt_to_forward,tu64,
tlvtype,tlv_payload,outgoing_cltv_value,4
tlvdata,tlv_payload,outgoing_cltv_value,outgoing_cltv_value,tu32,
tlvtype,tlv_payload,short_channel_id,6
tlvdata,tlv_payload,short_channel_id,short_channel_id,short_channel_id,
Protocol: make var_onion, payment_secret and basic_mpp non-EXPERIMENTAL. Thanks to @t-bast, who made this possible by interop testing with Eclair! Changelog-Added: Protocol: can now send and receive TLV-style onion messages. Changelog-Added: Protocol: can now send and receive BOLT11 payment_secrets. Changelog-Added: Protocol: can now receive basic multi-part payments. Changelog-Added: RPC: low-level commands sendpay and waitsendpay can now be used to manually send multi-part payments. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-12-12 11:57:07 +01:00
tlvtype,tlv_payload,payment_data,8
tlvdata,tlv_payload,payment_data,payment_secret,byte,32
tlvdata,tlv_payload,payment_data,total_msat,tu64,
bolt11: support payment_metadata. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-03-31 11:10:50 +02:00
tlvtype,tlv_payload,payment_metadata,16
tlvdata,tlv_payload,payment_metadata,payment_metadata,byte,...
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,
tlvdata,obs2_onionmsg_payload,reply_path,path,onionmsg_path,...
tlvtype,obs2_onionmsg_payload,enctlv,10
tlvdata,obs2_onionmsg_payload,enctlv,enctlv,byte,...
tlvtype,obs2_onionmsg_payload,invoice_request,64
tlvdata,obs2_onionmsg_payload,invoice_request,invoice_request,byte,...
tlvtype,obs2_onionmsg_payload,invoice,66
tlvdata,obs2_onionmsg_payload,invoice,invoice,byte,...
tlvtype,obs2_onionmsg_payload,invoice_error,68
tlvdata,obs2_onionmsg_payload,invoice_error,invoice_error,byte,...
tlvtype,obs2_encmsg_tlvs,padding,1
tlvdata,obs2_encmsg_tlvs,padding,pad,byte,...
tlvtype,obs2_encmsg_tlvs,next_node_id,4
tlvdata,obs2_encmsg_tlvs,next_node_id,node_id,point,
tlvtype,obs2_encmsg_tlvs,next_blinding,12
tlvdata,obs2_encmsg_tlvs,next_blinding,blinding,point,
tlvtype,obs2_encmsg_tlvs,self_id,14
tlvdata,obs2_encmsg_tlvs,self_id,data,byte,...
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,
tlvtype,encrypted_data_tlv,padding,1
tlvdata,encrypted_data_tlv,padding,padding,byte,...
tlvtype,encrypted_data_tlv,short_channel_id,2
tlvdata,encrypted_data_tlv,short_channel_id,short_channel_id,short_channel_id,
tlvtype,encrypted_data_tlv,next_node_id,4
tlvdata,encrypted_data_tlv,next_node_id,node_id,point,
tlvtype,encrypted_data_tlv,path_id,6
tlvdata,encrypted_data_tlv,path_id,data,byte,...
tlvtype,encrypted_data_tlv,next_blinding_override,8
tlvdata,encrypted_data_tlv,next_blinding_override,blinding,point,
tlvtype,onionmsg_payload,reply_path,2
tlvdata,onionmsg_payload,reply_path,first_node_id,point,
tlvdata,onionmsg_payload,reply_path,blinding,point,
tlvdata,onionmsg_payload,reply_path,path,onionmsg_path,...
tlvtype,onionmsg_payload,encrypted_data_tlv,4
tlvdata,onionmsg_payload,encrypted_data_tlv,encrypted_data_tlv,byte,...
tlvtype,onionmsg_payload,invoice_request,64
tlvdata,onionmsg_payload,invoice_request,invoice_request,byte,...
tlvtype,onionmsg_payload,invoice,66
tlvdata,onionmsg_payload,invoice,invoice,byte,...
tlvtype,onionmsg_payload,invoice_error,68
tlvdata,onionmsg_payload,invoice_error,invoice_error,byte,...
wire: Apply onion mesages spec patch even when not experimental. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2021-01-13 02:49:36 +01:00
subtype,onionmsg_path
subtypedata,onionmsg_path,node_id,point,
subtypedata,onionmsg_path,enclen,u16,
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
subtypedata,onionmsg_path,encrypted_recipient_data,byte,enclen
bolt: update to BOLT spec changes (extract format + type specifications) updates the bolt version to 6639cef095a2ecc7b8f0c48c6e7f2f906fbfbc58. this requires us to use the new bolt parser at generate-bolt.py and updates to all of the type specifications (ie. from u8 -> byte)
2019-07-16 01:20:37 +02:00
msgtype,invalid_realm,PERM|1
msgtype,temporary_node_failure,NODE|2
msgtype,permanent_node_failure,PERM|NODE|2
msgtype,required_node_feature_missing,PERM|NODE|3
msgtype,invalid_onion_version,BADONION|PERM|4
msgdata,invalid_onion_version,sha256_of_onion,sha256,
msgtype,invalid_onion_hmac,BADONION|PERM|5
msgdata,invalid_onion_hmac,sha256_of_onion,sha256,
msgtype,invalid_onion_key,BADONION|PERM|6
msgdata,invalid_onion_key,sha256_of_onion,sha256,
msgtype,temporary_channel_failure,UPDATE|7
msgdata,temporary_channel_failure,len,u16,
msgdata,temporary_channel_failure,channel_update,byte,len
msgtype,permanent_channel_failure,PERM|8
msgtype,required_channel_feature_missing,PERM|9
msgtype,unknown_next_peer,PERM|10
msgtype,amount_below_minimum,UPDATE|11
msgdata,amount_below_minimum,htlc_msat,u64,
msgdata,amount_below_minimum,len,u16,
msgdata,amount_below_minimum,channel_update,byte,len
msgtype,fee_insufficient,UPDATE|12
msgdata,fee_insufficient,htlc_msat,u64,
msgdata,fee_insufficient,len,u16,
msgdata,fee_insufficient,channel_update,byte,len
msgtype,incorrect_cltv_expiry,UPDATE|13
msgdata,incorrect_cltv_expiry,cltv_expiry,u32,
msgdata,incorrect_cltv_expiry,len,u16,
msgdata,incorrect_cltv_expiry,channel_update,byte,len
msgtype,expiry_too_soon,UPDATE|14
msgdata,expiry_too_soon,len,u16,
msgdata,expiry_too_soon,channel_update,byte,len
msgtype,incorrect_or_unknown_payment_details,PERM|15
msgdata,incorrect_or_unknown_payment_details,htlc_msat,u64,
BOLT: update CSV to latest bolt version. This removes the WIRE_FINAL_EXPIRY_TOO_SOON which leaked too much info, and adds the blockheight to WIRE_INCORRECT_OR_UNKNOWN_PAYMENT_DETAILS. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-28 06:06:17 +02:00
msgdata,incorrect_or_unknown_payment_details,height,u32,
bolt: update to BOLT spec changes (extract format + type specifications) updates the bolt version to 6639cef095a2ecc7b8f0c48c6e7f2f906fbfbc58. this requires us to use the new bolt parser at generate-bolt.py and updates to all of the type specifications (ie. from u8 -> byte)
2019-07-16 01:20:37 +02:00
msgtype,final_incorrect_cltv_expiry,18
msgdata,final_incorrect_cltv_expiry,cltv_expiry,u32,
msgtype,final_incorrect_htlc_amount,19
msgdata,final_incorrect_htlc_amount,incoming_htlc_amt,u64,
msgtype,channel_disabled,UPDATE|20
specs: update CSV files. Regenerate from current BOLTS via `make extract-bolt-csv` 1. The remote_addr field was added manually into peer_wire.csv: this needs to be a patch otherwise it vanishes on regen. 2. We never brought into the channel_disabled fields, because it was too much hassle (we never actually generate this!). Do it now. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2022-03-31 11:10:05 +02:00
msgdata,channel_disabled,flags,u16,
msgdata,channel_disabled,len,u16,
msgdata,channel_disabled,channel_update,byte,len
bolt: update to BOLT spec changes (extract format + type specifications) updates the bolt version to 6639cef095a2ecc7b8f0c48c6e7f2f906fbfbc58. this requires us to use the new bolt parser at generate-bolt.py and updates to all of the type specifications (ie. from u8 -> byte)
2019-07-16 01:20:37 +02:00
msgtype,expiry_too_far,21
wire: update csv to current bolt. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-20 08:57:20 +02:00
msgtype,invalid_onion_payload,PERM|22
wire: update to latest version of the spec. The main change here is that the previously-optional open/accept fields and reestablish fields are now compulsory (everyone was including them anyway). In fact, the open/accept is a TLV because it was actually the same format. For more details, see lightning-rfc/f068dd0d8dfa5ae75feedd99f269e23be4777381 Changelog-Removed: protocol: support for optioned form of reestablish messages now compulsory. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-06-22 07:06:03 +02:00
msgdata,invalid_onion_payload,type,bigsize,
wire: update csv to current bolt. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-20 08:57:20 +02:00
msgdata,invalid_onion_payload,offset,u16,
Protocol: make var_onion, payment_secret and basic_mpp non-EXPERIMENTAL. Thanks to @t-bast, who made this possible by interop testing with Eclair! Changelog-Added: Protocol: can now send and receive TLV-style onion messages. Changelog-Added: Protocol: can now send and receive BOLT11 payment_secrets. Changelog-Added: Protocol: can now receive basic multi-part payments. Changelog-Added: RPC: low-level commands sendpay and waitsendpay can now be used to manually send multi-part payments. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-12-12 11:57:07 +01:00
msgtype,mpp_timeout,23
Reference in New Issue Copy Permalink