mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-02-24 07:07:46 +01:00
6cf8a19881
The requirements for accepting the remote config are more complex than a simple min/max value, as various parameters are related. It turns out that with a few assumptions, we can boil this down to: 1. The valid feerate range. 2. The minimum effective HTLC throughput we want 3. The a maximum delay we'll accept for us to redeem. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2.3 KiB
2.3 KiB
| 1 | #include <lightningd/cryptomsg.h> |
|---|---|
| 2 | #include <lightningd/channel_config.h> |
| 3 | opening_init,0 |
| 4 | # Base configuration we'll offer (channel reserve will vary with amount) |
| 5 | opening_init,0,our_config,36,struct channel_config |
| 6 | # Minimum/maximum configuration values we'll accept |
| 7 | opening_init,36,max_to_self_delay,4 |
| 8 | opening_init,40,min_effective_htlc_capacity_msat,8 |
| 9 | opening_init,48,crypto_state,144,struct crypto_state |
| 10 | # Seed to generate all the keys from |
| 11 | opening_init,196,seed,32,struct privkey |
| 12 | # This means we offer the open. |
| 13 | opening_open,1 |
| 14 | opening_open,0,funding_satoshis,8 |
| 15 | opening_open,8,push_msat,8 |
| 16 | opening_open,16,feerate_per_kw,4 |
| 17 | opening_open,20,max_minimum_depth,4 |
| 18 | # Response asks for txid of funding transaction. |
| 19 | opening_open_resp,101 |
| 20 | opening_open_resp,0,local_fundingkey,33 |
| 21 | opening_open_resp,0,remote_fundingkey,33 |
| 22 | # Now we give the funding txid and outnum. |
| 23 | opening_open_funding,2 |
| 24 | opening_open_funding,0,txid,32,struct sha256_double |
| 25 | opening_open_funding,32,txout,1,u8 |
| 26 | # This gives their sig, means we can broadcast tx: we're done. |
| 27 | opening_open_funding_resp,102 |
| 28 | opening_open_funding_resp,0,their_config,36,struct channel_config |
| 29 | opening_open_funding_resp,36,first_commit_sig,64,secp256k1_ecdsa_signature |
| 30 | opening_open_funding_resp,100,crypto_state,144,struct crypto_state |
| 31 | opening_open_funding_resp,244,revocation_basepoint,33 |
| 32 | opening_open_funding_resp,277,payment_basepoint,33 |
| 33 | opening_open_funding_resp,310,delayed_payment_basepoint,33 |
| 34 | opening_open_funding_resp,343,their_per_commit_point,33 |
| 35 | # This means they offer the open (contains their offer packet) |
| 36 | opening_accept,3 |
| 37 | opening_accept,0,min_feerate,4 |
| 38 | opening_accept,4,max_feerate,4 |
| 39 | opening_accept,8,len,2 |
| 40 | opening_accept,10,msg,len,u8 |
| 41 | # This gives the txid of their funding tx: we're done. |
| 42 | opening_accept_resp,103 |
| 43 | opening_accept_resp,0,funding_txid,32,struct sha256_double |
| 44 | opening_accept_resp,32,funding_txout,1,u8 |
| 45 | opening_accept_resp,33,their_config,36,struct channel_config |
| 46 | opening_accept_resp,69,first_commit_sig,64,secp256k1_ecdsa_signature |
| 47 | opening_accept_resp,133,crypto_state,144,struct crypto_state |
| 48 | opening_accept_resp,277,remote_fundingkey,33 |
| 49 | opening_accept_resp,310,revocation_basepoint,33 |
| 50 | opening_accept_resp,343,payment_basepoint,33 |
| 51 | opening_accept_resp,376,delayed_payment_basepoint,33 |
| 52 | opening_accept_resp,409,their_per_commit_point,33 |
| 53 | # You're OK to exit. |
| 54 | opening_exit_req,99 |