Pierre-Marie Padiou 202598d14e Introduce a specific funding status for zeroconf (#2598) ... We used to consider zero-conf funding txs as _confirmed_ as soon as they were _published_, but it was hacky. Before splices, it prevented RBF-ing zero-conf txs, which in theory make sense (we start using the channel without confirmations, but may still want to bump the fees later). After splices, it would prevent using a channel while a splice tx is pending confirmation (even if the channel isn't zero-conf). What we are really doing is separating the state of the channel, from the state of the blockchain. As a consequence the management of the funding tx is more independent from the channel FSM, which is why we end up with catch-all handlers for `WatchPublishedTriggered`/`WatchFundingConfirmedTriggered`. As a side effect, we also simplify how we put watchers: instead of putting them back at every connection, we do this once and for all (either when creating the channel, or at restart). --------- Co-authored-by: t-bast <bastuc@hotmail.fr>		2023-02-16 11:23:32 +01:00
..
main	Introduce a specific funding status for zeroconf (#2598)	2023-02-16 11:23:32 +01:00
test	Introduce a specific funding status for zeroconf (#2598)	2023-02-16 11:23:32 +01:00