core-lightning/onchaind/onchain_wire.csv
Rusty Russell 160f27061e common/utxo: make commitment_point optional in close_info.
We don't rotate key for option_static_remotekey, so we don't need
this point for such channels.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-09-10 16:18:25 -05:00

4.4 KiB

1#include <common/derive_basepoints.h>
2#include <common/htlc_wire.h>
3#include <common/wallet.h>
4# Begin! Here's the onchain tx which spends funding tx, followed by all HTLCs.
5msgtype,onchain_init,5001
6msgdata,onchain_init,shachain,shachain,
7msgdata,onchain_init,chain_hash,bitcoin_blkid,
8msgdata,onchain_init,funding_amount_satoshi,amount_sat,
9# Remote per commit point for committed tx.
10msgdata,onchain_init,old_remote_per_commitment_point,pubkey,
11# Remote per commit point for current tx (needed if we haven't got revoke_and_ack yet).
12msgdata,onchain_init,remote_per_commitment_point,pubkey,
13msgdata,onchain_init,local_to_self_delay,u32,
14msgdata,onchain_init,remote_to_self_delay,u32,
15msgdata,onchain_init,feerate_per_kw,u32,
16msgdata,onchain_init,local_dust_limit_satoshi,amount_sat,
17# Gives an easy way to tell if it's our unilateral close or theirs...
18msgdata,onchain_init,our_broadcast_txid,bitcoin_txid,
19msgdata,onchain_init,local_scriptpubkey_len,u16,
20msgdata,onchain_init,local_scriptpubkey,u8,local_scriptpubkey_len
21msgdata,onchain_init,remote_scriptpubkey_len,u16,
22msgdata,onchain_init,remote_scriptpubkey,u8,remote_scriptpubkey_len
23msgdata,onchain_init,ourwallet_pubkey,pubkey,
24# We need these two for commit number obscurer
25msgdata,onchain_init,funder,enum side,
26msgdata,onchain_init,local_basepoints,basepoints,
27msgdata,onchain_init,remote_basepoints,basepoints,
28msgdata,onchain_init,tx,bitcoin_tx,
29msgdata,onchain_init,tx_blockheight,u32,
30msgdata,onchain_init,reasonable_depth,u32,
31msgdata,onchain_init,num_htlc_sigs,u16,
32msgdata,onchain_init,htlc_signature,secp256k1_ecdsa_signature,num_htlc_sigs
33msgdata,onchain_init,num_htlcs,u64,
34msgdata,onchain_init,min_possible_feerate,u32,
35msgdata,onchain_init,max_possible_feerate,u32,
36msgdata,onchain_init,possible_remote_per_commit_point,?pubkey,
37msgdata,onchain_init,option_static_remotekey,bool,
38#include <onchaind/onchain_wire.h>
39# This is all the HTLCs: one per message
40msgtype,onchain_htlc,5002
41msgdata,onchain_htlc,htlc,htlc_stub,
42# If it's not in the commitment tx, tell us (immediately or htlc_missing_depth)
43msgdata,onchain_htlc,tell_if_missing,bool,
44msgdata,onchain_htlc,tell_immediately,bool,
45# This says we're ready; give us preimages.
46msgtype,onchain_init_reply,5101
47# onchaind->master: Send out a tx.
48msgtype,onchain_broadcast_tx,5003
49msgdata,onchain_broadcast_tx,tx,bitcoin_tx,
50msgdata,onchain_broadcast_tx,type,enum wallet_tx_type,
51# master->onchaind: Notifier that an output has been spent by input_num of tx.
52msgtype,onchain_spent,5004
53msgdata,onchain_spent,tx,bitcoin_tx,
54msgdata,onchain_spent,input_num,u32,
55msgdata,onchain_spent,blockheight,u32,
56# master->onchaind: We will receive more than one of these, as depth changes.
57msgtype,onchain_depth,5005
58msgdata,onchain_depth,txid,bitcoin_txid,
59msgdata,onchain_depth,depth,u32,
60# onchaind->master: We don't want to watch this tx, or its outputs
61msgtype,onchain_unwatch_tx,5006
62msgdata,onchain_unwatch_tx,txid,bitcoin_txid,
63# master->onchaind: We know HTLC preimage
64msgtype,onchain_known_preimage,5007
65msgdata,onchain_known_preimage,preimage,preimage,
66# onchaind->master: We discovered HTLC preimage
67msgtype,onchain_extracted_preimage,5008
68msgdata,onchain_extracted_preimage,preimage,preimage,
69# onchaind->master: this HTLC was missing from commit tx.
70msgtype,onchain_missing_htlc_output,5009
71msgdata,onchain_missing_htlc_output,htlc,htlc_stub,
72# onchaind->master: this HTLC has timed out (after reasonable_depth)
73msgtype,onchain_htlc_timeout,5010
74msgdata,onchain_htlc_timeout,htlc,htlc_stub,
75# onchaind->master: this peer can be forgotten
76msgtype,onchain_all_irrevocably_resolved,5011
77# onchaind->master: hey, I identified an UTXO you'll want to track
78msgtype,onchain_add_utxo,5012
79msgdata,onchain_add_utxo,prev_out_tx,bitcoin_txid,
80msgdata,onchain_add_utxo,prev_out_index,u32,
81msgdata,onchain_add_utxo,per_commit_point,?pubkey,
82msgdata,onchain_add_utxo,value,amount_sat,
83msgdata,onchain_add_utxo,blockheight,u32,
84msgdata,onchain_add_utxo,len,u16,
85msgdata,onchain_add_utxo,scriptpubkey,u8,len
86# master -> onchaind: do you have a memleak?
87msgtype,onchain_dev_memleak,5033
88msgtype,onchain_dev_memleak_reply,5133
89msgdata,onchain_dev_memleak_reply,leak,bool,
90# Tell the main daemon what we've been watching, mainly used for transactions
91# that we tracked automatically but only onchaind knows how to classify their
92# transactions.
93msgtype,onchain_transaction_annotate,5034
94msgdata,onchain_transaction_annotate,txid,bitcoin_txid,
95msgdata,onchain_transaction_annotate,type,enum wallet_tx_type,