1 // This file is Copyright its original authors, visible in version control
4 // This file is licensed under the Apache License, Version 2.0 <LICENSE-APACHE
5 // or http://www.apache.org/licenses/LICENSE-2.0> or the MIT license
6 // <LICENSE-MIT or http://opensource.org/licenses/MIT>, at your option.
7 // You may not use this file except in accordance with one or both of these
10 //! Events are returned from various bits in the library which indicate some action must be taken
13 //! Because we don't have a built-in runtime, it's up to the client to call events at a time in the
14 //! future, as well as generate and broadcast funding transactions handle payment preimages and a
17 use crate::chain::keysinterface::SpendableOutputDescriptor;
19 use crate::ln::chan_utils::HTLCOutputInCommitment;
20 use crate::ln::channelmanager::PaymentId;
21 use crate::ln::channel::FUNDING_CONF_DEADLINE_BLOCKS;
22 use crate::ln::features::ChannelTypeFeatures;
24 use crate::ln::msgs::DecodeError;
25 use crate::ln::{PaymentPreimage, PaymentHash, PaymentSecret};
26 use crate::routing::gossip::NetworkUpdate;
27 use crate::util::ser::{BigSize, FixedLengthReader, Writeable, Writer, MaybeReadable, Readable, WithoutLength, OptionDeserWrapper};
28 use crate::routing::router::{RouteHop, RouteParameters};
30 use bitcoin::{PackedLockTime, Transaction};
32 use bitcoin::OutPoint;
33 use bitcoin::blockdata::script::Script;
34 use bitcoin::hashes::Hash;
35 use bitcoin::hashes::sha256::Hash as Sha256;
36 use bitcoin::secp256k1::PublicKey;
38 use crate::prelude::*;
39 use core::time::Duration;
43 /// Some information provided on receipt of payment depends on whether the payment received is a
44 /// spontaneous payment or a "conventional" lightning payment that's paying an invoice.
45 #[derive(Clone, Debug)]
46 pub enum PaymentPurpose {
47 /// Information for receiving a payment that we generated an invoice for.
49 /// The preimage to the payment_hash, if the payment hash (and secret) were fetched via
50 /// [`ChannelManager::create_inbound_payment`]. If provided, this can be handed directly to
51 /// [`ChannelManager::claim_funds`].
53 /// [`ChannelManager::create_inbound_payment`]: crate::ln::channelmanager::ChannelManager::create_inbound_payment
54 /// [`ChannelManager::claim_funds`]: crate::ln::channelmanager::ChannelManager::claim_funds
55 payment_preimage: Option<PaymentPreimage>,
56 /// The "payment secret". This authenticates the sender to the recipient, preventing a
57 /// number of deanonymization attacks during the routing process.
58 /// It is provided here for your reference, however its accuracy is enforced directly by
59 /// [`ChannelManager`] using the values you previously provided to
60 /// [`ChannelManager::create_inbound_payment`] or
61 /// [`ChannelManager::create_inbound_payment_for_hash`].
63 /// [`ChannelManager`]: crate::ln::channelmanager::ChannelManager
64 /// [`ChannelManager::create_inbound_payment`]: crate::ln::channelmanager::ChannelManager::create_inbound_payment
65 /// [`ChannelManager::create_inbound_payment_for_hash`]: crate::ln::channelmanager::ChannelManager::create_inbound_payment_for_hash
66 payment_secret: PaymentSecret,
68 /// Because this is a spontaneous payment, the payer generated their own preimage rather than us
69 /// (the payee) providing a preimage.
70 SpontaneousPayment(PaymentPreimage),
73 impl_writeable_tlv_based_enum!(PaymentPurpose,
74 (0, InvoicePayment) => {
75 (0, payment_preimage, option),
76 (2, payment_secret, required),
78 (2, SpontaneousPayment)
81 #[derive(Clone, Debug, PartialEq, Eq)]
82 /// The reason the channel was closed. See individual variants more details.
83 pub enum ClosureReason {
84 /// Closure generated from receiving a peer error message.
86 /// Our counterparty may have broadcasted their latest commitment state, and we have
88 CounterpartyForceClosed {
89 /// The error which the peer sent us.
91 /// The string should be sanitized before it is used (e.g emitted to logs
92 /// or printed to stdout). Otherwise, a well crafted error message may exploit
93 /// a security vulnerability in the terminal emulator or the logging subsystem.
96 /// Closure generated from [`ChannelManager::force_close_channel`], called by the user.
98 /// [`ChannelManager::force_close_channel`]: crate::ln::channelmanager::ChannelManager::force_close_channel.
100 /// The channel was closed after negotiating a cooperative close and we've now broadcasted
101 /// the cooperative close transaction. Note the shutdown may have been initiated by us.
102 //TODO: split between CounterpartyInitiated/LocallyInitiated
104 /// A commitment transaction was confirmed on chain, closing the channel. Most likely this
105 /// commitment transaction came from our counterparty, but it may also have come from
106 /// a copy of our own `ChannelMonitor`.
107 CommitmentTxConfirmed,
108 /// The funding transaction failed to confirm in a timely manner on an inbound channel.
110 /// Closure generated from processing an event, likely a HTLC forward/relay/reception.
112 /// A developer-readable error message which we generated.
115 /// The peer disconnected prior to funding completing. In this case the spec mandates that we
116 /// forget the channel entirely - we can attempt again if the peer reconnects.
118 /// This includes cases where we restarted prior to funding completion, including prior to the
119 /// initial [`ChannelMonitor`] persistence completing.
121 /// In LDK versions prior to 0.0.107 this could also occur if we were unable to connect to the
122 /// peer because of mutual incompatibility between us and our channel counterparty.
124 /// [`ChannelMonitor`]: crate::chain::channelmonitor::ChannelMonitor
126 /// Closure generated from `ChannelManager::read` if the [`ChannelMonitor`] is newer than
127 /// the [`ChannelManager`] deserialized.
129 /// [`ChannelMonitor`]: crate::chain::channelmonitor::ChannelMonitor
130 /// [`ChannelManager`]: crate::ln::channelmanager::ChannelManager
131 OutdatedChannelManager
134 impl core::fmt::Display for ClosureReason {
135 fn fmt(&self, f: &mut core::fmt::Formatter) -> Result<(), core::fmt::Error> {
136 f.write_str("Channel closed because ")?;
138 ClosureReason::CounterpartyForceClosed { peer_msg } => {
139 f.write_str("counterparty force-closed with message ")?;
140 f.write_str(&peer_msg)
142 ClosureReason::HolderForceClosed => f.write_str("user manually force-closed the channel"),
143 ClosureReason::CooperativeClosure => f.write_str("the channel was cooperatively closed"),
144 ClosureReason::CommitmentTxConfirmed => f.write_str("commitment or closing transaction was confirmed on chain."),
145 ClosureReason::FundingTimedOut => write!(f, "funding transaction failed to confirm within {} blocks", FUNDING_CONF_DEADLINE_BLOCKS),
146 ClosureReason::ProcessingError { err } => {
147 f.write_str("of an exception: ")?;
150 ClosureReason::DisconnectedPeer => f.write_str("the peer disconnected prior to the channel being funded"),
151 ClosureReason::OutdatedChannelManager => f.write_str("the ChannelManager read from disk was stale compared to ChannelMonitor(s)"),
156 impl_writeable_tlv_based_enum_upgradable!(ClosureReason,
157 (0, CounterpartyForceClosed) => { (1, peer_msg, required) },
158 (1, FundingTimedOut) => {},
159 (2, HolderForceClosed) => {},
160 (6, CommitmentTxConfirmed) => {},
161 (4, CooperativeClosure) => {},
162 (8, ProcessingError) => { (1, err, required) },
163 (10, DisconnectedPeer) => {},
164 (12, OutdatedChannelManager) => {},
167 /// Intended destination of a failed HTLC as indicated in [`Event::HTLCHandlingFailed`].
168 #[derive(Clone, Debug, PartialEq, Eq)]
169 pub enum HTLCDestination {
170 /// We tried forwarding to a channel but failed to do so. An example of such an instance is when
171 /// there is insufficient capacity in our outbound channel.
173 /// The `node_id` of the next node. For backwards compatibility, this field is
174 /// marked as optional, versions prior to 0.0.110 may not always be able to provide
175 /// counterparty node information.
176 node_id: Option<PublicKey>,
177 /// The outgoing `channel_id` between us and the next node.
178 channel_id: [u8; 32],
180 /// Scenario where we are unsure of the next node to forward the HTLC to.
182 /// Short channel id we are requesting to forward an HTLC to.
183 requested_forward_scid: u64,
185 /// Failure scenario where an HTLC may have been forwarded to be intended for us,
186 /// but is invalid for some reason, so we reject it.
188 /// Some of the reasons may include:
190 /// * Expected MPP amount to claim does not equal HTLC total
191 /// * Claimable amount does not match expected amount
193 /// The payment hash of the payment we attempted to process.
194 payment_hash: PaymentHash
198 impl_writeable_tlv_based_enum_upgradable!(HTLCDestination,
199 (0, NextHopChannel) => {
200 (0, node_id, required),
201 (2, channel_id, required),
203 (2, UnknownNextHop) => {
204 (0, requested_forward_scid, required),
206 (4, FailedPayment) => {
207 (0, payment_hash, required),
212 /// A descriptor used to sign for a commitment transaction's anchor output.
213 #[derive(Clone, Debug)]
214 pub struct AnchorDescriptor {
215 /// A unique identifier used along with `channel_value_satoshis` to re-derive the
216 /// [`InMemorySigner`] required to sign `input`.
218 /// [`InMemorySigner`]: crate::chain::keysinterface::InMemorySigner
219 pub channel_keys_id: [u8; 32],
220 /// The value in satoshis of the channel we're attempting to spend the anchor output of. This is
221 /// used along with `channel_keys_id` to re-derive the [`InMemorySigner`] required to sign
224 /// [`InMemorySigner`]: crate::chain::keysinterface::InMemorySigner
225 pub channel_value_satoshis: u64,
226 /// The transaction input's outpoint corresponding to the commitment transaction's anchor
228 pub outpoint: OutPoint,
232 /// Represents the different types of transactions, originating from LDK, to be bumped.
233 #[derive(Clone, Debug)]
234 pub enum BumpTransactionEvent {
235 /// Indicates that a channel featuring anchor outputs is to be closed by broadcasting the local
236 /// commitment transaction. Since commitment transactions have a static feerate pre-agreed upon,
237 /// they may need additional fees to be attached through a child transaction using the popular
238 /// [Child-Pays-For-Parent](https://bitcoinops.org/en/topics/cpfp) fee bumping technique. This
239 /// child transaction must include the anchor input described within `anchor_descriptor` along
240 /// with additional inputs to meet the target feerate. Failure to meet the target feerate
241 /// decreases the confirmation odds of the transaction package (which includes the commitment
242 /// and child anchor transactions), possibly resulting in a loss of funds. Once the transaction
243 /// is constructed, it must be fully signed for and broadcasted by the consumer of the event
244 /// along with the `commitment_tx` enclosed. Note that the `commitment_tx` must always be
245 /// broadcast first, as the child anchor transaction depends on it.
247 /// The consumer should be able to sign for any of the additional inputs included within the
248 /// child anchor transaction. To sign its anchor input, an [`InMemorySigner`] should be
249 /// re-derived through [`KeysManager::derive_channel_keys`] with the help of
250 /// [`AnchorDescriptor::channel_keys_id`] and [`AnchorDescriptor::channel_value_satoshis`].
252 /// It is possible to receive more than one instance of this event if a valid child anchor
253 /// transaction is never broadcast or is but not with a sufficient fee to be mined. Care should
254 /// be taken by the consumer of the event to ensure any future iterations of the child anchor
255 /// transaction adhere to the [Replace-By-Fee
256 /// rules](https://github.com/bitcoin/bitcoin/blob/master/doc/policy/mempool-replacements.md)
257 /// for fee bumps to be accepted into the mempool, and eventually the chain. As the frequency of
258 /// these events is not user-controlled, users may ignore/drop the event if they are no longer
259 /// able to commit external confirmed funds to the child anchor transaction.
261 /// The set of `pending_htlcs` on the commitment transaction to be broadcast can be inspected to
262 /// determine whether a significant portion of the channel's funds are allocated to HTLCs,
263 /// enabling users to make their own decisions regarding the importance of the commitment
264 /// transaction's confirmation. Note that this is not required, but simply exists as an option
265 /// for users to override LDK's behavior. On commitments with no HTLCs (indicated by those with
266 /// an empty `pending_htlcs`), confirmation of the commitment transaction can be considered to
269 /// [`InMemorySigner`]: crate::chain::keysinterface::InMemorySigner
270 /// [`KeysManager::derive_channel_keys`]: crate::chain::keysinterface::KeysManager::derive_channel_keys
272 /// The target feerate that the transaction package, which consists of the commitment
273 /// transaction and the to-be-crafted child anchor transaction, must meet.
274 package_target_feerate_sat_per_1000_weight: u32,
275 /// The channel's commitment transaction to bump the fee of. This transaction should be
276 /// broadcast along with the anchor transaction constructed as a result of consuming this
278 commitment_tx: Transaction,
279 /// The absolute fee in satoshis of the commitment transaction. This can be used along the
280 /// with weight of the commitment transaction to determine its feerate.
281 commitment_tx_fee_satoshis: u64,
282 /// The descriptor to sign the anchor input of the anchor transaction constructed as a
283 /// result of consuming this event.
284 anchor_descriptor: AnchorDescriptor,
285 /// The set of pending HTLCs on the commitment transaction that need to be resolved once the
286 /// commitment transaction confirms.
287 pending_htlcs: Vec<HTLCOutputInCommitment>,
291 /// An Event which you should probably take some action in response to.
293 /// Note that while Writeable and Readable are implemented for Event, you probably shouldn't use
294 /// them directly as they don't round-trip exactly (for example FundingGenerationReady is never
295 /// written as it makes no sense to respond to it after reconnecting to peers).
296 #[derive(Clone, Debug)]
298 /// Used to indicate that the client should generate a funding transaction with the given
299 /// parameters and then call [`ChannelManager::funding_transaction_generated`].
300 /// Generated in [`ChannelManager`] message handling.
301 /// Note that *all inputs* in the funding transaction must spend SegWit outputs or your
302 /// counterparty can steal your funds!
304 /// [`ChannelManager`]: crate::ln::channelmanager::ChannelManager
305 /// [`ChannelManager::funding_transaction_generated`]: crate::ln::channelmanager::ChannelManager::funding_transaction_generated
306 FundingGenerationReady {
307 /// The random channel_id we picked which you'll need to pass into
308 /// [`ChannelManager::funding_transaction_generated`].
310 /// [`ChannelManager::funding_transaction_generated`]: crate::ln::channelmanager::ChannelManager::funding_transaction_generated
311 temporary_channel_id: [u8; 32],
312 /// The counterparty's node_id, which you'll need to pass back into
313 /// [`ChannelManager::funding_transaction_generated`].
315 /// [`ChannelManager::funding_transaction_generated`]: crate::ln::channelmanager::ChannelManager::funding_transaction_generated
316 counterparty_node_id: PublicKey,
317 /// The value, in satoshis, that the output should have.
318 channel_value_satoshis: u64,
319 /// The script which should be used in the transaction output.
320 output_script: Script,
321 /// The `user_channel_id` value passed in to [`ChannelManager::create_channel`], or a
322 /// random value for an inbound channel. This may be zero for objects serialized with LDK
323 /// versions prior to 0.0.113.
325 /// [`ChannelManager::create_channel`]: crate::ln::channelmanager::ChannelManager::create_channel
326 user_channel_id: u128,
328 /// Indicates we've received (an offer of) money! Just gotta dig out that payment preimage and
329 /// feed it to [`ChannelManager::claim_funds`] to get it....
331 /// Note that if the preimage is not known, you should call
332 /// [`ChannelManager::fail_htlc_backwards`] to free up resources for this HTLC and avoid
333 /// network congestion.
334 /// If you fail to call either [`ChannelManager::claim_funds`] or
335 /// [`ChannelManager::fail_htlc_backwards`] within the HTLC's timeout, the HTLC will be
336 /// automatically failed.
339 /// LDK will not stop an inbound payment from being paid multiple times, so multiple
340 /// `PaymentReceived` events may be generated for the same payment.
342 /// [`ChannelManager::claim_funds`]: crate::ln::channelmanager::ChannelManager::claim_funds
343 /// [`ChannelManager::fail_htlc_backwards`]: crate::ln::channelmanager::ChannelManager::fail_htlc_backwards
345 /// The hash for which the preimage should be handed to the ChannelManager. Note that LDK will
346 /// not stop you from registering duplicate payment hashes for inbound payments.
347 payment_hash: PaymentHash,
348 /// The value, in thousandths of a satoshi, that this payment is for.
350 /// Information for claiming this received payment, based on whether the purpose of the
351 /// payment is to pay an invoice or to send a spontaneous payment.
352 purpose: PaymentPurpose,
354 /// Indicates a payment has been claimed and we've received money!
356 /// This most likely occurs when [`ChannelManager::claim_funds`] has been called in response
357 /// to an [`Event::PaymentReceived`]. However, if we previously crashed during a
358 /// [`ChannelManager::claim_funds`] call you may see this event without a corresponding
359 /// [`Event::PaymentReceived`] event.
362 /// LDK will not stop an inbound payment from being paid multiple times, so multiple
363 /// `PaymentReceived` events may be generated for the same payment. If you then call
364 /// [`ChannelManager::claim_funds`] twice for the same [`Event::PaymentReceived`] you may get
365 /// multiple `PaymentClaimed` events.
367 /// [`ChannelManager::claim_funds`]: crate::ln::channelmanager::ChannelManager::claim_funds
369 /// The payment hash of the claimed payment. Note that LDK will not stop you from
370 /// registering duplicate payment hashes for inbound payments.
371 payment_hash: PaymentHash,
372 /// The value, in thousandths of a satoshi, that this payment is for.
374 /// The purpose of this claimed payment, i.e. whether the payment was for an invoice or a
375 /// spontaneous payment.
376 purpose: PaymentPurpose,
378 /// Indicates an outbound payment we made succeeded (i.e. it made it all the way to its target
379 /// and we got back the payment preimage for it).
381 /// Note for MPP payments: in rare cases, this event may be preceded by a `PaymentPathFailed`
382 /// event. In this situation, you SHOULD treat this payment as having succeeded.
384 /// The id returned by [`ChannelManager::send_payment`] and used with
385 /// [`ChannelManager::retry_payment`].
387 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
388 /// [`ChannelManager::retry_payment`]: crate::ln::channelmanager::ChannelManager::retry_payment
389 payment_id: Option<PaymentId>,
390 /// The preimage to the hash given to ChannelManager::send_payment.
391 /// Note that this serves as a payment receipt, if you wish to have such a thing, you must
392 /// store it somehow!
393 payment_preimage: PaymentPreimage,
394 /// The hash that was given to [`ChannelManager::send_payment`].
396 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
397 payment_hash: PaymentHash,
398 /// The total fee which was spent at intermediate hops in this payment, across all paths.
400 /// Note that, like [`Route::get_total_fees`] this does *not* include any potential
401 /// overpayment to the recipient node.
403 /// If the recipient or an intermediate node misbehaves and gives us free money, this may
404 /// overstate the amount paid, though this is unlikely.
406 /// [`Route::get_total_fees`]: crate::routing::router::Route::get_total_fees
407 fee_paid_msat: Option<u64>,
409 /// Indicates an outbound payment failed. Individual [`Event::PaymentPathFailed`] events
410 /// provide failure information for each MPP part in the payment.
412 /// This event is provided once there are no further pending HTLCs for the payment and the
413 /// payment is no longer retryable due to [`ChannelManager::abandon_payment`] having been
414 /// called for the corresponding payment.
416 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
418 /// The id returned by [`ChannelManager::send_payment`] and used with
419 /// [`ChannelManager::retry_payment`] and [`ChannelManager::abandon_payment`].
421 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
422 /// [`ChannelManager::retry_payment`]: crate::ln::channelmanager::ChannelManager::retry_payment
423 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
424 payment_id: PaymentId,
425 /// The hash that was given to [`ChannelManager::send_payment`].
427 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
428 payment_hash: PaymentHash,
430 /// Indicates that a path for an outbound payment was successful.
432 /// Always generated after [`Event::PaymentSent`] and thus useful for scoring channels. See
433 /// [`Event::PaymentSent`] for obtaining the payment preimage.
434 PaymentPathSuccessful {
435 /// The id returned by [`ChannelManager::send_payment`] and used with
436 /// [`ChannelManager::retry_payment`].
438 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
439 /// [`ChannelManager::retry_payment`]: crate::ln::channelmanager::ChannelManager::retry_payment
440 payment_id: PaymentId,
441 /// The hash that was given to [`ChannelManager::send_payment`].
443 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
444 payment_hash: Option<PaymentHash>,
445 /// The payment path that was successful.
447 /// May contain a closed channel if the HTLC sent along the path was fulfilled on chain.
450 /// Indicates an outbound HTLC we sent failed. Probably some intermediary node dropped
451 /// something. You may wish to retry with a different route.
453 /// If you have given up retrying this payment and wish to fail it, you MUST call
454 /// [`ChannelManager::abandon_payment`] at least once for a given [`PaymentId`] or memory
455 /// related to payment tracking will leak.
457 /// Note that this does *not* indicate that all paths for an MPP payment have failed, see
458 /// [`Event::PaymentFailed`] and [`all_paths_failed`].
460 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
461 /// [`all_paths_failed`]: Self::PaymentPathFailed::all_paths_failed
463 /// The id returned by [`ChannelManager::send_payment`] and used with
464 /// [`ChannelManager::retry_payment`] and [`ChannelManager::abandon_payment`].
466 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
467 /// [`ChannelManager::retry_payment`]: crate::ln::channelmanager::ChannelManager::retry_payment
468 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
469 payment_id: Option<PaymentId>,
470 /// The hash that was given to [`ChannelManager::send_payment`].
472 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
473 payment_hash: PaymentHash,
474 /// Indicates the payment was rejected for some reason by the recipient. This implies that
475 /// the payment has failed, not just the route in question. If this is not set, you may
476 /// retry the payment via a different route.
477 payment_failed_permanently: bool,
478 /// Any failure information conveyed via the Onion return packet by a node along the failed
481 /// Should be applied to the [`NetworkGraph`] so that routing decisions can take into
482 /// account the update.
484 /// [`NetworkGraph`]: crate::routing::gossip::NetworkGraph
485 network_update: Option<NetworkUpdate>,
486 /// For both single-path and multi-path payments, this is set if all paths of the payment have
487 /// failed. This will be set to false if (1) this is an MPP payment and (2) other parts of the
488 /// larger MPP payment were still in flight when this event was generated.
490 /// Note that if you are retrying individual MPP parts, using this value to determine if a
491 /// payment has fully failed is race-y. Because multiple failures can happen prior to events
492 /// being processed, you may retry in response to a first failure, with a second failure
493 /// (with `all_paths_failed` set) still pending. Then, when the second failure is processed
494 /// you will see `all_paths_failed` set even though the retry of the first failure still
495 /// has an associated in-flight HTLC. See (1) for an example of such a failure.
497 /// If you wish to retry individual MPP parts and learn when a payment has failed, you must
498 /// call [`ChannelManager::abandon_payment`] and wait for a [`Event::PaymentFailed`] event.
500 /// (1) <https://github.com/lightningdevkit/rust-lightning/issues/1164>
502 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
503 all_paths_failed: bool,
504 /// The payment path that failed.
506 /// The channel responsible for the failed payment path.
508 /// Note that for route hints or for the first hop in a path this may be an SCID alias and
509 /// may not refer to a channel in the public network graph. These aliases may also collide
510 /// with channels in the public network graph.
512 /// If this is `Some`, then the corresponding channel should be avoided when the payment is
513 /// retried. May be `None` for older [`Event`] serializations.
514 short_channel_id: Option<u64>,
515 /// Parameters needed to compute a new [`Route`] when retrying the failed payment path.
517 /// See [`find_route`] for details.
519 /// [`Route`]: crate::routing::router::Route
520 /// [`find_route`]: crate::routing::router::find_route
521 retry: Option<RouteParameters>,
523 error_code: Option<u16>,
525 error_data: Option<Vec<u8>>,
527 /// Indicates that a probe payment we sent returned successful, i.e., only failed at the destination.
529 /// The id returned by [`ChannelManager::send_probe`].
531 /// [`ChannelManager::send_probe`]: crate::ln::channelmanager::ChannelManager::send_probe
532 payment_id: PaymentId,
533 /// The hash generated by [`ChannelManager::send_probe`].
535 /// [`ChannelManager::send_probe`]: crate::ln::channelmanager::ChannelManager::send_probe
536 payment_hash: PaymentHash,
537 /// The payment path that was successful.
540 /// Indicates that a probe payment we sent failed at an intermediary node on the path.
542 /// The id returned by [`ChannelManager::send_probe`].
544 /// [`ChannelManager::send_probe`]: crate::ln::channelmanager::ChannelManager::send_probe
545 payment_id: PaymentId,
546 /// The hash generated by [`ChannelManager::send_probe`].
548 /// [`ChannelManager::send_probe`]: crate::ln::channelmanager::ChannelManager::send_probe
549 payment_hash: PaymentHash,
550 /// The payment path that failed.
552 /// The channel responsible for the failed probe.
554 /// Note that for route hints or for the first hop in a path this may be an SCID alias and
555 /// may not refer to a channel in the public network graph. These aliases may also collide
556 /// with channels in the public network graph.
557 short_channel_id: Option<u64>,
559 /// Used to indicate that [`ChannelManager::process_pending_htlc_forwards`] should be called at
560 /// a time in the future.
562 /// [`ChannelManager::process_pending_htlc_forwards`]: crate::ln::channelmanager::ChannelManager::process_pending_htlc_forwards
563 PendingHTLCsForwardable {
564 /// The minimum amount of time that should be waited prior to calling
565 /// process_pending_htlc_forwards. To increase the effort required to correlate payments,
566 /// you should wait a random amount of time in roughly the range (now + time_forwardable,
567 /// now + 5*time_forwardable).
568 time_forwardable: Duration,
570 /// Used to indicate that an output which you should know how to spend was confirmed on chain
571 /// and is now spendable.
572 /// Such an output will *not* ever be spent by rust-lightning, and are not at risk of your
573 /// counterparty spending them due to some kind of timeout. Thus, you need to store them
574 /// somewhere and spend them when you create on-chain transactions.
576 /// The outputs which you should store as spendable by you.
577 outputs: Vec<SpendableOutputDescriptor>,
579 /// This event is generated when a payment has been successfully forwarded through us and a
580 /// forwarding fee earned.
582 /// The incoming channel between the previous node and us. This is only `None` for events
583 /// generated or serialized by versions prior to 0.0.107.
584 prev_channel_id: Option<[u8; 32]>,
585 /// The outgoing channel between the next node and us. This is only `None` for events
586 /// generated or serialized by versions prior to 0.0.107.
587 next_channel_id: Option<[u8; 32]>,
588 /// The fee, in milli-satoshis, which was earned as a result of the payment.
590 /// Note that if we force-closed the channel over which we forwarded an HTLC while the HTLC
591 /// was pending, the amount the next hop claimed will have been rounded down to the nearest
592 /// whole satoshi. Thus, the fee calculated here may be higher than expected as we still
593 /// claimed the full value in millisatoshis from the source. In this case,
594 /// `claim_from_onchain_tx` will be set.
596 /// If the channel which sent us the payment has been force-closed, we will claim the funds
597 /// via an on-chain transaction. In that case we do not yet know the on-chain transaction
598 /// fees which we will spend and will instead set this to `None`. It is possible duplicate
599 /// `PaymentForwarded` events are generated for the same payment iff `fee_earned_msat` is
601 fee_earned_msat: Option<u64>,
602 /// If this is `true`, the forwarded HTLC was claimed by our counterparty via an on-chain
604 claim_from_onchain_tx: bool,
606 /// Used to indicate that a channel with the given `channel_id` is ready to
607 /// be used. This event is emitted either when the funding transaction has been confirmed
608 /// on-chain, or, in case of a 0conf channel, when both parties have confirmed the channel
611 /// The channel_id of the channel that is ready.
612 channel_id: [u8; 32],
613 /// The `user_channel_id` value passed in to [`ChannelManager::create_channel`] for outbound
614 /// channels, or to [`ChannelManager::accept_inbound_channel`] for inbound channels if
615 /// [`UserConfig::manually_accept_inbound_channels`] config flag is set to true. Otherwise
616 /// `user_channel_id` will be randomized for an inbound channel.
618 /// [`ChannelManager::create_channel`]: crate::ln::channelmanager::ChannelManager::create_channel
619 /// [`ChannelManager::accept_inbound_channel`]: crate::ln::channelmanager::ChannelManager::accept_inbound_channel
620 /// [`UserConfig::manually_accept_inbound_channels`]: crate::util::config::UserConfig::manually_accept_inbound_channels
621 user_channel_id: u128,
622 /// The node_id of the channel counterparty.
623 counterparty_node_id: PublicKey,
624 /// The features that this channel will operate with.
625 channel_type: ChannelTypeFeatures,
627 /// Used to indicate that a previously opened channel with the given `channel_id` is in the
628 /// process of closure.
630 /// The channel_id of the channel which has been closed. Note that on-chain transactions
631 /// resolving the channel are likely still awaiting confirmation.
632 channel_id: [u8; 32],
633 /// The `user_channel_id` value passed in to [`ChannelManager::create_channel`] for outbound
634 /// channels, or to [`ChannelManager::accept_inbound_channel`] for inbound channels if
635 /// [`UserConfig::manually_accept_inbound_channels`] config flag is set to true. Otherwise
636 /// `user_channel_id` will be randomized for inbound channels.
637 /// This may be zero for inbound channels serialized prior to 0.0.113 and will always be
638 /// zero for objects serialized with LDK versions prior to 0.0.102.
640 /// [`ChannelManager::create_channel`]: crate::ln::channelmanager::ChannelManager::create_channel
641 /// [`ChannelManager::accept_inbound_channel`]: crate::ln::channelmanager::ChannelManager::accept_inbound_channel
642 /// [`UserConfig::manually_accept_inbound_channels`]: crate::util::config::UserConfig::manually_accept_inbound_channels
643 user_channel_id: u128,
644 /// The reason the channel was closed.
645 reason: ClosureReason
647 /// Used to indicate to the user that they can abandon the funding transaction and recycle the
648 /// inputs for another purpose.
650 /// The channel_id of the channel which has been closed.
651 channel_id: [u8; 32],
652 /// The full transaction received from the user
653 transaction: Transaction
655 /// Indicates a request to open a new channel by a peer.
657 /// To accept the request, call [`ChannelManager::accept_inbound_channel`]. To reject the
658 /// request, call [`ChannelManager::force_close_without_broadcasting_txn`].
660 /// The event is only triggered when a new open channel request is received and the
661 /// [`UserConfig::manually_accept_inbound_channels`] config flag is set to true.
663 /// [`ChannelManager::accept_inbound_channel`]: crate::ln::channelmanager::ChannelManager::accept_inbound_channel
664 /// [`ChannelManager::force_close_without_broadcasting_txn`]: crate::ln::channelmanager::ChannelManager::force_close_without_broadcasting_txn
665 /// [`UserConfig::manually_accept_inbound_channels`]: crate::util::config::UserConfig::manually_accept_inbound_channels
667 /// The temporary channel ID of the channel requested to be opened.
669 /// When responding to the request, the `temporary_channel_id` should be passed
670 /// back to the ChannelManager through [`ChannelManager::accept_inbound_channel`] to accept,
671 /// or through [`ChannelManager::force_close_without_broadcasting_txn`] to reject.
673 /// [`ChannelManager::accept_inbound_channel`]: crate::ln::channelmanager::ChannelManager::accept_inbound_channel
674 /// [`ChannelManager::force_close_without_broadcasting_txn`]: crate::ln::channelmanager::ChannelManager::force_close_without_broadcasting_txn
675 temporary_channel_id: [u8; 32],
676 /// The node_id of the counterparty requesting to open the channel.
678 /// When responding to the request, the `counterparty_node_id` should be passed
679 /// back to the `ChannelManager` through [`ChannelManager::accept_inbound_channel`] to
680 /// accept the request, or through [`ChannelManager::force_close_without_broadcasting_txn`] to reject the
683 /// [`ChannelManager::accept_inbound_channel`]: crate::ln::channelmanager::ChannelManager::accept_inbound_channel
684 /// [`ChannelManager::force_close_without_broadcasting_txn`]: crate::ln::channelmanager::ChannelManager::force_close_without_broadcasting_txn
685 counterparty_node_id: PublicKey,
686 /// The channel value of the requested channel.
687 funding_satoshis: u64,
688 /// Our starting balance in the channel if the request is accepted, in milli-satoshi.
690 /// The features that this channel will operate with. If you reject the channel, a
691 /// well-behaved counterparty may automatically re-attempt the channel with a new set of
694 /// Note that if [`ChannelTypeFeatures::supports_scid_privacy`] returns true on this type,
695 /// the resulting [`ChannelManager`] will not be readable by versions of LDK prior to
698 /// Furthermore, note that if [`ChannelTypeFeatures::supports_zero_conf`] returns true on this type,
699 /// the resulting [`ChannelManager`] will not be readable by versions of LDK prior to
700 /// 0.0.107. Channels setting this type also need to get manually accepted via
701 /// [`crate::ln::channelmanager::ChannelManager::accept_inbound_channel_from_trusted_peer_0conf`],
702 /// or will be rejected otherwise.
704 /// [`ChannelManager`]: crate::ln::channelmanager::ChannelManager
705 channel_type: ChannelTypeFeatures,
707 /// Indicates that the HTLC was accepted, but could not be processed when or after attempting to
710 /// Some scenarios where this event may be sent include:
711 /// * Insufficient capacity in the outbound channel
712 /// * While waiting to forward the HTLC, the channel it is meant to be forwarded through closes
713 /// * When an unknown SCID is requested for forwarding a payment.
714 /// * Claiming an amount for an MPP payment that exceeds the HTLC total
715 /// * The HTLC has timed out
717 /// This event, however, does not get generated if an HTLC fails to meet the forwarding
718 /// requirements (i.e. insufficient fees paid, or a CLTV that is too soon).
720 /// The channel over which the HTLC was received.
721 prev_channel_id: [u8; 32],
722 /// Destination of the HTLC that failed to be processed.
723 failed_next_destination: HTLCDestination,
726 /// Indicates that a transaction originating from LDK needs to have its fee bumped. This event
727 /// requires confirmed external funds to be readily available to spend.
729 /// LDK does not currently generate this event. It is limited to the scope of channels with
730 /// anchor outputs, which will be introduced in a future release.
731 BumpTransaction(BumpTransactionEvent),
734 impl Writeable for Event {
735 fn write<W: Writer>(&self, writer: &mut W) -> Result<(), io::Error> {
737 &Event::FundingGenerationReady { .. } => {
739 // We never write out FundingGenerationReady events as, upon disconnection, peers
740 // drop any channels which have not yet exchanged funding_signed.
742 &Event::PaymentReceived { ref payment_hash, ref amount_msat, ref purpose } => {
744 let mut payment_secret = None;
745 let payment_preimage;
747 PaymentPurpose::InvoicePayment { payment_preimage: preimage, payment_secret: secret } => {
748 payment_secret = Some(secret);
749 payment_preimage = *preimage;
751 PaymentPurpose::SpontaneousPayment(preimage) => {
752 payment_preimage = Some(*preimage);
755 write_tlv_fields!(writer, {
756 (0, payment_hash, required),
757 (2, payment_secret, option),
758 (4, amount_msat, required),
759 (6, 0u64, required), // user_payment_id required for compatibility with 0.0.103 and earlier
760 (8, payment_preimage, option),
763 &Event::PaymentSent { ref payment_id, ref payment_preimage, ref payment_hash, ref fee_paid_msat } => {
765 write_tlv_fields!(writer, {
766 (0, payment_preimage, required),
767 (1, payment_hash, required),
768 (3, payment_id, option),
769 (5, fee_paid_msat, option),
772 &Event::PaymentPathFailed {
773 ref payment_id, ref payment_hash, ref payment_failed_permanently, ref network_update,
774 ref all_paths_failed, ref path, ref short_channel_id, ref retry,
782 error_code.write(writer)?;
784 error_data.write(writer)?;
785 write_tlv_fields!(writer, {
786 (0, payment_hash, required),
787 (1, network_update, option),
788 (2, payment_failed_permanently, required),
789 (3, all_paths_failed, required),
790 (5, *path, vec_type),
791 (7, short_channel_id, option),
793 (11, payment_id, option),
796 &Event::PendingHTLCsForwardable { time_forwardable: _ } => {
798 // Note that we now ignore these on the read end as we'll re-generate them in
799 // ChannelManager, we write them here only for backwards compatibility.
801 &Event::SpendableOutputs { ref outputs } => {
803 write_tlv_fields!(writer, {
804 (0, WithoutLength(outputs), required),
807 &Event::PaymentForwarded { fee_earned_msat, prev_channel_id, claim_from_onchain_tx, next_channel_id } => {
809 write_tlv_fields!(writer, {
810 (0, fee_earned_msat, option),
811 (1, prev_channel_id, option),
812 (2, claim_from_onchain_tx, required),
813 (3, next_channel_id, option),
816 &Event::ChannelClosed { ref channel_id, ref user_channel_id, ref reason } => {
818 // `user_channel_id` used to be a single u64 value. In order to remain backwards
819 // compatible with versions prior to 0.0.113, the u128 is serialized as two
820 // separate u64 values.
821 let user_channel_id_low = *user_channel_id as u64;
822 let user_channel_id_high = (*user_channel_id >> 64) as u64;
823 write_tlv_fields!(writer, {
824 (0, channel_id, required),
825 (1, user_channel_id_low, required),
826 (2, reason, required),
827 (3, user_channel_id_high, required),
830 &Event::DiscardFunding { ref channel_id, ref transaction } => {
832 write_tlv_fields!(writer, {
833 (0, channel_id, required),
834 (2, transaction, required)
837 &Event::PaymentPathSuccessful { ref payment_id, ref payment_hash, ref path } => {
839 write_tlv_fields!(writer, {
840 (0, payment_id, required),
841 (2, payment_hash, option),
845 &Event::PaymentFailed { ref payment_id, ref payment_hash } => {
847 write_tlv_fields!(writer, {
848 (0, payment_id, required),
849 (2, payment_hash, required),
852 &Event::OpenChannelRequest { .. } => {
854 // We never write the OpenChannelRequest events as, upon disconnection, peers
855 // drop any channels which have not yet exchanged funding_signed.
857 &Event::PaymentClaimed { ref payment_hash, ref amount_msat, ref purpose } => {
859 write_tlv_fields!(writer, {
860 (0, payment_hash, required),
861 (2, purpose, required),
862 (4, amount_msat, required),
865 &Event::ProbeSuccessful { ref payment_id, ref payment_hash, ref path } => {
867 write_tlv_fields!(writer, {
868 (0, payment_id, required),
869 (2, payment_hash, required),
873 &Event::ProbeFailed { ref payment_id, ref payment_hash, ref path, ref short_channel_id } => {
875 write_tlv_fields!(writer, {
876 (0, payment_id, required),
877 (2, payment_hash, required),
878 (4, *path, vec_type),
879 (6, short_channel_id, option),
882 &Event::HTLCHandlingFailed { ref prev_channel_id, ref failed_next_destination } => {
884 write_tlv_fields!(writer, {
885 (0, prev_channel_id, required),
886 (2, failed_next_destination, required),
890 &Event::BumpTransaction(ref event)=> {
893 // We never write the ChannelClose events as they'll be replayed upon restarting
894 // anyway if the commitment transaction remains unconfirmed.
895 BumpTransactionEvent::ChannelClose { .. } => {}
898 &Event::ChannelReady { ref channel_id, ref user_channel_id, ref counterparty_node_id, ref channel_type } => {
900 write_tlv_fields!(writer, {
901 (0, channel_id, required),
902 (2, user_channel_id, required),
903 (4, counterparty_node_id, required),
904 (6, channel_type, required),
907 // Note that, going forward, all new events must only write data inside of
908 // `write_tlv_fields`. Versions 0.0.101+ will ignore odd-numbered events that write
909 // data via `write_tlv_fields`.
914 impl MaybeReadable for Event {
915 fn read<R: io::Read>(reader: &mut R) -> Result<Option<Self>, msgs::DecodeError> {
916 match Readable::read(reader)? {
917 // Note that we do not write a length-prefixed TLV for FundingGenerationReady events,
918 // unlike all other events, thus we return immediately here.
922 let mut payment_hash = PaymentHash([0; 32]);
923 let mut payment_preimage = None;
924 let mut payment_secret = None;
925 let mut amount_msat = 0;
926 let mut _user_payment_id = None::<u64>; // For compatibility with 0.0.103 and earlier
927 read_tlv_fields!(reader, {
928 (0, payment_hash, required),
929 (2, payment_secret, option),
930 (4, amount_msat, required),
931 (6, _user_payment_id, option),
932 (8, payment_preimage, option),
934 let purpose = match payment_secret {
935 Some(secret) => PaymentPurpose::InvoicePayment {
937 payment_secret: secret
939 None if payment_preimage.is_some() => PaymentPurpose::SpontaneousPayment(payment_preimage.unwrap()),
940 None => return Err(msgs::DecodeError::InvalidValue),
942 Ok(Some(Event::PaymentReceived {
952 let mut payment_preimage = PaymentPreimage([0; 32]);
953 let mut payment_hash = None;
954 let mut payment_id = None;
955 let mut fee_paid_msat = None;
956 read_tlv_fields!(reader, {
957 (0, payment_preimage, required),
958 (1, payment_hash, option),
959 (3, payment_id, option),
960 (5, fee_paid_msat, option),
962 if payment_hash.is_none() {
963 payment_hash = Some(PaymentHash(Sha256::hash(&payment_preimage.0[..]).into_inner()));
965 Ok(Some(Event::PaymentSent {
968 payment_hash: payment_hash.unwrap(),
977 let error_code = Readable::read(reader)?;
979 let error_data = Readable::read(reader)?;
980 let mut payment_hash = PaymentHash([0; 32]);
981 let mut payment_failed_permanently = false;
982 let mut network_update = None;
983 let mut all_paths_failed = Some(true);
984 let mut path: Option<Vec<RouteHop>> = Some(vec![]);
985 let mut short_channel_id = None;
986 let mut retry = None;
987 let mut payment_id = None;
988 read_tlv_fields!(reader, {
989 (0, payment_hash, required),
990 (1, network_update, ignorable),
991 (2, payment_failed_permanently, required),
992 (3, all_paths_failed, option),
994 (7, short_channel_id, option),
996 (11, payment_id, option),
998 Ok(Some(Event::PaymentPathFailed {
1001 payment_failed_permanently,
1003 all_paths_failed: all_paths_failed.unwrap(),
1004 path: path.unwrap(),
1018 let mut outputs = WithoutLength(Vec::new());
1019 read_tlv_fields!(reader, {
1020 (0, outputs, required),
1022 Ok(Some(Event::SpendableOutputs { outputs: outputs.0 }))
1028 let mut fee_earned_msat = None;
1029 let mut prev_channel_id = None;
1030 let mut claim_from_onchain_tx = false;
1031 let mut next_channel_id = None;
1032 read_tlv_fields!(reader, {
1033 (0, fee_earned_msat, option),
1034 (1, prev_channel_id, option),
1035 (2, claim_from_onchain_tx, required),
1036 (3, next_channel_id, option),
1038 Ok(Some(Event::PaymentForwarded { fee_earned_msat, prev_channel_id, claim_from_onchain_tx, next_channel_id }))
1044 let mut channel_id = [0; 32];
1045 let mut reason = None;
1046 let mut user_channel_id_low_opt: Option<u64> = None;
1047 let mut user_channel_id_high_opt: Option<u64> = None;
1048 read_tlv_fields!(reader, {
1049 (0, channel_id, required),
1050 (1, user_channel_id_low_opt, option),
1051 (2, reason, ignorable),
1052 (3, user_channel_id_high_opt, option),
1054 if reason.is_none() { return Ok(None); }
1056 // `user_channel_id` used to be a single u64 value. In order to remain
1057 // backwards compatible with versions prior to 0.0.113, the u128 is serialized
1058 // as two separate u64 values.
1059 let user_channel_id = (user_channel_id_low_opt.unwrap_or(0) as u128) +
1060 ((user_channel_id_high_opt.unwrap_or(0) as u128) << 64);
1062 Ok(Some(Event::ChannelClosed { channel_id, user_channel_id, reason: reason.unwrap() }))
1068 let mut channel_id = [0; 32];
1069 let mut transaction = Transaction{ version: 2, lock_time: PackedLockTime::ZERO, input: Vec::new(), output: Vec::new() };
1070 read_tlv_fields!(reader, {
1071 (0, channel_id, required),
1072 (2, transaction, required),
1074 Ok(Some(Event::DiscardFunding { channel_id, transaction } ))
1080 let mut payment_id = PaymentId([0; 32]);
1081 let mut payment_hash = None;
1082 let mut path: Option<Vec<RouteHop>> = Some(vec![]);
1083 read_tlv_fields!(reader, {
1084 (0, payment_id, required),
1085 (2, payment_hash, option),
1086 (4, path, vec_type),
1088 Ok(Some(Event::PaymentPathSuccessful {
1091 path: path.unwrap(),
1098 let mut payment_hash = PaymentHash([0; 32]);
1099 let mut payment_id = PaymentId([0; 32]);
1100 read_tlv_fields!(reader, {
1101 (0, payment_id, required),
1102 (2, payment_hash, required),
1104 Ok(Some(Event::PaymentFailed {
1112 // Value 17 is used for `Event::OpenChannelRequest`.
1117 let mut payment_hash = PaymentHash([0; 32]);
1118 let mut purpose = None;
1119 let mut amount_msat = 0;
1120 read_tlv_fields!(reader, {
1121 (0, payment_hash, required),
1122 (2, purpose, ignorable),
1123 (4, amount_msat, required),
1125 if purpose.is_none() { return Ok(None); }
1126 Ok(Some(Event::PaymentClaimed {
1128 purpose: purpose.unwrap(),
1136 let mut payment_id = PaymentId([0; 32]);
1137 let mut payment_hash = PaymentHash([0; 32]);
1138 let mut path: Option<Vec<RouteHop>> = Some(vec![]);
1139 read_tlv_fields!(reader, {
1140 (0, payment_id, required),
1141 (2, payment_hash, required),
1142 (4, path, vec_type),
1144 Ok(Some(Event::ProbeSuccessful {
1147 path: path.unwrap(),
1154 let mut payment_id = PaymentId([0; 32]);
1155 let mut payment_hash = PaymentHash([0; 32]);
1156 let mut path: Option<Vec<RouteHop>> = Some(vec![]);
1157 let mut short_channel_id = None;
1158 read_tlv_fields!(reader, {
1159 (0, payment_id, required),
1160 (2, payment_hash, required),
1161 (4, path, vec_type),
1162 (6, short_channel_id, option),
1164 Ok(Some(Event::ProbeFailed {
1167 path: path.unwrap(),
1175 let mut prev_channel_id = [0; 32];
1176 let mut failed_next_destination_opt = None;
1177 read_tlv_fields!(reader, {
1178 (0, prev_channel_id, required),
1179 (2, failed_next_destination_opt, ignorable),
1181 if let Some(failed_next_destination) = failed_next_destination_opt {
1182 Ok(Some(Event::HTLCHandlingFailed {
1184 failed_next_destination,
1187 // If we fail to read a `failed_next_destination` assume it's because
1188 // `MaybeReadable::read` returned `Ok(None)`, though it's also possible we
1189 // were simply missing the field.
1198 let mut channel_id = [0; 32];
1199 let mut user_channel_id: u128 = 0;
1200 let mut counterparty_node_id = OptionDeserWrapper(None);
1201 let mut channel_type = OptionDeserWrapper(None);
1202 read_tlv_fields!(reader, {
1203 (0, channel_id, required),
1204 (2, user_channel_id, required),
1205 (4, counterparty_node_id, required),
1206 (6, channel_type, required),
1209 Ok(Some(Event::ChannelReady {
1212 counterparty_node_id: counterparty_node_id.0.unwrap(),
1213 channel_type: channel_type.0.unwrap()
1218 // Versions prior to 0.0.100 did not ignore odd types, instead returning InvalidValue.
1219 // Version 0.0.100 failed to properly ignore odd types, possibly resulting in corrupt
1221 x if x % 2 == 1 => {
1222 // If the event is of unknown type, assume it was written with `write_tlv_fields`,
1223 // which prefixes the whole thing with a length BigSize. Because the event is
1224 // odd-type unknown, we should treat it as `Ok(None)` even if it has some TLV
1225 // fields that are even. Thus, we avoid using `read_tlv_fields` and simply read
1226 // exactly the number of bytes specified, ignoring them entirely.
1227 let tlv_len: BigSize = Readable::read(reader)?;
1228 FixedLengthReader::new(reader, tlv_len.0)
1229 .eat_remaining().map_err(|_| msgs::DecodeError::ShortRead)?;
1232 _ => Err(msgs::DecodeError::InvalidValue)
1237 /// An event generated by ChannelManager which indicates a message should be sent to a peer (or
1238 /// broadcast to most peers).
1239 /// These events are handled by PeerManager::process_events if you are using a PeerManager.
1240 #[derive(Clone, Debug)]
1241 pub enum MessageSendEvent {
1242 /// Used to indicate that we've accepted a channel open and should send the accept_channel
1243 /// message provided to the given peer.
1245 /// The node_id of the node which should receive this message
1247 /// The message which should be sent.
1248 msg: msgs::AcceptChannel,
1250 /// Used to indicate that we've initiated a channel open and should send the open_channel
1251 /// message provided to the given peer.
1253 /// The node_id of the node which should receive this message
1255 /// The message which should be sent.
1256 msg: msgs::OpenChannel,
1258 /// Used to indicate that a funding_created message should be sent to the peer with the given node_id.
1259 SendFundingCreated {
1260 /// The node_id of the node which should receive this message
1262 /// The message which should be sent.
1263 msg: msgs::FundingCreated,
1265 /// Used to indicate that a funding_signed message should be sent to the peer with the given node_id.
1267 /// The node_id of the node which should receive this message
1269 /// The message which should be sent.
1270 msg: msgs::FundingSigned,
1272 /// Used to indicate that a channel_ready message should be sent to the peer with the given node_id.
1274 /// The node_id of the node which should receive these message(s)
1276 /// The channel_ready message which should be sent.
1277 msg: msgs::ChannelReady,
1279 /// Used to indicate that an announcement_signatures message should be sent to the peer with the given node_id.
1280 SendAnnouncementSignatures {
1281 /// The node_id of the node which should receive these message(s)
1283 /// The announcement_signatures message which should be sent.
1284 msg: msgs::AnnouncementSignatures,
1286 /// Used to indicate that a series of HTLC update messages, as well as a commitment_signed
1287 /// message should be sent to the peer with the given node_id.
1289 /// The node_id of the node which should receive these message(s)
1291 /// The update messages which should be sent. ALL messages in the struct should be sent!
1292 updates: msgs::CommitmentUpdate,
1294 /// Used to indicate that a revoke_and_ack message should be sent to the peer with the given node_id.
1296 /// The node_id of the node which should receive this message
1298 /// The message which should be sent.
1299 msg: msgs::RevokeAndACK,
1301 /// Used to indicate that a closing_signed message should be sent to the peer with the given node_id.
1303 /// The node_id of the node which should receive this message
1305 /// The message which should be sent.
1306 msg: msgs::ClosingSigned,
1308 /// Used to indicate that a shutdown message should be sent to the peer with the given node_id.
1310 /// The node_id of the node which should receive this message
1312 /// The message which should be sent.
1313 msg: msgs::Shutdown,
1315 /// Used to indicate that a channel_reestablish message should be sent to the peer with the given node_id.
1316 SendChannelReestablish {
1317 /// The node_id of the node which should receive this message
1319 /// The message which should be sent.
1320 msg: msgs::ChannelReestablish,
1322 /// Used to send a channel_announcement and channel_update to a specific peer, likely on
1323 /// initial connection to ensure our peers know about our channels.
1324 SendChannelAnnouncement {
1325 /// The node_id of the node which should receive this message
1327 /// The channel_announcement which should be sent.
1328 msg: msgs::ChannelAnnouncement,
1329 /// The followup channel_update which should be sent.
1330 update_msg: msgs::ChannelUpdate,
1332 /// Used to indicate that a channel_announcement and channel_update should be broadcast to all
1333 /// peers (except the peer with node_id either msg.contents.node_id_1 or msg.contents.node_id_2).
1335 /// Note that after doing so, you very likely (unless you did so very recently) want to
1336 /// broadcast a node_announcement (e.g. via [`PeerManager::broadcast_node_announcement`]). This
1337 /// ensures that any nodes which see our channel_announcement also have a relevant
1338 /// node_announcement, including relevant feature flags which may be important for routing
1339 /// through or to us.
1341 /// [`PeerManager::broadcast_node_announcement`]: crate::ln::peer_handler::PeerManager::broadcast_node_announcement
1342 BroadcastChannelAnnouncement {
1343 /// The channel_announcement which should be sent.
1344 msg: msgs::ChannelAnnouncement,
1345 /// The followup channel_update which should be sent.
1346 update_msg: msgs::ChannelUpdate,
1348 /// Used to indicate that a channel_update should be broadcast to all peers.
1349 BroadcastChannelUpdate {
1350 /// The channel_update which should be sent.
1351 msg: msgs::ChannelUpdate,
1353 /// Used to indicate that a channel_update should be sent to a single peer.
1354 /// In contrast to [`Self::BroadcastChannelUpdate`], this is used when the channel is a
1355 /// private channel and we shouldn't be informing all of our peers of channel parameters.
1357 /// The node_id of the node which should receive this message
1359 /// The channel_update which should be sent.
1360 msg: msgs::ChannelUpdate,
1362 /// Broadcast an error downstream to be handled
1364 /// The node_id of the node which should receive this message
1366 /// The action which should be taken.
1367 action: msgs::ErrorAction
1369 /// Query a peer for channels with funding transaction UTXOs in a block range.
1370 SendChannelRangeQuery {
1371 /// The node_id of this message recipient
1373 /// The query_channel_range which should be sent.
1374 msg: msgs::QueryChannelRange,
1376 /// Request routing gossip messages from a peer for a list of channels identified by
1377 /// their short_channel_ids.
1379 /// The node_id of this message recipient
1381 /// The query_short_channel_ids which should be sent.
1382 msg: msgs::QueryShortChannelIds,
1384 /// Sends a reply to a channel range query. This may be one of several SendReplyChannelRange events
1385 /// emitted during processing of the query.
1386 SendReplyChannelRange {
1387 /// The node_id of this message recipient
1389 /// The reply_channel_range which should be sent.
1390 msg: msgs::ReplyChannelRange,
1392 /// Sends a timestamp filter for inbound gossip. This should be sent on each new connection to
1393 /// enable receiving gossip messages from the peer.
1394 SendGossipTimestampFilter {
1395 /// The node_id of this message recipient
1397 /// The gossip_timestamp_filter which should be sent.
1398 msg: msgs::GossipTimestampFilter,
1402 /// A trait indicating an object may generate message send events
1403 pub trait MessageSendEventsProvider {
1404 /// Gets the list of pending events which were generated by previous actions, clearing the list
1406 fn get_and_clear_pending_msg_events(&self) -> Vec<MessageSendEvent>;
1409 /// A trait indicating an object may generate onion messages to send
1410 pub trait OnionMessageProvider {
1411 /// Gets the next pending onion message for the peer with the given node id.
1412 fn next_onion_message_for_peer(&self, peer_node_id: PublicKey) -> Option<msgs::OnionMessage>;
1415 /// A trait indicating an object may generate events.
1417 /// Events are processed by passing an [`EventHandler`] to [`process_pending_events`].
1419 /// Implementations of this trait may also feature an async version of event handling, as shown with
1420 /// [`ChannelManager::process_pending_events_async`] and
1421 /// [`ChainMonitor::process_pending_events_async`].
1425 /// When using this trait, [`process_pending_events`] will call [`handle_event`] for each pending
1426 /// event since the last invocation.
1428 /// In order to ensure no [`Event`]s are lost, implementors of this trait will persist [`Event`]s
1429 /// and replay any unhandled events on startup. An [`Event`] is considered handled when
1430 /// [`process_pending_events`] returns, thus handlers MUST fully handle [`Event`]s and persist any
1431 /// relevant changes to disk *before* returning.
1433 /// Further, because an application may crash between an [`Event`] being handled and the
1434 /// implementor of this trait being re-serialized, [`Event`] handling must be idempotent - in
1435 /// effect, [`Event`]s may be replayed.
1437 /// Note, handlers may call back into the provider and thus deadlocking must be avoided. Be sure to
1438 /// consult the provider's documentation on the implication of processing events and how a handler
1439 /// may safely use the provider (e.g., see [`ChannelManager::process_pending_events`] and
1440 /// [`ChainMonitor::process_pending_events`]).
1442 /// (C-not implementable) As there is likely no reason for a user to implement this trait on their
1445 /// [`process_pending_events`]: Self::process_pending_events
1446 /// [`handle_event`]: EventHandler::handle_event
1447 /// [`ChannelManager::process_pending_events`]: crate::ln::channelmanager::ChannelManager#method.process_pending_events
1448 /// [`ChainMonitor::process_pending_events`]: crate::chain::chainmonitor::ChainMonitor#method.process_pending_events
1449 /// [`ChannelManager::process_pending_events_async`]: crate::ln::channelmanager::ChannelManager::process_pending_events_async
1450 /// [`ChainMonitor::process_pending_events_async`]: crate::chain::chainmonitor::ChainMonitor::process_pending_events_async
1451 pub trait EventsProvider {
1452 /// Processes any events generated since the last call using the given event handler.
1454 /// See the trait-level documentation for requirements.
1455 fn process_pending_events<H: Deref>(&self, handler: H) where H::Target: EventHandler;
1458 /// A trait implemented for objects handling events from [`EventsProvider`].
1460 /// An async variation also exists for implementations of [`EventsProvider`] that support async
1461 /// event handling. The async event handler should satisfy the generic bounds: `F:
1462 /// core::future::Future, H: Fn(Event) -> F`.
1463 pub trait EventHandler {
1464 /// Handles the given [`Event`].
1466 /// See [`EventsProvider`] for details that must be considered when implementing this method.
1467 fn handle_event(&self, event: Event);
1470 impl<F> EventHandler for F where F: Fn(Event) {
1471 fn handle_event(&self, event: Event) {
1476 impl<T: EventHandler> EventHandler for Arc<T> {
1477 fn handle_event(&self, event: Event) {
1478 self.deref().handle_event(event)