From: Elias Rohrer Date: Tue, 16 Apr 2024 12:50:51 +0000 (+0200) Subject: Edit `Event::SpendableOutputs` docs to mention `OutputSweeper` X-Git-Tag: v0.0.123-beta~6^2 X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=commitdiff_plain;h=be8c0d099d9fe132727606cdf019fb21d1e5a6a5;hp=681106d23f9d801bd3a41d598e115dd477461d96;p=rust-lightning Edit `Event::SpendableOutputs` docs to mention `OutputSweeper` --- diff --git a/lightning/src/events/mod.rs b/lightning/src/events/mod.rs index f6e7f716..4d644fe4 100644 --- a/lightning/src/events/mod.rs +++ b/lightning/src/events/mod.rs @@ -792,9 +792,15 @@ pub enum Event { }, /// Used to indicate that an output which you should know how to spend was confirmed on chain /// and is now spendable. - /// Such an output will *not* ever be spent by rust-lightning, and are not at risk of your + /// + /// Such an output will *never* be spent directly by LDK, and are not at risk of your /// counterparty spending them due to some kind of timeout. Thus, you need to store them /// somewhere and spend them when you create on-chain transactions. + /// + /// You may hand them to the [`OutputSweeper`] utility which will store and (re-)generate spending + /// transactions for you. + /// + /// [`OutputSweeper`]: crate::util::sweep::OutputSweeper SpendableOutputs { /// The outputs which you should store as spendable by you. outputs: Vec,