mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-11-19 18:11:28 +01:00
Code Issues Projects Releases Wiki Activity
3e311b2510
core-lightning/lightningd/channel_state.h

37 lines
857 B
C
Raw Normal View History

lightningd: rename peer_state -> channel_state, remove OPENINGD. And now we can finally do the db upgrade to remove any OPENINGD channels once, since we never put them back. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-19 02:06:14 +01:00
#ifndef LIGHTNING_LIGHTNINGD_CHANNEL_STATE_H
#define LIGHTNING_LIGHTNINGD_CHANNEL_STATE_H
lightningd: introduce peer_state enum. The actual state names are place holders for now, really. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-22 13:24:59 +02:00
#include "config.h"
lightningd: rename peer_state -> channel_state, remove OPENINGD. And now we can finally do the db upgrade to remove any OPENINGD channels once, since we never put them back. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-19 02:06:14 +01:00
/* These are in the database, so don't renumber them! */
enum channel_state {
lightningd: peer state cleanup. 1. We explicitly assert what state we're coming from, to make transitions clearer. 2. Every transition has a state, even between owners while waiting for HSM. 3. Explictly step though getting the HSM signature on the funding tx before starting channeld, rather than doing it in parallel: makes states clearer. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-22 13:27:20 +02:00
/* In channeld, still waiting for lockin. */
lightningd: rename peer_state -> channel_state, remove OPENINGD. And now we can finally do the db upgrade to remove any OPENINGD channels once, since we never put them back. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-19 02:06:14 +01:00
CHANNELD_AWAITING_LOCKIN = 2,
lightningd: introduce peer_state enum. The actual state names are place holders for now, really. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-22 13:24:59 +02:00
/* Normal operating state. */
lightningd: peer state cleanup. 1. We explicitly assert what state we're coming from, to make transitions clearer. 2. Every transition has a state, even between owners while waiting for HSM. 3. Explictly step though getting the HSM signature on the funding tx before starting channeld, rather than doing it in parallel: makes states clearer. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-22 13:27:20 +02:00
CHANNELD_NORMAL,
lightningd: introduce peer_state enum. The actual state names are place holders for now, really. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-22 13:24:59 +02:00
/* We are closing, pending HTLC resolution. */
channeld: shutdown support. We keep the scriptpubkey to send until after a commitment_signed (or, in the corner case, if there's no pending commitment). When we receive a shutdown from the peer, we pass it up to the master. It's up to the master not to add any more HTLCs, which works because we move from CHANNELD_NORMAL to CHANNELD_SHUTTING_DOWN. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-06-26 03:16:43 +02:00
CHANNELD_SHUTTING_DOWN,
lightningd: introduce peer_state enum. The actual state names are place holders for now, really. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-22 13:24:59 +02:00
/* Exchanging signatures on closing tx. */
lightningd: peer state cleanup. 1. We explicitly assert what state we're coming from, to make transitions clearer. 2. Every transition has a state, even between owners while waiting for HSM. 3. Explictly step though getting the HSM signature on the funding tx before starting channeld, rather than doing it in parallel: makes states clearer. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-22 13:27:20 +02:00
CLOSINGD_SIGEXCHANGE,
lightningd: introduce peer_state enum. The actual state names are place holders for now, really. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-22 13:24:59 +02:00
lightningd: new peer state CLOSINGD_COMPLETE. This is a transitional state, while we're waiting to see the closing tx onchain (which is To Be Implemented). The simplest way to do re-transmission is to re-use closingd, and just disallow any updates. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-07-05 07:33:40 +02:00
/* Waiting for onchain event. */
CLOSINGD_COMPLETE,
lightningd: new state AWAITING_UNILATERAL. When in this state, we send a canned error "Awaiting unilateral close". We enter this both when we drop to chain, and when we're trying to get them to drop to chain due to option_data_loss_protect. As this state (unlike channel errors) is saved to the database, it means we will *never* talk to a peer again in this state, so they can't confuse us. Since we set this state in channel_fail_permanent() (which is the only place we call drop_to_chain for a unilateral close), we don't need to save to the db: channel_set_state() does that for us. This state change has a subtle effect: we return WIRE_UNKNOWN_NEXT_PEER instead of WIRE_TEMPORARY_CHANNEL_FAILURE as soon as we get a failure with a peer. To provoke a temporary failure in test_pay_disconnect we take the node offline. Reported-by: Christian Decker @cdecker Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-08-23 03:08:48 +02:00
/* Waiting for unilateral close to hit blockchain. */
AWAITING_UNILATERAL,
onchain: add initial onchain state. We have a race where we start onchaind, but state is unchanged, so checks like peer_control.c's: peer_ready = (peer->owner && peer->state == CHANNELD_AWAITING_LOCKIN); if (!peer_ready) { log_unusual(peer->log, "Funding tx confirmed, but peer state %s %s", peer_state_name(peer->state), peer->owner ? peer->owner->name : "unowned"); } else { subd_send_msg(peer->owner, take(towire_channel_funding_locked(peer, peer->scid))); } Can send to the wrong daemon. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-09-26 23:02:48 +02:00
/* We've seen the funding spent, we're waiting for onchaind. */
FUNDING_SPEND_SEEN,
channel_states: fold all the ONCHAIND states into one. The billboard is now far more useful to tell what's going on, and this gets us closer to a state == owner mapping. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-23 07:23:51 +01:00
/* On chain */
wallet: Add a final `CLOSED` state to channels Instead of deleting the channels we will simple mark them as `CLOSED` from now on. This is needed for some of the other tables not to end up with dangling references that would otherwise survive the channel lifetime, e.g., forwards and transactions. Signed-off-by: Christian Decker <decker.christian@gmail.com>
2019-06-22 14:49:30 +02:00
ONCHAIN,
/* Final state after we have fully settled on-chain */
CLOSED
lightningd: introduce peer_state enum. The actual state names are place holders for now, really. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-22 13:24:59 +02:00
};
wallet: Add a final `CLOSED` state to channels Instead of deleting the channels we will simple mark them as `CLOSED` from now on. This is needed for some of the other tables not to end up with dangling references that would otherwise survive the channel lifetime, e.g., forwards and transactions. Signed-off-by: Christian Decker <decker.christian@gmail.com>
2019-06-22 14:49:30 +02:00
#define CHANNEL_STATE_MAX CLOSED
lightningd: introduce peer_state enum. The actual state names are place holders for now, really. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2017-05-22 13:24:59 +02:00
lightningd: rename peer_state -> channel_state, remove OPENINGD. And now we can finally do the db upgrade to remove any OPENINGD channels once, since we never put them back. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2018-02-19 02:06:14 +01:00
#endif /* LIGHTNING_LIGHTNINGD_CHANNEL_STATE_H */
Reference in New Issue Copy Permalink