core-lightning/gossipd/gossipd_peerd_wire.csv

# These must be distinct from WIRE_CHANNEL_ANNOUNCEMENT etc. gossip msgs!
#include <bitcoin/short_channel_id.h>
#include <common/amount.h>

# Channel daemon can ask for updates for a specific channel, for sending
# errors.  
msgtype,gossipd_get_update,3501
msgdata,gossipd_get_update,short_channel_id,short_channel_id,

# If channel isn't known, update will be empty.
msgtype,gossipd_get_update_reply,3601
msgdata,gossipd_get_update_reply,len,u16,
msgdata,gossipd_get_update_reply,update,u8,len

# Send this channel_update.
msgtype,gossipd_local_channel_update,3504
msgdata,gossipd_local_channel_update,short_channel_id,short_channel_id,
msgdata,gossipd_local_channel_update,disable,bool,
msgdata,gossipd_local_channel_update,cltv_expiry_delta,u16,
msgdata,gossipd_local_channel_update,htlc_minimum_msat,amount_msat,
msgdata,gossipd_local_channel_update,fee_base_msat,u32,
msgdata,gossipd_local_channel_update,fee_proportional_millionths,u32,
msgdata,gossipd_local_channel_update,htlc_maximum_msat,amount_msat,

# Send this channel_announcement
msgtype,gossipd_local_channel_announcement,3506
msgdata,gossipd_local_channel_announcement,len,u16,
msgdata,gossipd_local_channel_announcement,cannount,u8,len
gossipd: don't wrap messages when we send them to the peer. They already send us gossip messages, so they have to be distinct anyway. Why make us both do extra work? Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-06-03 20:12:25 +02:00			`# These must be distinct from WIRE_CHANNEL_ANNOUNCEMENT etc. gossip msgs!`
wire: move towire/fromwire_short_channel_id out to bitcoin/short_channel_id.c Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2020-05-15 12:32:43 +02:00			`#include <bitcoin/short_channel_id.h>`
wire: move remaining bitcoin functions out to bitcoin/ files. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2020-05-16 03:29:05 +02:00			`#include <common/amount.h>`
wire: move towire/fromwire_short_channel_id out to bitcoin/short_channel_id.c Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2020-05-15 12:32:43 +02:00
gossipd: split wire types into msgs from lightningd and msgs from per-peer daemons This avoids some very ugly switch() statements which mixed the two, but we also take the chance to rename 'towire_gossip_' to 'towire_gossipd_' for those inter-daemon messages; they're messages to gossipd, not gossip messages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-11-13 05:03:51 +01:00			`# Channel daemon can ask for updates for a specific channel, for sending`
gossipd: don't wrap messages when we send them to the peer. They already send us gossip messages, so they have to be distinct anyway. Why make us both do extra work? Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-06-03 20:12:25 +02:00			`# errors.`
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgtype,gossipd_get_update,3501`
			`msgdata,gossipd_get_update,short_channel_id,short_channel_id,`
gossipd: split wire types into msgs from lightningd and msgs from per-peer daemons This avoids some very ugly switch() statements which mixed the two, but we also take the chance to rename 'towire_gossip_' to 'towire_gossipd_' for those inter-daemon messages; they're messages to gossipd, not gossip messages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-11-13 05:03:51 +01:00
			`# If channel isn't known, update will be empty.`
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgtype,gossipd_get_update_reply,3601`
			`msgdata,gossipd_get_update_reply,len,u16,`
			`msgdata,gossipd_get_update_reply,update,u8,len`
gossipd: split wire types into msgs from lightningd and msgs from per-peer daemons This avoids some very ugly switch() statements which mixed the two, but we also take the chance to rename 'towire_gossip_' to 'towire_gossipd_' for those inter-daemon messages; they're messages to gossipd, not gossip messages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2018-11-13 05:03:51 +01:00
			`# Send this channel_update.`
wire-gen: move in-house wire delcarations to new format tidying things up! 2019-07-24 00:51:11 +02:00			`msgtype,gossipd_local_channel_update,3504`
			`msgdata,gossipd_local_channel_update,short_channel_id,short_channel_id,`
			`msgdata,gossipd_local_channel_update,disable,bool,`
			`msgdata,gossipd_local_channel_update,cltv_expiry_delta,u16,`
			`msgdata,gossipd_local_channel_update,htlc_minimum_msat,amount_msat,`
			`msgdata,gossipd_local_channel_update,fee_base_msat,u32,`
			`msgdata,gossipd_local_channel_update,fee_proportional_millionths,u32,`
			`msgdata,gossipd_local_channel_update,htlc_maximum_msat,amount_msat,`
gossipd: provide new fd to per-peer daemons when we compact it. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-05-04 07:53:13 +02:00
gossipd: push our own gossip messages harder. I had a report of a 0.7.2 user whose node hadn't appeared on 1ml. Their node_announcement wasn't visible to my node, either. I suspect this is a consequence of recent version reducing the amount of gossip they send, as well as large nodes increasingly turning off gossip altogether from some peers (as we do). We should ignore timestamp filters for our own channels: the easiest way to do this is to push them out directly from gossipd (other messages are sent via the store). We change channeld to wrap the local channel_announcements: previously we just handed it to gossipd as for any other gossip message we received from our peer. Now gossipd knows to push it out, as it's local. This interferes with the logic in tests/test_misc.py::test_htlc_send_timeout which expects the node_announcement message last, so we generalize that too. [ Thanks to @trueptolmy for bugfix! ] Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 2019-10-11 12:23:12 +02:00			`# Send this channel_announcement`
			`msgtype,gossipd_local_channel_announcement,3506`
			`msgdata,gossipd_local_channel_announcement,len,u16,`
			`msgdata,gossipd_local_channel_announcement,cannount,u8,len`