core-lightning/connectd/connect_wire.csv
Rusty Russell c95e58ad4b subdaemons: initialize feature routines with explicit feature_set.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-03-31 13:36:02 +02:00

2.8 KiB

1#include <common/cryptomsg.h>
2#include <common/features.h>
3#include <common/per_peer_state.h>
4#include <common/wireaddr.h>
5#include <lightningd/gossip_msg.h>
6msgtype,connectctl_init,2000
7msgdata,connectctl_init,chainparams,chainparams,
8msgdata,connectctl_init,feature_set,feature_set,
9msgdata,connectctl_init,id,node_id,
10msgdata,connectctl_init,num_wireaddrs,u16,
11msgdata,connectctl_init,wireaddrs,wireaddr_internal,num_wireaddrs
12msgdata,connectctl_init,listen_announce,enum addr_listen_announce,num_wireaddrs
13msgdata,connectctl_init,tor_proxyaddr,?wireaddr,
14msgdata,connectctl_init,use_tor_proxy_always,bool,
15msgdata,connectctl_init,dev_allow_localhost,bool,
16msgdata,connectctl_init,use_dns,bool,
17msgdata,connectctl_init,tor_password,wirestring,
18msgdata,connectctl_init,use_v3_autotor,bool,
19msgdata,connectctl_init,init_featurebits_len,u16,
20msgdata,connectctl_init,init_featurebits,u8,init_featurebits_len
21# Connectd->master, here are the addresses I bound, can announce.
22msgtype,connectctl_init_reply,2100
23msgdata,connectctl_init_reply,num_bindings,u16,
24msgdata,connectctl_init_reply,bindings,wireaddr_internal,num_bindings
25msgdata,connectctl_init_reply,num_announcable,u16,
26msgdata,connectctl_init_reply,announcable,wireaddr,num_announcable
27# Activate the connect daemon, so others can connect.
28msgtype,connectctl_activate,2025
29# Do we listen?
30msgdata,connectctl_activate,listen,bool,
31# Connectd->master, I am ready.
32msgtype,connectctl_activate_reply,2125
33# connectd->master: disconnect this peer please (due to reconnect).
34msgtype,connect_reconnected,2112
35msgdata,connect_reconnected,id,node_id,
36# Master -> connectd: connect to a peer.
37msgtype,connectctl_connect_to_peer,2001
38msgdata,connectctl_connect_to_peer,id,node_id,
39msgdata,connectctl_connect_to_peer,seconds_waited,u32,
40msgdata,connectctl_connect_to_peer,addrhint,?wireaddr_internal,
41# Connectd->master: connect failed.
42msgtype,connectctl_connect_failed,2020
43msgdata,connectctl_connect_failed,id,node_id,
44msgdata,connectctl_connect_failed,failcode,errcode_t,
45msgdata,connectctl_connect_failed,failreason,wirestring,
46msgdata,connectctl_connect_failed,seconds_to_delay,u32,
47msgdata,connectctl_connect_failed,addrhint,?wireaddr_internal,
48# Connectd -> master: we got a peer. Three fds: peer, gossip and gossip_store
49msgtype,connect_peer_connected,2002
50msgdata,connect_peer_connected,id,node_id,
51msgdata,connect_peer_connected,addr,wireaddr_internal,
52msgdata,connect_peer_connected,pps,per_peer_state,
53msgdata,connect_peer_connected,flen,u16,
54msgdata,connect_peer_connected,features,u8,flen
55# master -> connectd: peer has disconnected.
56msgtype,connectctl_peer_disconnected,2015
57msgdata,connectctl_peer_disconnected,id,node_id,
58# master -> connectd: do you have a memleak?
59msgtype,connect_dev_memleak,2033
60msgtype,connect_dev_memleak_reply,2133
61msgdata,connect_dev_memleak_reply,leak,bool,