core-lightning/openingd/opening_wire.csv
Rusty Russell dffe2f516a signature: wrap almost all signatures in struct bitcoin_signature.
This is prep work for when we sign htlc txs with
SIGHASH_SINGLE|SIGHASH_ANYONECANPAY.

We still deal with raw signatures for the htlc txs at the moment, since
we send them like that across the wire, and changing that was simply too
painful (for the moment?).

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-12-06 23:11:51 +01:00

3.6 KiB

1#include <common/cryptomsg.h>
2#include <common/channel_config.h>
3#include <common/derive_basepoints.h>
4opening_init,6000
5# Which network are we configured for?
6opening_init,,chain_hash,struct bitcoin_blkid
7# Base configuration we'll offer (channel reserve will vary with amount)
8opening_init,,our_config,struct channel_config
9# Minimum/maximum configuration values we'll accept
10opening_init,,max_to_self_delay,u32
11opening_init,,min_effective_htlc_capacity_msat,u64
12opening_init,,crypto_state,struct crypto_state
13opening_init,,our_basepoints,struct basepoints
14opening_init,,our_funding_pubkey,struct pubkey
15# Constraints in case the other end tries to open a channel.
16opening_init,,minimum_depth,u32
17opening_init,,min_feerate,u32
18opening_init,,max_feerate,u32
19opening_init,,can_open_channel,bool
20# Optional msg to send.
21opening_init,,len,u16
22opening_init,,msg,len*u8
23# Master->openingd: they can now open a channel if they want.
24opening_can_accept_channel,6002
25#include <common/bip32.h>
26#include <common/htlc_wire.h>
27# Master->openingd: please fund a channel.
28opening_funder,6001
29opening_funder,,funding_satoshis,u64
30opening_funder,,push_msat,u64
31opening_funder,,feerate_per_kw,u32
32opening_funder,,change_satoshis,u64
33opening_funder,,change_keyindex,u32
34opening_funder,,channel_flags,u8
35#include <common/utxo.h>
36opening_funder,,num_inputs,u16
37opening_funder,,inputs,num_inputs*struct utxo
38opening_funder,,bip32,struct ext_key
39# Openingd->master: we've successfully offered channel.
40# This gives their sig, means we can broadcast tx: we're done.
41opening_funder_reply,6101
42opening_funder_reply,,their_config,struct channel_config
43opening_funder_reply,,first_commit,struct bitcoin_tx
44opening_funder_reply,,first_commit_sig,struct bitcoin_signature
45opening_funder_reply,,crypto_state,struct crypto_state
46opening_funder_reply,,revocation_basepoint,struct pubkey
47opening_funder_reply,,payment_basepoint,struct pubkey
48opening_funder_reply,,htlc_basepoint,struct pubkey
49opening_funder_reply,,delayed_payment_basepoint,struct pubkey
50opening_funder_reply,,their_per_commit_point,struct pubkey
51opening_funder_reply,,minimum_depth,u32
52opening_funder_reply,,remote_fundingkey,struct pubkey
53opening_funder_reply,,funding_txid,struct bitcoin_txid
54opening_funder_reply,,feerate_per_kw,u32
55opening_funder_reply,,our_channel_reserve_satoshis,u64
56# Openingd->master: we failed to negotiation channel
57opening_funder_failed,6004
58opening_funder_failed,,reason,wirestring
59# Openingd->master: they offered channel.
60# This gives their txid and info, means we can send funding_signed: we're done.
61opening_fundee,6003
62opening_fundee,,their_config,struct channel_config
63opening_fundee,,first_commit,struct bitcoin_tx
64opening_fundee,,first_commit_sig,struct bitcoin_signature
65opening_fundee,,crypto_state,struct crypto_state
66opening_fundee,,revocation_basepoint,struct pubkey
67opening_fundee,,payment_basepoint,struct pubkey
68opening_fundee,,htlc_basepoint,struct pubkey
69opening_fundee,,delayed_payment_basepoint,struct pubkey
70opening_fundee,,their_per_commit_point,struct pubkey
71opening_fundee,,remote_fundingkey,struct pubkey
72opening_fundee,,funding_txid,struct bitcoin_txid
73opening_fundee,,funding_txout,u16
74opening_fundee,,funding_satoshis,u64
75opening_fundee,,push_msat,u64
76opening_fundee,,channel_flags,u8
77opening_fundee,,feerate_per_kw,u32
78# The funding signed message: send this and we're committed.
79opening_fundee,,msglen,u16
80opening_fundee,,funding_signed_msg,msglen*u8
81opening_fundee,,our_channel_reserve_satoshis,u64
82# master -> openingd: do you have a memleak?
83opening_dev_memleak,6033
84opening_dev_memleak_reply,6133
85opening_dev_memleak_reply,,leak,bool