core-lightning/lightningd/gossip/gossip_wire.csv
Rusty Russell ccad93edb3 gossipd: add fail_peer.
We use this if it reconnects via another fd.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-25 14:24:47 +09:30

3.4 KiB

1# These are fatal.
2gossipstatus_init_failed,0x8000
3gossipstatus_bad_new_peer_request,0x8001
4gossipstatus_bad_release_request,0x8002
5gossipstatus_bad_fail_request,0x8003
6gossipstatus_bad_request,0x8004
7gossipstatus_fdpass_failed,0x8005
8# Peers can give a bad message, we close their fd, but no harm done.
9gossipstatus_peer_bad_msg,1000
10gossipstatus_peer_bad_msg,0,unique_id,8
11gossipstatus_peer_bad_msg,8,len,2
12gossipstatus_peer_bad_msg,10,err,len*u8
13# Misc problems like opening control fd.
14gossipstatus_peer_failed,1001
15gossipstatus_peer_failed,0,unique_id,8
16gossipstatus_peer_failed,8,len,2
17gossipstatus_peer_failed,10,err,len*u8
18#include <lightningd/cryptomsg.h>
19# Initialize the gossip daemon
20gossipctl_init,0
21gossipctl_init,0,broadcast_interval,4
22# These take an fd, but have no response
23# (if it is to move onto a channel, we get a status msg).
24gossipctl_new_peer,1
25gossipctl_new_peer,0,unique_id,8
26gossipctl_new_peer,8,crypto_state,struct crypto_state
27# Tell it to release a peer which has initialized.
28gossipctl_release_peer,2
29gossipctl_release_peer,0,unique_id,8
30# This releases the peer and returns the cryptostate (followed two fds: peer and gossip)
31gossipctl_release_peer_reply,102
32gossipctl_release_peer_reply,0,unique_id,8
33gossipctl_release_peer_reply,8,crypto_state,struct crypto_state
34# This is where we save a peer's features.
35#gossipstatus_peer_features,1
36#gossipstatus_peer_features,0,unique_id,8
37#gossipstatus_peer_features,8,gflen,2
38#gossipstatus_peer_features,10,globalfeatures,gflen
39#gossipstatus_peer_features,10+gflen,lflen,2
40#gossipstatus_peer_features,12+gflen,localfeatures,lflen
41# Peer can send non-gossip packet (usually an open_channel) (followed two fds: peer and gossip)
42gossipstatus_peer_nongossip,4
43gossipstatus_peer_nongossip,0,unique_id,8
44gossipstatus_peer_nongossip,10,crypto_state,struct crypto_state
45gossipstatus_peer_nongossip,154,len,2
46gossipstatus_peer_nongossip,156,msg,len*u8
47# Pass JSON-RPC getnodes call through
48gossip_getnodes_request,5
49#include <lightningd/gossip_msg.h>
50gossip_getnodes_reply,105
51gossip_getnodes_reply,0,num_nodes,u16
52gossip_getnodes_reply,2,nodes,num_nodes*struct gossip_getnodes_entry
53# Pass JSON-RPC getroute call through
54gossip_getroute_request,6
55gossip_getroute_request,0,source,struct pubkey
56gossip_getroute_request,33,destination,struct pubkey
57gossip_getroute_request,66,msatoshi,u32
58gossip_getroute_request,70,riskfactor,u16
59gossip_getroute_reply,106
60gossip_getroute_reply,0,num_hops,u16
61gossip_getroute_reply,2,hops,num_hops*struct route_hop
62gossip_getchannels_request,7
63gossip_getchannels_reply,107
64gossip_getchannels_reply,0,num_channels,u16
65gossip_getchannels_reply,2,nodes,num_channels*struct gossip_getchannels_entry
66# Ping/pong test.
67gossip_ping,8
68gossip_ping,0,unique_id,u64
69gossip_ping,0,num_pong_bytes,u16
70gossip_ping,0,len,u16
71gossip_ping_reply,108
72gossip_ping_reply,0,totlen,u16
73# Given a short_channel_id, return the endpoints
74gossip_resolve_channel_request,9
75gossip_resolve_channel_request,0,channel_id,struct short_channel_id
76gossip_resolve_channel_reply,109
77gossip_resolve_channel_reply,0,num_keys,u16
78gossip_resolve_channel_reply,0,keys,num_keys*struct pubkey
79# The main daemon forward some gossip message to gossipd, allows injecting
80# arbitrary gossip messages.
81gossip_forwarded_msg,10
82gossip_forwarded_msg,0,msglen,2
83gossip_forwarded_msg,2,msg,msglen
84# If peer is still connected, fail it (master does this for reconnect)
85gossipctl_fail_peer,11
86gossipctl_fail_peer,0,unique_id,8