mirror of
https://github.com/ElementsProject/lightning.git
synced 2024-11-19 18:11:28 +01:00
31e3bdb42d
We consolidate to the latest/singular RFC patch for dual-funding, so there's just a single patchfile for the change. Plus we move back to the opener setting the desired feerate, the accepter merely declines to participate if they disagree with the set rate.
9.2 KiB
9.2 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/fee_states.h> |
| 9 | #include <common/htlc_wire.h> |
| 10 | #include <common/penalty_base.h> |
| 11 | #include <common/per_peer_state.h> |
| 12 | # Which network are we configured for? |
| 13 | # Base configuration we'll offer |
| 14 | # Minimum/maximum configuration values we'll accept |
| 15 | # Constraints in case the other end tries to open a channel. |
| 16 | # Optional msg to send. |
| 17 | # master-dualopend: peer has reconnected |
| 18 | # Optional msg to send. |
| 19 | # master->dualopend: reply back with our first funding info/contribs |
| 20 | # master->dualopend: reply back with our funding info/contribs |
| 21 | # dualopend->master: is this a valid RBF candidate transaction? |
| 22 | # master->dualopend: this is a valid RBF candidate transaction |
| 23 | # master->dualopend: attempt an RBF |
| 24 | # dualopend->master: ready to commit channel open to database and |
| 25 | # get some signatures for the funding_tx. |
| 26 | # dualopend->master: peer updated the psbt |
| 27 | # master->dualopend: we updated the psbt |
| 28 | # master->dualopend: fail this channel open |
| 29 | # dualopend->master received tx_sigs from peer |
| 30 | # master->dualopend send our tx_sigs to peer |
| 31 | # dualopend->master tx sigs transmitted to peer |
| 32 | # dualopend->peer peer locked channel |
| 33 | # dualopend->master this channel has been locked |
| 34 | # master->dualopend funding reached depth; tell peer |
| 35 | # Tell peer to shut down channel. |
| 36 | # Peer told us that channel is shutting down |
| 37 | # Peer presented proof it was from the future. |
| 38 | # master -> dualopend: do you have a memleak? |