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