lightning/handshaked/handshake_wire.csv

#include <common/cryptomsg.h>

# FIXME: This is probably too finegrained.
initr_act_one,14001
initr_act_two,14002
initr_act_three,14003
respr_act_one,14011
respr_act_two,14012
respr_act_three,14013
success,4000

handshake_responder,4001
handshake_responder,,my_id,struct pubkey
handshake_responder_reply,4101
handshake_responder_reply,,initiator_id,struct pubkey
handshake_responder_reply,,cs,struct crypto_state
handshake_responder_reply,,gflen,u16
handshake_responder_reply,,globalfeatures,gflen*u8
handshake_responder_reply,,lflen,u16
handshake_responder_reply,,localfeatures,lflen*u8

handshake_initiator,4002
handshake_initiator,,my_id,struct pubkey
handshake_initiator,,responder_id,struct pubkey

handshake_initiator_reply,4102
handshake_initiator_reply,,cs,struct crypto_state
handshake_initiator_reply,,gflen,u16
handshake_initiator_reply,,globalfeatures,gflen*u8
handshake_initiator_reply,,lflen,u16
handshake_initiator_reply,,localfeatures,lflen*u8
common: move some files out of lightningd/ Basically all files shared by different daemons. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 8 years ago			`#include <common/cryptomsg.h>`
lightningd/handshake: convert to subd. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 8 years ago
			`# FIXME: This is probably too finegrained.`
Make all internal message numbers unique. We were sending a channeld message to onchaind, which was v. confusing due to overlap. We make all the numbers distinct, which means we can also add an assert() that it's valid for that daemon, which catches such errors immediately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 7 years ago			`initr_act_one,14001`
			`initr_act_two,14002`
			`initr_act_three,14003`
			`respr_act_one,14011`
			`respr_act_two,14012`
			`respr_act_three,14013`
			`success,4000`
lightningd/handshake: convert to subd. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 8 years ago
Make all internal message numbers unique. We were sending a channeld message to onchaind, which was v. confusing due to overlap. We make all the numbers distinct, which means we can also add an assert() that it's valid for that daemon, which catches such errors immediately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 7 years ago			`handshake_responder,4001`
generate-wire.py: add --bolt arg, use size->type hacks only when that's specified. For our own internal comms CSVs, we should always name explicit types. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 7 years ago			`handshake_responder,,my_id,struct pubkey`
Make all internal message numbers unique. We were sending a channeld message to onchaind, which was v. confusing due to overlap. We make all the numbers distinct, which means we can also add an assert() that it's valid for that daemon, which catches such errors immediately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 7 years ago			`handshake_responder_reply,4101`
generate-wire.py: add --bolt arg, use size->type hacks only when that's specified. For our own internal comms CSVs, we should always name explicit types. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 7 years ago			`handshake_responder_reply,,initiator_id,struct pubkey`
lightningd: remove unused offset field from CSV files. The format we use to generate marshal/unmarshal code is from the spec's tools/extract-formats.py which includes the offset: we don't use it at all, so rather than having manually-calculated (and thus probably wrong) values, or 0, emit it altogther. Reported-by: Christian Decker Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 8 years ago			`handshake_responder_reply,,cs,struct crypto_state`
generate-wire.py: add --bolt arg, use size->type hacks only when that's specified. For our own internal comms CSVs, we should always name explicit types. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 7 years ago			`handshake_responder_reply,,gflen,u16`
			`handshake_responder_reply,,globalfeatures,gflen*u8`
			`handshake_responder_reply,,lflen,u16`
			`handshake_responder_reply,,localfeatures,lflen*u8`
lightningd/handshake: convert to subd. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 8 years ago
Make all internal message numbers unique. We were sending a channeld message to onchaind, which was v. confusing due to overlap. We make all the numbers distinct, which means we can also add an assert() that it's valid for that daemon, which catches such errors immediately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 7 years ago			`handshake_initiator,4002`
generate-wire.py: add --bolt arg, use size->type hacks only when that's specified. For our own internal comms CSVs, we should always name explicit types. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 7 years ago			`handshake_initiator,,my_id,struct pubkey`
			`handshake_initiator,,responder_id,struct pubkey`
lightningd/handshake: convert to subd. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 8 years ago
Make all internal message numbers unique. We were sending a channeld message to onchaind, which was v. confusing due to overlap. We make all the numbers distinct, which means we can also add an assert() that it's valid for that daemon, which catches such errors immediately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 7 years ago			`handshake_initiator_reply,4102`
lightningd: remove unused offset field from CSV files. The format we use to generate marshal/unmarshal code is from the spec's tools/extract-formats.py which includes the offset: we don't use it at all, so rather than having manually-calculated (and thus probably wrong) values, or 0, emit it altogther. Reported-by: Christian Decker Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 8 years ago			`handshake_initiator_reply,,cs,struct crypto_state`
generate-wire.py: add --bolt arg, use size->type hacks only when that's specified. For our own internal comms CSVs, we should always name explicit types. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> 7 years ago			`handshake_initiator_reply,,gflen,u16`
			`handshake_initiator_reply,,globalfeatures,gflen*u8`
			`handshake_initiator_reply,,lflen,u16`
			`handshake_initiator_reply,,localfeatures,lflen*u8`