rgb-cln/openingd/dualopend_wire.csv

9.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/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# master-dualopend: peer has reconnected
17# master->dualopend: reply back with our first funding info/contribs
18# master->dualopend: reply back with our funding info/contribs
19# dualopend->master: is this a valid RBF candidate transaction?
20# master->dualopend: this is a valid RBF candidate transaction
21# master->dualopend: attempt an RBF
22# dualopend->master: ready to commit channel open to database and
23# get some signatures for the funding_tx.
24# dualopend->master: peer updated the psbt
25# master->dualopend: we updated the psbt
26# master->dualopend: fail this channel open
27# dualopend->master received tx_sigs from peer
28# master->dualopend send our tx_sigs to peer
29# dualopend->master tx sigs transmitted to peer
30# dualopend->peer peer locked channel
31# dualopend->master this channel has been locked
32# master->dualopend funding reached depth; tell peer
33# Tell peer to shut down channel.
34# Peer told us that channel is shutting down
35# Peer presented proof it was from the future.
36# master -> dualopend: do you have a memleak?