core-lightning/openingd/dualopend_wire.csv
Rusty Russell 5b7f14a7cb channeld/dualopend/lightningd: use channel_ready everywhere.
This alters the billboard, but that's a human-readable thing so not
noted in CHANGELOG.

Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
Changelog-Changed: JSON-RPC: `listpeers` `status` now refers to "channel ready" rather than "funding locked" (BOLT language change for zeroconf channels)
Changelog-Added: JSON-RPC: `channel_opened` notification `channel_ready` flag.
Changelog-Deprecated: JSON-RPC: `channel_opened` notification `funding_locked` flag (use `channel_ready`: BOLTs namechange).
2022-09-12 09:34:52 +09:30

11 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 <secp256k1.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# must go last because of embedded tu32
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# must go last because embedded tu32
30# dualopend->master received tx_sigs from peer
31# master->dualopend send our tx_sigs to peer
32# dualopend->master tx sigs transmitted to peer
33# dualopend->peer peer locked channel
34# dualopend->master this channel has been locked
35# master->dualopend funding reached depth; tell peer
36# Tell peer to shut down channel.
37# Peer told us that channel is shutting down
38# Peer presented proof it was from the future.
39# master -> dualopend: do you have a memleak?
40# must go last because of embedded tu32
41# dualopend -> master: validate liqudity offer sig
42# Tell gossipd about this (as-yet) unannounced channel