mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-02-23 15:00:34 +01:00
We were sending a channeld message to onchaind, which was v. confusing due to overlap. We make all the numbers distinct, which means we can also add an assert() that it's valid for that daemon, which catches such errors immediately. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2.9 KiB
2.9 KiB
1 | #include <common/cryptomsg.h> |
---|---|
2 | #include <common/channel_config.h> |
3 | opening_init,6000 |
4 | # Which network are we configured for (as index into the chainparams)? |
5 | opening_init,,network_index,4 |
6 | # Base configuration we'll offer (channel reserve will vary with amount) |
7 | opening_init,,our_config,struct channel_config |
8 | # Minimum/maximum configuration values we'll accept |
9 | opening_init,,max_to_self_delay,4 |
10 | opening_init,,min_effective_htlc_capacity_msat,8 |
11 | opening_init,,crypto_state,struct crypto_state |
12 | # Seed to generate all the keys from |
13 | opening_init,,seed,struct privkey |
14 | #include <common/bip32.h> |
15 | #include <common/htlc_wire.h> |
16 | # This means we offer the open. |
17 | opening_funder,6001 |
18 | opening_funder,,funding_satoshis,8 |
19 | opening_funder,,push_msat,8 |
20 | opening_funder,,feerate_per_kw,4 |
21 | opening_funder,,max_minimum_depth,4 |
22 | opening_funder,,change_satoshis,u64 |
23 | opening_funder,,change_keyindex,u32 |
24 | opening_funder,,channel_flags,u8 |
25 | #include <common/utxo.h> |
26 | opening_funder,,num_inputs,u16 |
27 | opening_funder,,inputs,num_inputs*struct utxo |
28 | opening_funder,,bip32,struct ext_key |
29 | # This gives their sig, means we can broadcast tx: we're done. |
30 | opening_funder_reply,6101 |
31 | opening_funder_reply,,their_config,struct channel_config |
32 | opening_funder_reply,,first_commit,struct bitcoin_tx |
33 | opening_funder_reply,,first_commit_sig,secp256k1_ecdsa_signature |
34 | opening_funder_reply,,crypto_state,struct crypto_state |
35 | opening_funder_reply,,revocation_basepoint,33 |
36 | opening_funder_reply,,payment_basepoint,33 |
37 | opening_funder_reply,,delayed_payment_basepoint,33 |
38 | opening_funder_reply,,their_per_commit_point,33 |
39 | opening_funder_reply,,minimum_depth,4 |
40 | opening_funder_reply,,remote_fundingkey,33 |
41 | opening_funder_reply,,funding_txid,struct sha256_double |
42 | opening_funder_reply,,feerate_per_kw,4 |
43 | # This means they offer the open (contains their offer packet) |
44 | opening_fundee,6003 |
45 | opening_fundee,,minimum_depth,4 |
46 | opening_fundee,,min_feerate,4 |
47 | opening_fundee,,max_feerate,4 |
48 | opening_fundee,,len,2 |
49 | opening_fundee,,msg,len*u8 |
50 | # This gives their txid and info, means we can send funding_signed: we're done. |
51 | opening_fundee_reply,6103 |
52 | opening_fundee_reply,,their_config,struct channel_config |
53 | opening_fundee_reply,,first_commit,struct bitcoin_tx |
54 | opening_fundee_reply,,first_commit_sig,secp256k1_ecdsa_signature |
55 | opening_fundee_reply,,crypto_state,struct crypto_state |
56 | opening_fundee_reply,,revocation_basepoint,33 |
57 | opening_fundee_reply,,payment_basepoint,33 |
58 | opening_fundee_reply,,delayed_payment_basepoint,33 |
59 | opening_fundee_reply,,their_per_commit_point,33 |
60 | opening_fundee_reply,,remote_fundingkey,33 |
61 | opening_fundee_reply,,funding_txid,struct sha256_double |
62 | opening_fundee_reply,,funding_txout,u16 |
63 | opening_fundee_reply,,funding_satoshis,8 |
64 | opening_fundee_reply,,push_msat,8 |
65 | opening_fundee_reply,,channel_flags,u8 |
66 | opening_fundee_reply,,feerate_per_kw,4 |
67 | # The (encrypted) funding signed message: send this and we're committed. |
68 | opening_fundee_reply,,msglen,u16 |
69 | opening_fundee_reply,,funding_signed_msg,msglen*u8 |