core-lightning/hsmd/hsm_wire.csv
Christian Decker ef7a63d8f8 elements: Move from a global is_elements to a global chainparams
We now have a pointer to chainparams, that fails valgrind if we do anything
chain-specific before setting it.

Suggested-by: Rusty Russell <@rustyrussell>
2019-10-03 04:32:57 +00:00

7.5 KiB

1# Clients should not give a bad request but not the HSM's decision to crash.
2msgtype,hsmstatus_client_bad_request,1000
3msgdata,hsmstatus_client_bad_request,id,node_id,
4msgdata,hsmstatus_client_bad_request,description,wirestring,
5msgdata,hsmstatus_client_bad_request,len,u16,
6msgdata,hsmstatus_client_bad_request,msg,u8,len
7#include <bitcoin/chainparams.h>
8# Start the HSM.
9msgtype,hsm_init,11
10msgdata,hsm_init,bip32_key_version,bip32_key_version,
11msgdata,hsm_init,chainparams,chainparams,
12msgdata,hsm_init,dev_force_privkey,?privkey,
13msgdata,hsm_init,dev_force_bip32_seed,?secret,
14msgdata,hsm_init,dev_force_channel_secrets,?secrets,
15msgdata,hsm_init,dev_force_channel_secrets_shaseed,?sha256,
16#include <common/bip32.h>
17msgtype,hsm_init_reply,111
18msgdata,hsm_init_reply,node_id,node_id,
19msgdata,hsm_init_reply,bip32,ext_key,
20# Get a new HSM FD, with the specified capabilities
21msgtype,hsm_client_hsmfd,9
22# Which identity to use for requests
23msgdata,hsm_client_hsmfd,id,node_id,
24# Database id for this client, if any.
25msgdata,hsm_client_hsmfd,dbid,u64,
26msgdata,hsm_client_hsmfd,capabilities,u64,
27# No content, just an fd.
28msgtype,hsm_client_hsmfd_reply,109
29#include <common/derive_basepoints.h>
30# Get the basepoints and funding key for this specific channel.
31msgtype,hsm_get_channel_basepoints,10
32msgdata,hsm_get_channel_basepoints,peerid,node_id,
33msgdata,hsm_get_channel_basepoints,dbid,u64,
34msgtype,hsm_get_channel_basepoints_reply,110
35msgdata,hsm_get_channel_basepoints_reply,basepoints,basepoints,
36msgdata,hsm_get_channel_basepoints_reply,funding_pubkey,pubkey,
37# Return signature for a funding tx.
38#include <common/utxo.h>
39# FIXME: This should also take their commit sig & details, to verify.
40msgtype,hsm_sign_funding,4
41msgdata,hsm_sign_funding,satoshi_out,amount_sat,
42msgdata,hsm_sign_funding,change_out,amount_sat,
43msgdata,hsm_sign_funding,change_keyindex,u32,
44msgdata,hsm_sign_funding,our_pubkey,pubkey,
45msgdata,hsm_sign_funding,their_pubkey,pubkey,
46msgdata,hsm_sign_funding,num_inputs,u16,
47msgdata,hsm_sign_funding,inputs,utxo,num_inputs
48msgtype,hsm_sign_funding_reply,104
49msgdata,hsm_sign_funding_reply,tx,bitcoin_tx,
50# Master asks the HSM to sign a node_announcement
51msgtype,hsm_node_announcement_sig_req,6
52msgdata,hsm_node_announcement_sig_req,annlen,u16,
53msgdata,hsm_node_announcement_sig_req,announcement,u8,annlen
54msgtype,hsm_node_announcement_sig_reply,106
55msgdata,hsm_node_announcement_sig_reply,signature,secp256k1_ecdsa_signature,
56# Sign a withdrawal request
57msgtype,hsm_sign_withdrawal,7
58msgdata,hsm_sign_withdrawal,satoshi_out,amount_sat,
59msgdata,hsm_sign_withdrawal,change_out,amount_sat,
60msgdata,hsm_sign_withdrawal,change_keyindex,u32,
61msgdata,hsm_sign_withdrawal,num_outputs,u16,
62msgdata,hsm_sign_withdrawal,outputs,bitcoin_tx_output,num_outputs
63msgdata,hsm_sign_withdrawal,num_inputs,u16,
64msgdata,hsm_sign_withdrawal,inputs,utxo,num_inputs
65msgtype,hsm_sign_withdrawal_reply,107
66msgdata,hsm_sign_withdrawal_reply,tx,bitcoin_tx,
67# Sign an invoice
68msgtype,hsm_sign_invoice,8
69msgdata,hsm_sign_invoice,len,u16,
70msgdata,hsm_sign_invoice,u5bytes,u8,len
71msgdata,hsm_sign_invoice,hrplen,u16,
72msgdata,hsm_sign_invoice,hrp,u8,hrplen
73msgtype,hsm_sign_invoice_reply,108
74msgdata,hsm_sign_invoice_reply,sig,secp256k1_ecdsa_recoverable_signature,
75# Give me ECDH(node-id-secret,point)
76msgtype,hsm_ecdh_req,1
77msgdata,hsm_ecdh_req,point,pubkey,
78msgtype,hsm_ecdh_resp,100
79msgdata,hsm_ecdh_resp,ss,secret,
80msgtype,hsm_cannouncement_sig_req,2
81msgdata,hsm_cannouncement_sig_req,calen,u16,
82msgdata,hsm_cannouncement_sig_req,ca,u8,calen
83msgtype,hsm_cannouncement_sig_reply,102
84msgdata,hsm_cannouncement_sig_reply,node_signature,secp256k1_ecdsa_signature,
85msgdata,hsm_cannouncement_sig_reply,bitcoin_signature,secp256k1_ecdsa_signature,
86msgtype,hsm_cupdate_sig_req,3
87msgdata,hsm_cupdate_sig_req,culen,u16,
88msgdata,hsm_cupdate_sig_req,cu,u8,culen
89msgtype,hsm_cupdate_sig_reply,103
90msgdata,hsm_cupdate_sig_reply,culen,u16,
91msgdata,hsm_cupdate_sig_reply,cu,u8,culen
92# Master asks HSM to sign a commitment transaction.
93msgtype,hsm_sign_commitment_tx,5
94msgdata,hsm_sign_commitment_tx,peer_id,node_id,
95msgdata,hsm_sign_commitment_tx,channel_dbid,u64,
96msgdata,hsm_sign_commitment_tx,tx,bitcoin_tx,
97msgdata,hsm_sign_commitment_tx,remote_funding_key,pubkey,
98msgdata,hsm_sign_commitment_tx,funding_amount,amount_sat,
99msgtype,hsm_sign_commitment_tx_reply,105
100msgdata,hsm_sign_commitment_tx_reply,sig,bitcoin_signature,
101# Onchaind asks HSM to sign a spend to-us. Four variants, since each set
102# of keys is derived differently...
103# FIXME: Have master tell hsmd the keyindex, so it can validate output!
104msgtype,hsm_sign_delayed_payment_to_us,12
105msgdata,hsm_sign_delayed_payment_to_us,commit_num,u64,
106msgdata,hsm_sign_delayed_payment_to_us,tx,bitcoin_tx,
107msgdata,hsm_sign_delayed_payment_to_us,wscript_len,u16,
108msgdata,hsm_sign_delayed_payment_to_us,wscript,u8,wscript_len
109msgdata,hsm_sign_delayed_payment_to_us,input_amount,amount_sat,
110msgtype,hsm_sign_remote_htlc_to_us,13
111msgdata,hsm_sign_remote_htlc_to_us,remote_per_commitment_point,pubkey,
112msgdata,hsm_sign_remote_htlc_to_us,tx,bitcoin_tx,
113msgdata,hsm_sign_remote_htlc_to_us,wscript_len,u16,
114msgdata,hsm_sign_remote_htlc_to_us,wscript,u8,wscript_len
115msgdata,hsm_sign_remote_htlc_to_us,input_amount,amount_sat,
116msgtype,hsm_sign_penalty_to_us,14
117msgdata,hsm_sign_penalty_to_us,revocation_secret,secret,
118msgdata,hsm_sign_penalty_to_us,tx,bitcoin_tx,
119msgdata,hsm_sign_penalty_to_us,wscript_len,u16,
120msgdata,hsm_sign_penalty_to_us,wscript,u8,wscript_len
121msgdata,hsm_sign_penalty_to_us,input_amount,amount_sat,
122# Onchaind asks HSM to sign a local HTLC success or HTLC timeout tx.
123msgtype,hsm_sign_local_htlc_tx,16
124msgdata,hsm_sign_local_htlc_tx,commit_num,u64,
125msgdata,hsm_sign_local_htlc_tx,tx,bitcoin_tx,
126msgdata,hsm_sign_local_htlc_tx,wscript_len,u16,
127msgdata,hsm_sign_local_htlc_tx,wscript,u8,wscript_len
128msgdata,hsm_sign_local_htlc_tx,input_amount,amount_sat,
129# Openingd/channeld asks HSM to sign the other sides' commitment tx.
130msgtype,hsm_sign_remote_commitment_tx,19
131msgdata,hsm_sign_remote_commitment_tx,tx,bitcoin_tx,
132msgdata,hsm_sign_remote_commitment_tx,remote_funding_key,pubkey,
133msgdata,hsm_sign_remote_commitment_tx,funding_amount,amount_sat,
134# channeld asks HSM to sign remote HTLC tx.
135msgtype,hsm_sign_remote_htlc_tx,20
136msgdata,hsm_sign_remote_htlc_tx,tx,bitcoin_tx,
137msgdata,hsm_sign_remote_htlc_tx,len,u16,
138msgdata,hsm_sign_remote_htlc_tx,wscript,u8,len
139msgdata,hsm_sign_remote_htlc_tx,amounts_satoshi,amount_sat,
140msgdata,hsm_sign_remote_htlc_tx,remote_per_commit_point,pubkey,
141# closingd asks HSM to sign mutual close tx.
142msgtype,hsm_sign_mutual_close_tx,21
143msgdata,hsm_sign_mutual_close_tx,tx,bitcoin_tx,
144msgdata,hsm_sign_mutual_close_tx,remote_funding_key,pubkey,
145msgdata,hsm_sign_mutual_close_tx,funding,amount_sat,
146# Reply for all the above requests.
147msgtype,hsm_sign_tx_reply,112
148msgdata,hsm_sign_tx_reply,sig,bitcoin_signature,
149# Openingd/channeld/onchaind asks for Nth per_commitment_point, if > 2, gets N-2 secret.
150msgtype,hsm_get_per_commitment_point,18
151msgdata,hsm_get_per_commitment_point,n,u64,
152msgtype,hsm_get_per_commitment_point_reply,118
153msgdata,hsm_get_per_commitment_point_reply,per_commitment_point,pubkey,
154msgdata,hsm_get_per_commitment_point_reply,old_commitment_secret,?secret,
155# master -> hsmd: do you have a memleak?
156msgtype,hsm_dev_memleak,33
157msgtype,hsm_dev_memleak_reply,133
158msgdata,hsm_dev_memleak_reply,leak,bool,
159# channeld asks to check if claimed future commitment_secret is correct.
160msgtype,hsm_check_future_secret,22
161msgdata,hsm_check_future_secret,n,u64,
162msgdata,hsm_check_future_secret,commitment_secret,secret,
163msgtype,hsm_check_future_secret_reply,122
164msgdata,hsm_check_future_secret_reply,correct,bool,