mirror of
https://github.com/aljazceru/lightning.git
synced 2025-12-29 20:04:34 +01:00
We let the plugin decide what feerate to accept/whether or not to add funds to the open. To aid this decision, we also send the plugin what we (c-lightning) currently have as our max and min acceptable feerates. We also now use these as our default for max/min acceptable feerate range when sending an openchannel offer to a peer. In the future, it might be a good idea to make these more easily changeable, either via a config setting (?) or a command param.
5.3 KiB
5.3 KiB
| 1 | #include <bitcoin/chainparams.h> |
|---|---|
| 2 | #include <bitcoin/psbt.h> |
| 3 | #include <common/cryptomsg.h> |
| 4 | #include <common/channel_config.h> |
| 5 | #include <common/channel_id.h> |
| 6 | #include <common/derive_basepoints.h> |
| 7 | #include <common/features.h> |
| 8 | #include <common/penalty_base.h> |
| 9 | #include <common/per_peer_state.h> |
| 10 | # Which network are we configured for? |
| 11 | # Base configuration we'll offer |
| 12 | # Minimum/maximum configuration values we'll accept |
| 13 | # Constraints in case the other end tries to open a channel. |
| 14 | # Optional msg to send. |
| 15 | # master->dualopend: reply back with our first funding info/contribs |
| 16 | # dualopend->master: ready to commit channel open to database and |
| 17 | # get some signatures for the funding_tx. |
| 18 | # dualopend->master: peer updated the psbt |
| 19 | # master->dualopend: we updated the psbt |
| 20 | # master->dualopend: fail this channel open |
| 21 | # dualopend->master: we failed to negotiate channel |
| 22 | # master -> dualopend: do you have a memleak? |