core-lightning/wire/extracted_peer_warning.patch

--- wire/peer_exp_wire.csv	2021-01-14 11:00:27.526336550 +1030
+++ -	2021-01-21 15:31:37.071118999 +1030
@@ -10,6 +10,10 @@
 msgdata,error,channel_id,channel_id,
 msgdata,error,len,u16,
 msgdata,error,data,byte,len
+msgtype,warning,1
+msgdata,warning,channel_id,channel_id,
+msgdata,warning,len,u16,
+msgdata,warning,data,byte,len
 msgtype,ping,18
 msgdata,ping,num_pong_bytes,u16,
 msgdata,ping,byteslen,u16,
lightningd: implement receiving warnings. This takes from the draft spec at https://github.com/lightningnetwork/lightning-rfc/pull/834 Note that if this draft does not get included, the peer will simply ignore the warning message (we always close the connection afterwards anyway). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> Changelog-Added: Protocol: we now report the new (draft) warning message. 2021-02-02 13:46:01 +01:00			`--- wire/peer_exp_wire.csv 2021-01-14 11:00:27.526336550 +1030`
			`+++ - 2021-01-21 15:31:37.071118999 +1030`
			`@@ -10,6 +10,10 @@`
			`msgdata,error,channel_id,channel_id,`
			`msgdata,error,len,u16,`
			`msgdata,error,data,byte,len`
			`+msgtype,warning,1`
			`+msgdata,warning,channel_id,channel_id,`
			`+msgdata,warning,len,u16,`
			`+msgdata,warning,data,byte,len`
			`msgtype,ping,18`
			`msgdata,ping,num_pong_bytes,u16,`
			`msgdata,ping,byteslen,u16,`