core-lightning/gossipd/gossipd_wire.csv
Rusty Russell 4a78d17748 connectd: do response to gossip queries, don't hand them to gossipd.
This basically means moving the code from gossipd to connectd to handle
these queries.

This will get connectd have finer control over ratelimiting them.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2024-07-10 12:21:19 +09:30

3.2 KiB

1#include <common/cryptomsg.h>
2#include <common/features.h>
3#include <common/wireaddr.h>
4#include <wire/peer_wire.h>
5#include <wire/onion_wire.h>
6# Initialize the gossip daemon.
7msgtype,gossipd_init,3000
8msgdata,gossipd_init,chainparams,chainparams,
9msgdata,gossipd_init,our_features,feature_set,
10msgdata,gossipd_init,id,node_id,
11msgdata,gossipd_init,dev_gossip_time,?u32,
12msgdata,gossipd_init,dev_fast_gossip,bool,
13msgdata,gossipd_init,dev_fast_gossip_prune,bool,
14# Gossipd tells us all our public channel_updates before init_reply.
15msgtype,gossipd_init_cupdate,3101
16msgdata,gossipd_init_cupdate,scid,short_channel_id,
17msgdata,gossipd_init_cupdate,len,u16,
18msgdata,gossipd_init_cupdate,cupdate,u8,len
19# Gossipd tells us our node_announcement before init_reply.
20msgtype,gossipd_init_nannounce,3102
21msgdata,gossipd_init_nannounce,len,u16,
22msgdata,gossipd_init_nannounce,nannounce,u8,len
23msgtype,gossipd_init_reply,3100
24# In developer mode, we can mess with time.
25msgtype,gossipd_dev_set_time,3001
26msgdata,gossipd_dev_set_time,dev_gossip_time,u32,
27# Gossipd->master get this tx output please.
28msgtype,gossipd_get_txout,3018
29msgdata,gossipd_get_txout,short_channel_id,short_channel_id,
30# master->gossipd here is the output, or empty if none.
31msgtype,gossipd_get_txout_reply,3118
32msgdata,gossipd_get_txout_reply,short_channel_id,short_channel_id,
33msgdata,gossipd_get_txout_reply,satoshis,amount_sat,
34msgdata,gossipd_get_txout_reply,len,u16,
35msgdata,gossipd_get_txout_reply,outscript,u8,len
36# master -> gossipd: these potential funding outpoints were spent, please forget any channels
37msgtype,gossipd_outpoints_spent,3024
38msgdata,gossipd_outpoints_spent,blockheight,u32,
39msgdata,gossipd_outpoints_spent,len,u32,
40msgdata,gossipd_outpoints_spent,short_channel_id,short_channel_id,len
41# master -> gossipd: do you have a memleak?
42msgtype,gossipd_dev_memleak,3033
43msgtype,gossipd_dev_memleak_reply,3133
44msgdata,gossipd_dev_memleak_reply,leak,bool,
45# master -> gossipd: blockheight increased.
46msgtype,gossipd_new_blockheight,3026
47msgdata,gossipd_new_blockheight,blockheight,u32,
48# gossipd: got it!
49msgtype,gossipd_new_blockheight_reply,3126
50# Lightningd tells us to inject a gossip message (for addgossip RPC)
51msgtype,gossipd_addgossip,3044
52msgdata,gossipd_addgossip,len,u16,
53msgdata,gossipd_addgossip,msg,u8,len
54msgdata,gossipd_addgossip,known_channel,?amount_sat,
55# Empty string means no problem.
56msgtype,gossipd_addgossip_reply,3144
57msgdata,gossipd_addgossip_reply,err,wirestring,
58# Lightningd asks gossipd for any known addresses for that node.
59msgtype,gossipd_get_addrs,3050
60msgdata,gossipd_get_addrs,id,node_id,
61msgtype,gossipd_get_addrs_reply,3150
62msgdata,gossipd_get_addrs_reply,num,u16,
63msgdata,gossipd_get_addrs_reply,addrs,wireaddr,num
64subtype,peer_update
65subtypedata,peer_update,scid,short_channel_id,
66subtypedata,peer_update,fee_base,u32,
67subtypedata,peer_update,fee_ppm,u32,
68subtypedata,peer_update,cltv_delta,u16,
69subtypedata,peer_update,htlc_minimum_msat,amount_msat,
70subtypedata,peer_update,htlc_maximum_msat,amount_msat,
71# Tell lightningd we received channel update info for a local channel
72msgtype,gossipd_remote_channel_update,3010
73msgdata,gossipd_remote_channel_update,source_node,?node_id,
74msgdata,gossipd_remote_channel_update,peer_update,peer_update,