core-lightning/hsmd/hsm_wire.csv
lisa neigut 16656a85cf withdraw: refactor change output handling
We're not using the change_outnum for withdraw tx's (and the way
we were calculating it was broken as of the addition of 'multiple
outputs'). This removes the change output knowhow from withdraw_tx
entirely, and pushes the responsibility up to the caller to
include the change output in the output set if desired.

Consequently, we also remove the change output knowhow from hsmd.
2020-06-23 14:49:32 +02:00

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