mirror of
https://github.com/ElementsProject/lightning.git
synced 2025-01-18 13:25:43 +01:00
085c590a51
Rusty pointed out that having an empty channel_id is suboptimal; adding another call is probably the right idea rather than re-using an existing one. Suggested-By: @rustyrussell
5.1 KiB
5.1 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? |