core-lightning/common/status_wire.csv
Rusty Russell 00cb5adfe6 common: allow subdaemons to specify the node_id in status messages.
This is ignored in subdaemons which are per-peer, but very useful for
multi-peer daemons like connectd and gossipd.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-11-18 04:50:22 +00:00

736 B

1#include <common/per_peer_state.h>
2#include <common/status_wire.h>
3msgtype,status_log,0xFFF0
4msgdata,status_log,level,enum log_level,
5msgdata,status_log,peer,?node_id,
6msgdata,status_log,entry,wirestring,
7msgtype,status_io,0xFFF1
8msgdata,status_io,iodir,enum log_level,
9msgdata,status_io,peer,?node_id,
10msgdata,status_io,who,wirestring,
11msgdata,status_io,len,u16,
12msgdata,status_io,data,u8,len
13msgtype,status_fail,0xFFF2
14msgdata,status_fail,failreason,enum status_failreason,
15msgdata,status_fail,desc,wirestring,
16msgtype,status_peer_connection_lost,0xFFF3
17msgtype,status_peer_billboard,0xFFF5
18msgdata,status_peer_billboard,perm,bool,
19msgdata,status_peer_billboard,happenings,wirestring,
20# Note: 0xFFFF is reserved for MSG_PASS_FD!