core-lightning/gossipd/gossipd_wire.csv
Rusty Russell 7f5fe52320 gossipd: remove online gossip_store compaction.
It was an obscure dev command, as it never worked reliably.
It would be much easier to re-implement once this is done.

This turned out to reveal a tiny leak on
tests/test_gossip.py::test_gossip_store_load_amount_truncated where we
didn't immedately free chan_ann if it was dangling.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2024-02-04 09:24:44 +10:30

3.3 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# Set artificial maximum reply_channel_range size. Master->gossipd
28msgtype,gossipd_dev_set_max_scids_encode_size,3030
29msgdata,gossipd_dev_set_max_scids_encode_size,max,u32,
30# Gossipd->master get this tx output please.
31msgtype,gossipd_get_txout,3018
32msgdata,gossipd_get_txout,short_channel_id,short_channel_id,
33# master->gossipd here is the output, or empty if none.
34msgtype,gossipd_get_txout_reply,3118
35msgdata,gossipd_get_txout_reply,short_channel_id,short_channel_id,
36msgdata,gossipd_get_txout_reply,satoshis,amount_sat,
37msgdata,gossipd_get_txout_reply,len,u16,
38msgdata,gossipd_get_txout_reply,outscript,u8,len
39# master -> gossipd: these potential funding outpoints were spent, please forget any channels
40msgtype,gossipd_outpoints_spent,3024
41msgdata,gossipd_outpoints_spent,blockheight,u32,
42msgdata,gossipd_outpoints_spent,len,u32,
43msgdata,gossipd_outpoints_spent,short_channel_id,short_channel_id,len
44# master -> gossipd: do you have a memleak?
45msgtype,gossipd_dev_memleak,3033
46msgtype,gossipd_dev_memleak_reply,3133
47msgdata,gossipd_dev_memleak_reply,leak,bool,
48# master -> gossipd: blockheight increased.
49msgtype,gossipd_new_blockheight,3026
50msgdata,gossipd_new_blockheight,blockheight,u32,
51# gossipd: got it!
52msgtype,gossipd_new_blockheight_reply,3126
53# Lightningd tells us to inject a gossip message (for addgossip RPC)
54msgtype,gossipd_addgossip,3044
55msgdata,gossipd_addgossip,len,u16,
56msgdata,gossipd_addgossip,msg,u8,len
57# Empty string means no problem.
58msgtype,gossipd_addgossip_reply,3144
59msgdata,gossipd_addgossip_reply,err,wirestring,
60# Lightningd asks gossipd for any known addresses for that node.
61msgtype,gossipd_get_addrs,3050
62msgdata,gossipd_get_addrs,id,node_id,
63msgtype,gossipd_get_addrs_reply,3150
64msgdata,gossipd_get_addrs_reply,num,u16,
65msgdata,gossipd_get_addrs_reply,addrs,wireaddr,num
66subtype,peer_update
67subtypedata,peer_update,scid,short_channel_id,
68subtypedata,peer_update,fee_base,u32,
69subtypedata,peer_update,fee_ppm,u32,
70subtypedata,peer_update,cltv_delta,u16,
71subtypedata,peer_update,htlc_minimum_msat,amount_msat,
72subtypedata,peer_update,htlc_maximum_msat,amount_msat,
73# Tell lightningd we received channel update info for a local channel
74msgtype,gossipd_remote_channel_update,3010
75msgdata,gossipd_remote_channel_update,source_node,?node_id,
76msgdata,gossipd_remote_channel_update,peer_update,peer_update,