Files
lightning/openingd/dualopend_wire.csv
niftynei e41d2dc0e6 liquidity-ad: request amount, pass through to dualopend
Changelog-Experimental: EXPERIMENTAL-DUAL-FUND: JSON-RPC: openchannel_init now takes a `requested_amt`, which is an amount to request from peer
2021-07-20 13:28:38 -04:00

9.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/fee_states.h>
9#include <common/htlc_wire.h>
10#include <common/penalty_base.h>
11#include <common/per_peer_state.h>
12#include <wire/peer_wire.h>
13# Which network are we configured for?
14# Base configuration we'll offer
15# Minimum/maximum configuration values we'll accept
16# Constraints in case the other end tries to open a channel.
17# master-dualopend: peer has reconnected
18# master->dualopend: reply back with our first funding info/contribs
19# master->dualopend: reply back with our funding info/contribs
20# dualopend->master: is this a valid RBF candidate transaction?
21# master->dualopend: this is a valid RBF candidate transaction
22# master->dualopend: attempt an RBF
23# dualopend->master: ready to commit channel open to database and
24# get some signatures for the funding_tx.
25# dualopend->master: peer updated the psbt
26# master->dualopend: we updated the psbt
27# master->dualopend: fail this channel open
28# dualopend->master received tx_sigs from peer
29# master->dualopend send our tx_sigs to peer
30# dualopend->master tx sigs transmitted to peer
31# dualopend->peer peer locked channel
32# dualopend->master this channel has been locked
33# master->dualopend funding reached depth; tell peer
34# Tell peer to shut down channel.
35# Peer told us that channel is shutting down
36# Peer presented proof it was from the future.
37# master -> dualopend: do you have a memleak?