core-lightning/connectd/connect_wire.csv
Rusty Russell bd55f6d940
common/features: only support a single feature bitset.
This is mainly an internal-only change, especially since we don't
offer any globalfeatures.

However, LND (as of next release) will offer global features, and also
expect option_static_remotekey to be a *global* feature.  So we send
our (merged) feature bitset as both global and local in init, and fold
those bitsets together when we get an init msg.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-10-11 02:52:04 +00:00

2.5 KiB

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