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
18 pub mod bump_transaction;
21 pub use bump_transaction::BumpTransactionEvent;
23 use crate::sign::SpendableOutputDescriptor;
24 use crate::ln::channelmanager::{InterceptId, PaymentId, RecipientOnionFields};
25 use crate::ln::channel::FUNDING_CONF_DEADLINE_BLOCKS;
26 use crate::ln::features::ChannelTypeFeatures;
28 use crate::ln::{PaymentPreimage, PaymentHash, PaymentSecret};
29 use crate::routing::gossip::NetworkUpdate;
30 use crate::util::errors::APIError;
31 use crate::util::ser::{BigSize, FixedLengthReader, Writeable, Writer, MaybeReadable, Readable, RequiredWrapper, UpgradableRequired, WithoutLength};
32 use crate::util::string::UntrustedString;
33 use crate::routing::router::{BlindedTail, Path, RouteHop, RouteParameters};
35 use bitcoin::{PackedLockTime, Transaction, OutPoint};
37 use bitcoin::{Txid, TxIn, TxOut, Witness};
38 use bitcoin::blockdata::script::Script;
39 use bitcoin::hashes::Hash;
40 use bitcoin::hashes::sha256::Hash as Sha256;
41 use bitcoin::secp256k1::PublicKey;
43 use crate::prelude::*;
44 use core::time::Duration;
48 /// Some information provided on receipt of payment depends on whether the payment received is a
49 /// spontaneous payment or a "conventional" lightning payment that's paying an invoice.
50 #[derive(Clone, Debug, PartialEq, Eq)]
51 pub enum PaymentPurpose {
52 /// Information for receiving a payment that we generated an invoice for.
54 /// The preimage to the payment_hash, if the payment hash (and secret) were fetched via
55 /// [`ChannelManager::create_inbound_payment`]. If provided, this can be handed directly to
56 /// [`ChannelManager::claim_funds`].
58 /// [`ChannelManager::create_inbound_payment`]: crate::ln::channelmanager::ChannelManager::create_inbound_payment
59 /// [`ChannelManager::claim_funds`]: crate::ln::channelmanager::ChannelManager::claim_funds
60 payment_preimage: Option<PaymentPreimage>,
61 /// The "payment secret". This authenticates the sender to the recipient, preventing a
62 /// number of deanonymization attacks during the routing process.
63 /// It is provided here for your reference, however its accuracy is enforced directly by
64 /// [`ChannelManager`] using the values you previously provided to
65 /// [`ChannelManager::create_inbound_payment`] or
66 /// [`ChannelManager::create_inbound_payment_for_hash`].
68 /// [`ChannelManager`]: crate::ln::channelmanager::ChannelManager
69 /// [`ChannelManager::create_inbound_payment`]: crate::ln::channelmanager::ChannelManager::create_inbound_payment
70 /// [`ChannelManager::create_inbound_payment_for_hash`]: crate::ln::channelmanager::ChannelManager::create_inbound_payment_for_hash
71 payment_secret: PaymentSecret,
73 /// Because this is a spontaneous payment, the payer generated their own preimage rather than us
74 /// (the payee) providing a preimage.
75 SpontaneousPayment(PaymentPreimage),
78 impl_writeable_tlv_based_enum!(PaymentPurpose,
79 (0, InvoicePayment) => {
80 (0, payment_preimage, option),
81 (2, payment_secret, required),
83 (2, SpontaneousPayment)
86 /// When the payment path failure took place and extra details about it. [`PathFailure::OnPath`] may
87 /// contain a [`NetworkUpdate`] that needs to be applied to the [`NetworkGraph`].
89 /// [`NetworkUpdate`]: crate::routing::gossip::NetworkUpdate
90 /// [`NetworkGraph`]: crate::routing::gossip::NetworkGraph
91 #[derive(Clone, Debug, Eq, PartialEq)]
92 pub enum PathFailure {
93 /// We failed to initially send the payment and no HTLC was committed to. Contains the relevant
96 /// The error surfaced from initial send.
99 /// A hop on the path failed to forward our payment.
101 /// If present, this [`NetworkUpdate`] should be applied to the [`NetworkGraph`] so that routing
102 /// decisions can take into account the update.
104 /// [`NetworkUpdate`]: crate::routing::gossip::NetworkUpdate
105 /// [`NetworkGraph`]: crate::routing::gossip::NetworkGraph
106 network_update: Option<NetworkUpdate>,
110 impl_writeable_tlv_based_enum_upgradable!(PathFailure,
112 (0, network_update, upgradable_option),
114 (2, InitialSend) => {
115 (0, err, upgradable_required),
119 #[derive(Clone, Debug, PartialEq, Eq)]
120 /// The reason the channel was closed. See individual variants more details.
121 pub enum ClosureReason {
122 /// Closure generated from receiving a peer error message.
124 /// Our counterparty may have broadcasted their latest commitment state, and we have
126 CounterpartyForceClosed {
127 /// The error which the peer sent us.
129 /// Be careful about printing the peer_msg, a well-crafted message could exploit
130 /// a security vulnerability in the terminal emulator or the logging subsystem.
131 /// To be safe, use `Display` on `UntrustedString`
133 /// [`UntrustedString`]: crate::util::string::UntrustedString
134 peer_msg: UntrustedString,
136 /// Closure generated from [`ChannelManager::force_close_channel`], called by the user.
138 /// [`ChannelManager::force_close_channel`]: crate::ln::channelmanager::ChannelManager::force_close_channel.
140 /// The channel was closed after negotiating a cooperative close and we've now broadcasted
141 /// the cooperative close transaction. Note the shutdown may have been initiated by us.
142 //TODO: split between CounterpartyInitiated/LocallyInitiated
144 /// A commitment transaction was confirmed on chain, closing the channel. Most likely this
145 /// commitment transaction came from our counterparty, but it may also have come from
146 /// a copy of our own `ChannelMonitor`.
147 CommitmentTxConfirmed,
148 /// The funding transaction failed to confirm in a timely manner on an inbound channel.
150 /// Closure generated from processing an event, likely a HTLC forward/relay/reception.
152 /// A developer-readable error message which we generated.
155 /// The peer disconnected prior to funding completing. In this case the spec mandates that we
156 /// forget the channel entirely - we can attempt again if the peer reconnects.
158 /// This includes cases where we restarted prior to funding completion, including prior to the
159 /// initial [`ChannelMonitor`] persistence completing.
161 /// In LDK versions prior to 0.0.107 this could also occur if we were unable to connect to the
162 /// peer because of mutual incompatibility between us and our channel counterparty.
164 /// [`ChannelMonitor`]: crate::chain::channelmonitor::ChannelMonitor
166 /// Closure generated from `ChannelManager::read` if the [`ChannelMonitor`] is newer than
167 /// the [`ChannelManager`] deserialized.
169 /// [`ChannelMonitor`]: crate::chain::channelmonitor::ChannelMonitor
170 /// [`ChannelManager`]: crate::ln::channelmanager::ChannelManager
171 OutdatedChannelManager
174 impl core::fmt::Display for ClosureReason {
175 fn fmt(&self, f: &mut core::fmt::Formatter) -> Result<(), core::fmt::Error> {
176 f.write_str("Channel closed because ")?;
178 ClosureReason::CounterpartyForceClosed { peer_msg } => {
179 f.write_fmt(format_args!("counterparty force-closed with message: {}", peer_msg))
181 ClosureReason::HolderForceClosed => f.write_str("user manually force-closed the channel"),
182 ClosureReason::CooperativeClosure => f.write_str("the channel was cooperatively closed"),
183 ClosureReason::CommitmentTxConfirmed => f.write_str("commitment or closing transaction was confirmed on chain."),
184 ClosureReason::FundingTimedOut => write!(f, "funding transaction failed to confirm within {} blocks", FUNDING_CONF_DEADLINE_BLOCKS),
185 ClosureReason::ProcessingError { err } => {
186 f.write_str("of an exception: ")?;
189 ClosureReason::DisconnectedPeer => f.write_str("the peer disconnected prior to the channel being funded"),
190 ClosureReason::OutdatedChannelManager => f.write_str("the ChannelManager read from disk was stale compared to ChannelMonitor(s)"),
195 impl_writeable_tlv_based_enum_upgradable!(ClosureReason,
196 (0, CounterpartyForceClosed) => { (1, peer_msg, required) },
197 (1, FundingTimedOut) => {},
198 (2, HolderForceClosed) => {},
199 (6, CommitmentTxConfirmed) => {},
200 (4, CooperativeClosure) => {},
201 (8, ProcessingError) => { (1, err, required) },
202 (10, DisconnectedPeer) => {},
203 (12, OutdatedChannelManager) => {},
206 /// Intended destination of a failed HTLC as indicated in [`Event::HTLCHandlingFailed`].
207 #[derive(Clone, Debug, PartialEq, Eq)]
208 pub enum HTLCDestination {
209 /// We tried forwarding to a channel but failed to do so. An example of such an instance is when
210 /// there is insufficient capacity in our outbound channel.
212 /// The `node_id` of the next node. For backwards compatibility, this field is
213 /// marked as optional, versions prior to 0.0.110 may not always be able to provide
214 /// counterparty node information.
215 node_id: Option<PublicKey>,
216 /// The outgoing `channel_id` between us and the next node.
217 channel_id: [u8; 32],
219 /// Scenario where we are unsure of the next node to forward the HTLC to.
221 /// Short channel id we are requesting to forward an HTLC to.
222 requested_forward_scid: u64,
224 /// We couldn't forward to the outgoing scid. An example would be attempting to send a duplicate
227 /// Short channel id we are requesting to forward an HTLC to.
228 requested_forward_scid: u64
230 /// Failure scenario where an HTLC may have been forwarded to be intended for us,
231 /// but is invalid for some reason, so we reject it.
233 /// Some of the reasons may include:
235 /// * Excess HTLCs for a payment that we have already fully received, over-paying for the
237 /// * The counterparty node modified the HTLC in transit,
238 /// * A probing attack where an intermediary node is trying to detect if we are the ultimate
239 /// recipient for a payment.
241 /// The payment hash of the payment we attempted to process.
242 payment_hash: PaymentHash
246 impl_writeable_tlv_based_enum_upgradable!(HTLCDestination,
247 (0, NextHopChannel) => {
248 (0, node_id, required),
249 (2, channel_id, required),
251 (1, InvalidForward) => {
252 (0, requested_forward_scid, required),
254 (2, UnknownNextHop) => {
255 (0, requested_forward_scid, required),
257 (4, FailedPayment) => {
258 (0, payment_hash, required),
262 /// Will be used in [`Event::HTLCIntercepted`] to identify the next hop in the HTLC's path.
263 /// Currently only used in serialization for the sake of maintaining compatibility. More variants
264 /// will be added for general-purpose HTLC forward intercepts as well as trampoline forward
265 /// intercepts in upcoming work.
266 enum InterceptNextHop {
268 requested_next_hop_scid: u64,
272 impl_writeable_tlv_based_enum!(InterceptNextHop,
274 (0, requested_next_hop_scid, required),
278 /// The reason the payment failed. Used in [`Event::PaymentFailed`].
279 #[derive(Clone, Copy, Debug, PartialEq, Eq)]
280 pub enum PaymentFailureReason {
281 /// The intended recipient rejected our payment.
283 /// The user chose to abandon this payment by calling [`ChannelManager::abandon_payment`].
285 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
287 /// We exhausted all of our retry attempts while trying to send the payment, or we
288 /// exhausted the [`Retry::Timeout`] if the user set one. If at any point a retry
289 /// attempt failed while being forwarded along the path, an [`Event::PaymentPathFailed`] will
290 /// have come before this.
292 /// [`Retry::Timeout`]: crate::ln::channelmanager::Retry::Timeout
294 /// The payment expired while retrying, based on the provided
295 /// [`PaymentParameters::expiry_time`].
297 /// [`PaymentParameters::expiry_time`]: crate::routing::router::PaymentParameters::expiry_time
299 /// We failed to find a route while retrying the payment.
301 /// This error should generally never happen. This likely means that there is a problem with
306 impl_writeable_tlv_based_enum!(PaymentFailureReason,
307 (0, RecipientRejected) => {},
308 (2, UserAbandoned) => {},
309 (4, RetriesExhausted) => {},
310 (6, PaymentExpired) => {},
311 (8, RouteNotFound) => {},
312 (10, UnexpectedError) => {}, ;
315 /// An Event which you should probably take some action in response to.
317 /// Note that while Writeable and Readable are implemented for Event, you probably shouldn't use
318 /// them directly as they don't round-trip exactly (for example FundingGenerationReady is never
319 /// written as it makes no sense to respond to it after reconnecting to peers).
320 #[derive(Clone, Debug, PartialEq, Eq)]
322 /// Used to indicate that the client should generate a funding transaction with the given
323 /// parameters and then call [`ChannelManager::funding_transaction_generated`].
324 /// Generated in [`ChannelManager`] message handling.
325 /// Note that *all inputs* in the funding transaction must spend SegWit outputs or your
326 /// counterparty can steal your funds!
328 /// [`ChannelManager`]: crate::ln::channelmanager::ChannelManager
329 /// [`ChannelManager::funding_transaction_generated`]: crate::ln::channelmanager::ChannelManager::funding_transaction_generated
330 FundingGenerationReady {
331 /// The random channel_id we picked which you'll need to pass into
332 /// [`ChannelManager::funding_transaction_generated`].
334 /// [`ChannelManager::funding_transaction_generated`]: crate::ln::channelmanager::ChannelManager::funding_transaction_generated
335 temporary_channel_id: [u8; 32],
336 /// The counterparty's node_id, which you'll need to pass back into
337 /// [`ChannelManager::funding_transaction_generated`].
339 /// [`ChannelManager::funding_transaction_generated`]: crate::ln::channelmanager::ChannelManager::funding_transaction_generated
340 counterparty_node_id: PublicKey,
341 /// The value, in satoshis, that the output should have.
342 channel_value_satoshis: u64,
343 /// The script which should be used in the transaction output.
344 output_script: Script,
345 /// The `user_channel_id` value passed in to [`ChannelManager::create_channel`], or a
346 /// random value for an inbound channel. This may be zero for objects serialized with LDK
347 /// versions prior to 0.0.113.
349 /// [`ChannelManager::create_channel`]: crate::ln::channelmanager::ChannelManager::create_channel
350 user_channel_id: u128,
352 /// Indicates that we've been offered a payment and it needs to be claimed via calling
353 /// [`ChannelManager::claim_funds`] with the preimage given in [`PaymentPurpose`].
355 /// Note that if the preimage is not known, you should call
356 /// [`ChannelManager::fail_htlc_backwards`] or [`ChannelManager::fail_htlc_backwards_with_reason`]
357 /// to free up resources for this HTLC and avoid network congestion.
358 /// If you fail to call either [`ChannelManager::claim_funds`], [`ChannelManager::fail_htlc_backwards`],
359 /// or [`ChannelManager::fail_htlc_backwards_with_reason`] within the HTLC's timeout, the HTLC will be
360 /// automatically failed.
363 /// LDK will not stop an inbound payment from being paid multiple times, so multiple
364 /// `PaymentClaimable` events may be generated for the same payment. In such a case it is
365 /// polite (and required in the lightning specification) to fail the payment the second time
366 /// and give the sender their money back rather than accepting double payment.
369 /// This event used to be called `PaymentReceived` in LDK versions 0.0.112 and earlier.
371 /// [`ChannelManager::claim_funds`]: crate::ln::channelmanager::ChannelManager::claim_funds
372 /// [`ChannelManager::fail_htlc_backwards`]: crate::ln::channelmanager::ChannelManager::fail_htlc_backwards
373 /// [`ChannelManager::fail_htlc_backwards_with_reason`]: crate::ln::channelmanager::ChannelManager::fail_htlc_backwards_with_reason
375 /// The node that will receive the payment after it has been claimed.
376 /// This is useful to identify payments received via [phantom nodes].
377 /// This field will always be filled in when the event was generated by LDK versions
378 /// 0.0.113 and above.
380 /// [phantom nodes]: crate::sign::PhantomKeysManager
381 receiver_node_id: Option<PublicKey>,
382 /// The hash for which the preimage should be handed to the ChannelManager. Note that LDK will
383 /// not stop you from registering duplicate payment hashes for inbound payments.
384 payment_hash: PaymentHash,
385 /// The fields in the onion which were received with each HTLC. Only fields which were
386 /// identical in each HTLC involved in the payment will be included here.
388 /// Payments received on LDK versions prior to 0.0.115 will have this field unset.
389 onion_fields: Option<RecipientOnionFields>,
390 /// The value, in thousandths of a satoshi, that this payment is for.
392 /// Information for claiming this received payment, based on whether the purpose of the
393 /// payment is to pay an invoice or to send a spontaneous payment.
394 purpose: PaymentPurpose,
395 /// The `channel_id` indicating over which channel we received the payment.
396 via_channel_id: Option<[u8; 32]>,
397 /// The `user_channel_id` indicating over which channel we received the payment.
398 via_user_channel_id: Option<u128>,
399 /// The block height at which this payment will be failed back and will no longer be
400 /// eligible for claiming.
402 /// Prior to this height, a call to [`ChannelManager::claim_funds`] is guaranteed to
403 /// succeed, however you should wait for [`Event::PaymentClaimed`] to be sure.
405 /// [`ChannelManager::claim_funds`]: crate::ln::channelmanager::ChannelManager::claim_funds
406 claim_deadline: Option<u32>,
408 /// Indicates a payment has been claimed and we've received money!
410 /// This most likely occurs when [`ChannelManager::claim_funds`] has been called in response
411 /// to an [`Event::PaymentClaimable`]. However, if we previously crashed during a
412 /// [`ChannelManager::claim_funds`] call you may see this event without a corresponding
413 /// [`Event::PaymentClaimable`] event.
416 /// LDK will not stop an inbound payment from being paid multiple times, so multiple
417 /// `PaymentClaimable` events may be generated for the same payment. If you then call
418 /// [`ChannelManager::claim_funds`] twice for the same [`Event::PaymentClaimable`] you may get
419 /// multiple `PaymentClaimed` events.
421 /// [`ChannelManager::claim_funds`]: crate::ln::channelmanager::ChannelManager::claim_funds
423 /// The node that received the payment.
424 /// This is useful to identify payments which were received via [phantom nodes].
425 /// This field will always be filled in when the event was generated by LDK versions
426 /// 0.0.113 and above.
428 /// [phantom nodes]: crate::sign::PhantomKeysManager
429 receiver_node_id: Option<PublicKey>,
430 /// The payment hash of the claimed payment. Note that LDK will not stop you from
431 /// registering duplicate payment hashes for inbound payments.
432 payment_hash: PaymentHash,
433 /// The value, in thousandths of a satoshi, that this payment is for.
435 /// The purpose of the claimed payment, i.e. whether the payment was for an invoice or a
436 /// spontaneous payment.
437 purpose: PaymentPurpose,
439 /// Indicates an outbound payment we made succeeded (i.e. it made it all the way to its target
440 /// and we got back the payment preimage for it).
442 /// Note for MPP payments: in rare cases, this event may be preceded by a `PaymentPathFailed`
443 /// event. In this situation, you SHOULD treat this payment as having succeeded.
445 /// The `payment_id` passed to [`ChannelManager::send_payment`].
447 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
448 payment_id: Option<PaymentId>,
449 /// The preimage to the hash given to ChannelManager::send_payment.
450 /// Note that this serves as a payment receipt, if you wish to have such a thing, you must
451 /// store it somehow!
452 payment_preimage: PaymentPreimage,
453 /// The hash that was given to [`ChannelManager::send_payment`].
455 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
456 payment_hash: PaymentHash,
457 /// The total fee which was spent at intermediate hops in this payment, across all paths.
459 /// Note that, like [`Route::get_total_fees`] this does *not* include any potential
460 /// overpayment to the recipient node.
462 /// If the recipient or an intermediate node misbehaves and gives us free money, this may
463 /// overstate the amount paid, though this is unlikely.
465 /// [`Route::get_total_fees`]: crate::routing::router::Route::get_total_fees
466 fee_paid_msat: Option<u64>,
468 /// Indicates an outbound payment failed. Individual [`Event::PaymentPathFailed`] events
469 /// provide failure information for each path attempt in the payment, including retries.
471 /// This event is provided once there are no further pending HTLCs for the payment and the
472 /// payment is no longer retryable, due either to the [`Retry`] provided or
473 /// [`ChannelManager::abandon_payment`] having been called for the corresponding payment.
475 /// [`Retry`]: crate::ln::channelmanager::Retry
476 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
478 /// The `payment_id` passed to [`ChannelManager::send_payment`].
480 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
481 payment_id: PaymentId,
482 /// The hash that was given to [`ChannelManager::send_payment`].
484 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
485 payment_hash: PaymentHash,
486 /// The reason the payment failed. This is only `None` for events generated or serialized
487 /// by versions prior to 0.0.115.
488 reason: Option<PaymentFailureReason>,
490 /// Indicates that a path for an outbound payment was successful.
492 /// Always generated after [`Event::PaymentSent`] and thus useful for scoring channels. See
493 /// [`Event::PaymentSent`] for obtaining the payment preimage.
494 PaymentPathSuccessful {
495 /// The `payment_id` passed to [`ChannelManager::send_payment`].
497 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
498 payment_id: PaymentId,
499 /// The hash that was given to [`ChannelManager::send_payment`].
501 /// This will be `Some` for all payments which completed on LDK 0.0.104 or later.
503 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
504 payment_hash: Option<PaymentHash>,
505 /// The payment path that was successful.
507 /// May contain a closed channel if the HTLC sent along the path was fulfilled on chain.
510 /// Indicates an outbound HTLC we sent failed, likely due to an intermediary node being unable to
513 /// Note that this does *not* indicate that all paths for an MPP payment have failed, see
514 /// [`Event::PaymentFailed`].
516 /// See [`ChannelManager::abandon_payment`] for giving up on this payment before its retries have
519 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
521 /// The `payment_id` passed to [`ChannelManager::send_payment`].
523 /// This will be `Some` for all payment paths which failed on LDK 0.0.103 or later.
525 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
526 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
527 payment_id: Option<PaymentId>,
528 /// The hash that was given to [`ChannelManager::send_payment`].
530 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
531 payment_hash: PaymentHash,
532 /// Indicates the payment was rejected for some reason by the recipient. This implies that
533 /// the payment has failed, not just the route in question. If this is not set, the payment may
534 /// be retried via a different route.
535 payment_failed_permanently: bool,
536 /// Extra error details based on the failure type. May contain an update that needs to be
537 /// applied to the [`NetworkGraph`].
539 /// [`NetworkGraph`]: crate::routing::gossip::NetworkGraph
540 failure: PathFailure,
541 /// The payment path that failed.
543 /// The channel responsible for the failed payment path.
545 /// Note that for route hints or for the first hop in a path this may be an SCID alias and
546 /// may not refer to a channel in the public network graph. These aliases may also collide
547 /// with channels in the public network graph.
549 /// If this is `Some`, then the corresponding channel should be avoided when the payment is
550 /// retried. May be `None` for older [`Event`] serializations.
551 short_channel_id: Option<u64>,
553 error_code: Option<u16>,
555 error_data: Option<Vec<u8>>,
557 /// Indicates that a probe payment we sent returned successful, i.e., only failed at the destination.
559 /// The id returned by [`ChannelManager::send_probe`].
561 /// [`ChannelManager::send_probe`]: crate::ln::channelmanager::ChannelManager::send_probe
562 payment_id: PaymentId,
563 /// The hash generated by [`ChannelManager::send_probe`].
565 /// [`ChannelManager::send_probe`]: crate::ln::channelmanager::ChannelManager::send_probe
566 payment_hash: PaymentHash,
567 /// The payment path that was successful.
570 /// Indicates that a probe payment we sent failed at an intermediary node on the path.
572 /// The id returned by [`ChannelManager::send_probe`].
574 /// [`ChannelManager::send_probe`]: crate::ln::channelmanager::ChannelManager::send_probe
575 payment_id: PaymentId,
576 /// The hash generated by [`ChannelManager::send_probe`].
578 /// [`ChannelManager::send_probe`]: crate::ln::channelmanager::ChannelManager::send_probe
579 payment_hash: PaymentHash,
580 /// The payment path that failed.
582 /// The channel responsible for the failed probe.
584 /// Note that for route hints or for the first hop in a path this may be an SCID alias and
585 /// may not refer to a channel in the public network graph. These aliases may also collide
586 /// with channels in the public network graph.
587 short_channel_id: Option<u64>,
589 /// Used to indicate that [`ChannelManager::process_pending_htlc_forwards`] should be called at
590 /// a time in the future.
592 /// [`ChannelManager::process_pending_htlc_forwards`]: crate::ln::channelmanager::ChannelManager::process_pending_htlc_forwards
593 PendingHTLCsForwardable {
594 /// The minimum amount of time that should be waited prior to calling
595 /// process_pending_htlc_forwards. To increase the effort required to correlate payments,
596 /// you should wait a random amount of time in roughly the range (now + time_forwardable,
597 /// now + 5*time_forwardable).
598 time_forwardable: Duration,
600 /// Used to indicate that we've intercepted an HTLC forward. This event will only be generated if
601 /// you've encoded an intercept scid in the receiver's invoice route hints using
602 /// [`ChannelManager::get_intercept_scid`] and have set [`UserConfig::accept_intercept_htlcs`].
604 /// [`ChannelManager::forward_intercepted_htlc`] or
605 /// [`ChannelManager::fail_intercepted_htlc`] MUST be called in response to this event. See
606 /// their docs for more information.
608 /// [`ChannelManager::get_intercept_scid`]: crate::ln::channelmanager::ChannelManager::get_intercept_scid
609 /// [`UserConfig::accept_intercept_htlcs`]: crate::util::config::UserConfig::accept_intercept_htlcs
610 /// [`ChannelManager::forward_intercepted_htlc`]: crate::ln::channelmanager::ChannelManager::forward_intercepted_htlc
611 /// [`ChannelManager::fail_intercepted_htlc`]: crate::ln::channelmanager::ChannelManager::fail_intercepted_htlc
613 /// An id to help LDK identify which HTLC is being forwarded or failed.
614 intercept_id: InterceptId,
615 /// The fake scid that was programmed as the next hop's scid, generated using
616 /// [`ChannelManager::get_intercept_scid`].
618 /// [`ChannelManager::get_intercept_scid`]: crate::ln::channelmanager::ChannelManager::get_intercept_scid
619 requested_next_hop_scid: u64,
620 /// The payment hash used for this HTLC.
621 payment_hash: PaymentHash,
622 /// How many msats were received on the inbound edge of this HTLC.
623 inbound_amount_msat: u64,
624 /// How many msats the payer intended to route to the next node. Depending on the reason you are
625 /// intercepting this payment, you might take a fee by forwarding less than this amount.
627 /// Note that LDK will NOT check that expected fees were factored into this value. You MUST
628 /// check that whatever fee you want has been included here or subtract it as required. Further,
629 /// LDK will not stop you from forwarding more than you received.
630 expected_outbound_amount_msat: u64,
632 /// Used to indicate that an output which you should know how to spend was confirmed on chain
633 /// and is now spendable.
634 /// Such an output will *not* ever be spent by rust-lightning, and are not at risk of your
635 /// counterparty spending them due to some kind of timeout. Thus, you need to store them
636 /// somewhere and spend them when you create on-chain transactions.
638 /// The outputs which you should store as spendable by you.
639 outputs: Vec<SpendableOutputDescriptor>,
641 /// This event is generated when a payment has been successfully forwarded through us and a
642 /// forwarding fee earned.
644 /// The incoming channel between the previous node and us. This is only `None` for events
645 /// generated or serialized by versions prior to 0.0.107.
646 prev_channel_id: Option<[u8; 32]>,
647 /// The outgoing channel between the next node and us. This is only `None` for events
648 /// generated or serialized by versions prior to 0.0.107.
649 next_channel_id: Option<[u8; 32]>,
650 /// The fee, in milli-satoshis, which was earned as a result of the payment.
652 /// Note that if we force-closed the channel over which we forwarded an HTLC while the HTLC
653 /// was pending, the amount the next hop claimed will have been rounded down to the nearest
654 /// whole satoshi. Thus, the fee calculated here may be higher than expected as we still
655 /// claimed the full value in millisatoshis from the source. In this case,
656 /// `claim_from_onchain_tx` will be set.
658 /// If the channel which sent us the payment has been force-closed, we will claim the funds
659 /// via an on-chain transaction. In that case we do not yet know the on-chain transaction
660 /// fees which we will spend and will instead set this to `None`. It is possible duplicate
661 /// `PaymentForwarded` events are generated for the same payment iff `fee_earned_msat` is
663 fee_earned_msat: Option<u64>,
664 /// If this is `true`, the forwarded HTLC was claimed by our counterparty via an on-chain
666 claim_from_onchain_tx: bool,
667 /// The final amount forwarded, in milli-satoshis, after the fee is deducted.
669 /// The caveat described above the `fee_earned_msat` field applies here as well.
670 outbound_amount_forwarded_msat: Option<u64>,
672 /// Used to indicate that a channel with the given `channel_id` is being opened and pending
673 /// confirmation on-chain.
675 /// This event is emitted when the funding transaction has been signed and is broadcast to the
676 /// network. For 0conf channels it will be immediately followed by the corresponding
677 /// [`Event::ChannelReady`] event.
679 /// The `channel_id` of the channel that is pending confirmation.
680 channel_id: [u8; 32],
681 /// The `user_channel_id` value passed in to [`ChannelManager::create_channel`] for outbound
682 /// channels, or to [`ChannelManager::accept_inbound_channel`] for inbound channels if
683 /// [`UserConfig::manually_accept_inbound_channels`] config flag is set to true. Otherwise
684 /// `user_channel_id` will be randomized for an inbound channel.
686 /// [`ChannelManager::create_channel`]: crate::ln::channelmanager::ChannelManager::create_channel
687 /// [`ChannelManager::accept_inbound_channel`]: crate::ln::channelmanager::ChannelManager::accept_inbound_channel
688 /// [`UserConfig::manually_accept_inbound_channels`]: crate::util::config::UserConfig::manually_accept_inbound_channels
689 user_channel_id: u128,
690 /// The `temporary_channel_id` this channel used to be known by during channel establishment.
692 /// Will be `None` for channels created prior to LDK version 0.0.115.
693 former_temporary_channel_id: Option<[u8; 32]>,
694 /// The `node_id` of the channel counterparty.
695 counterparty_node_id: PublicKey,
696 /// The outpoint of the channel's funding transaction.
697 funding_txo: OutPoint,
699 /// Used to indicate that a channel with the given `channel_id` is ready to
700 /// be used. This event is emitted either when the funding transaction has been confirmed
701 /// on-chain, or, in case of a 0conf channel, when both parties have confirmed the channel
704 /// The `channel_id` of the channel that is ready.
705 channel_id: [u8; 32],
706 /// The `user_channel_id` value passed in to [`ChannelManager::create_channel`] for outbound
707 /// channels, or to [`ChannelManager::accept_inbound_channel`] for inbound channels if
708 /// [`UserConfig::manually_accept_inbound_channels`] config flag is set to true. Otherwise
709 /// `user_channel_id` will be randomized for an inbound channel.
711 /// [`ChannelManager::create_channel`]: crate::ln::channelmanager::ChannelManager::create_channel
712 /// [`ChannelManager::accept_inbound_channel`]: crate::ln::channelmanager::ChannelManager::accept_inbound_channel
713 /// [`UserConfig::manually_accept_inbound_channels`]: crate::util::config::UserConfig::manually_accept_inbound_channels
714 user_channel_id: u128,
715 /// The `node_id` of the channel counterparty.
716 counterparty_node_id: PublicKey,
717 /// The features that this channel will operate with.
718 channel_type: ChannelTypeFeatures,
720 /// Used to indicate that a previously opened channel with the given `channel_id` is in the
721 /// process of closure.
723 /// The `channel_id` of the channel which has been closed. Note that on-chain transactions
724 /// resolving the channel are likely still awaiting confirmation.
725 channel_id: [u8; 32],
726 /// The `user_channel_id` value passed in to [`ChannelManager::create_channel`] for outbound
727 /// channels, or to [`ChannelManager::accept_inbound_channel`] for inbound channels if
728 /// [`UserConfig::manually_accept_inbound_channels`] config flag is set to true. Otherwise
729 /// `user_channel_id` will be randomized for inbound channels.
730 /// This may be zero for inbound channels serialized prior to 0.0.113 and will always be
731 /// zero for objects serialized with LDK versions prior to 0.0.102.
733 /// [`ChannelManager::create_channel`]: crate::ln::channelmanager::ChannelManager::create_channel
734 /// [`ChannelManager::accept_inbound_channel`]: crate::ln::channelmanager::ChannelManager::accept_inbound_channel
735 /// [`UserConfig::manually_accept_inbound_channels`]: crate::util::config::UserConfig::manually_accept_inbound_channels
736 user_channel_id: u128,
737 /// The reason the channel was closed.
738 reason: ClosureReason
740 /// Used to indicate to the user that they can abandon the funding transaction and recycle the
741 /// inputs for another purpose.
743 /// The channel_id of the channel which has been closed.
744 channel_id: [u8; 32],
745 /// The full transaction received from the user
746 transaction: Transaction
748 /// Indicates a request to open a new channel by a peer.
750 /// To accept the request, call [`ChannelManager::accept_inbound_channel`]. To reject the
751 /// request, call [`ChannelManager::force_close_without_broadcasting_txn`].
753 /// The event is only triggered when a new open channel request is received and the
754 /// [`UserConfig::manually_accept_inbound_channels`] config flag is set to true.
756 /// [`ChannelManager::accept_inbound_channel`]: crate::ln::channelmanager::ChannelManager::accept_inbound_channel
757 /// [`ChannelManager::force_close_without_broadcasting_txn`]: crate::ln::channelmanager::ChannelManager::force_close_without_broadcasting_txn
758 /// [`UserConfig::manually_accept_inbound_channels`]: crate::util::config::UserConfig::manually_accept_inbound_channels
760 /// The temporary channel ID of the channel requested to be opened.
762 /// When responding to the request, the `temporary_channel_id` should be passed
763 /// back to the ChannelManager through [`ChannelManager::accept_inbound_channel`] to accept,
764 /// or through [`ChannelManager::force_close_without_broadcasting_txn`] to reject.
766 /// [`ChannelManager::accept_inbound_channel`]: crate::ln::channelmanager::ChannelManager::accept_inbound_channel
767 /// [`ChannelManager::force_close_without_broadcasting_txn`]: crate::ln::channelmanager::ChannelManager::force_close_without_broadcasting_txn
768 temporary_channel_id: [u8; 32],
769 /// The node_id of the counterparty requesting to open the channel.
771 /// When responding to the request, the `counterparty_node_id` should be passed
772 /// back to the `ChannelManager` through [`ChannelManager::accept_inbound_channel`] to
773 /// accept the request, or through [`ChannelManager::force_close_without_broadcasting_txn`] to reject the
776 /// [`ChannelManager::accept_inbound_channel`]: crate::ln::channelmanager::ChannelManager::accept_inbound_channel
777 /// [`ChannelManager::force_close_without_broadcasting_txn`]: crate::ln::channelmanager::ChannelManager::force_close_without_broadcasting_txn
778 counterparty_node_id: PublicKey,
779 /// The channel value of the requested channel.
780 funding_satoshis: u64,
781 /// Our starting balance in the channel if the request is accepted, in milli-satoshi.
783 /// The features that this channel will operate with. If you reject the channel, a
784 /// well-behaved counterparty may automatically re-attempt the channel with a new set of
787 /// Note that if [`ChannelTypeFeatures::supports_scid_privacy`] returns true on this type,
788 /// the resulting [`ChannelManager`] will not be readable by versions of LDK prior to
791 /// Furthermore, note that if [`ChannelTypeFeatures::supports_zero_conf`] returns true on this type,
792 /// the resulting [`ChannelManager`] will not be readable by versions of LDK prior to
793 /// 0.0.107. Channels setting this type also need to get manually accepted via
794 /// [`crate::ln::channelmanager::ChannelManager::accept_inbound_channel_from_trusted_peer_0conf`],
795 /// or will be rejected otherwise.
797 /// [`ChannelManager`]: crate::ln::channelmanager::ChannelManager
798 channel_type: ChannelTypeFeatures,
800 /// Indicates that the HTLC was accepted, but could not be processed when or after attempting to
803 /// Some scenarios where this event may be sent include:
804 /// * Insufficient capacity in the outbound channel
805 /// * While waiting to forward the HTLC, the channel it is meant to be forwarded through closes
806 /// * When an unknown SCID is requested for forwarding a payment.
807 /// * Expected MPP amount has already been reached
808 /// * The HTLC has timed out
810 /// This event, however, does not get generated if an HTLC fails to meet the forwarding
811 /// requirements (i.e. insufficient fees paid, or a CLTV that is too soon).
813 /// The channel over which the HTLC was received.
814 prev_channel_id: [u8; 32],
815 /// Destination of the HTLC that failed to be processed.
816 failed_next_destination: HTLCDestination,
819 /// Indicates that a transaction originating from LDK needs to have its fee bumped. This event
820 /// requires confirmed external funds to be readily available to spend.
822 /// LDK does not currently generate this event. It is limited to the scope of channels with
823 /// anchor outputs, which will be introduced in a future release.
824 BumpTransaction(BumpTransactionEvent),
827 impl Writeable for Event {
828 fn write<W: Writer>(&self, writer: &mut W) -> Result<(), io::Error> {
830 &Event::FundingGenerationReady { .. } => {
832 // We never write out FundingGenerationReady events as, upon disconnection, peers
833 // drop any channels which have not yet exchanged funding_signed.
835 &Event::PaymentClaimable { ref payment_hash, ref amount_msat, ref purpose,
836 ref receiver_node_id, ref via_channel_id, ref via_user_channel_id,
837 ref claim_deadline, ref onion_fields
840 let mut payment_secret = None;
841 let payment_preimage;
843 PaymentPurpose::InvoicePayment { payment_preimage: preimage, payment_secret: secret } => {
844 payment_secret = Some(secret);
845 payment_preimage = *preimage;
847 PaymentPurpose::SpontaneousPayment(preimage) => {
848 payment_preimage = Some(*preimage);
851 write_tlv_fields!(writer, {
852 (0, payment_hash, required),
853 (1, receiver_node_id, option),
854 (2, payment_secret, option),
855 (3, via_channel_id, option),
856 (4, amount_msat, required),
857 (5, via_user_channel_id, option),
858 (6, 0u64, required), // user_payment_id required for compatibility with 0.0.103 and earlier
859 (7, claim_deadline, option),
860 (8, payment_preimage, option),
861 (9, onion_fields, option),
864 &Event::PaymentSent { ref payment_id, ref payment_preimage, ref payment_hash, ref fee_paid_msat } => {
866 write_tlv_fields!(writer, {
867 (0, payment_preimage, required),
868 (1, payment_hash, required),
869 (3, payment_id, option),
870 (5, fee_paid_msat, option),
873 &Event::PaymentPathFailed {
874 ref payment_id, ref payment_hash, ref payment_failed_permanently, ref failure,
875 ref path, ref short_channel_id,
883 error_code.write(writer)?;
885 error_data.write(writer)?;
886 write_tlv_fields!(writer, {
887 (0, payment_hash, required),
888 (1, None::<NetworkUpdate>, option), // network_update in LDK versions prior to 0.0.114
889 (2, payment_failed_permanently, required),
890 (3, false, required), // all_paths_failed in LDK versions prior to 0.0.114
891 (4, path.blinded_tail, option),
892 (5, path.hops, vec_type),
893 (7, short_channel_id, option),
894 (9, None::<RouteParameters>, option), // retry in LDK versions prior to 0.0.115
895 (11, payment_id, option),
896 (13, failure, required),
899 &Event::PendingHTLCsForwardable { time_forwardable: _ } => {
901 // Note that we now ignore these on the read end as we'll re-generate them in
902 // ChannelManager, we write them here only for backwards compatibility.
904 &Event::SpendableOutputs { ref outputs } => {
906 write_tlv_fields!(writer, {
907 (0, WithoutLength(outputs), required),
910 &Event::HTLCIntercepted { requested_next_hop_scid, payment_hash, inbound_amount_msat, expected_outbound_amount_msat, intercept_id } => {
912 let intercept_scid = InterceptNextHop::FakeScid { requested_next_hop_scid };
913 write_tlv_fields!(writer, {
914 (0, intercept_id, required),
915 (2, intercept_scid, required),
916 (4, payment_hash, required),
917 (6, inbound_amount_msat, required),
918 (8, expected_outbound_amount_msat, required),
921 &Event::PaymentForwarded {
922 fee_earned_msat, prev_channel_id, claim_from_onchain_tx,
923 next_channel_id, outbound_amount_forwarded_msat
926 write_tlv_fields!(writer, {
927 (0, fee_earned_msat, option),
928 (1, prev_channel_id, option),
929 (2, claim_from_onchain_tx, required),
930 (3, next_channel_id, option),
931 (5, outbound_amount_forwarded_msat, option),
934 &Event::ChannelClosed { ref channel_id, ref user_channel_id, ref reason } => {
936 // `user_channel_id` used to be a single u64 value. In order to remain backwards
937 // compatible with versions prior to 0.0.113, the u128 is serialized as two
938 // separate u64 values.
939 let user_channel_id_low = *user_channel_id as u64;
940 let user_channel_id_high = (*user_channel_id >> 64) as u64;
941 write_tlv_fields!(writer, {
942 (0, channel_id, required),
943 (1, user_channel_id_low, required),
944 (2, reason, required),
945 (3, user_channel_id_high, required),
948 &Event::DiscardFunding { ref channel_id, ref transaction } => {
950 write_tlv_fields!(writer, {
951 (0, channel_id, required),
952 (2, transaction, required)
955 &Event::PaymentPathSuccessful { ref payment_id, ref payment_hash, ref path } => {
957 write_tlv_fields!(writer, {
958 (0, payment_id, required),
959 (2, payment_hash, option),
960 (4, path.hops, vec_type),
961 (6, path.blinded_tail, option),
964 &Event::PaymentFailed { ref payment_id, ref payment_hash, ref reason } => {
966 write_tlv_fields!(writer, {
967 (0, payment_id, required),
969 (2, payment_hash, required),
972 &Event::OpenChannelRequest { .. } => {
974 // We never write the OpenChannelRequest events as, upon disconnection, peers
975 // drop any channels which have not yet exchanged funding_signed.
977 &Event::PaymentClaimed { ref payment_hash, ref amount_msat, ref purpose, ref receiver_node_id } => {
979 write_tlv_fields!(writer, {
980 (0, payment_hash, required),
981 (1, receiver_node_id, option),
982 (2, purpose, required),
983 (4, amount_msat, required),
986 &Event::ProbeSuccessful { ref payment_id, ref payment_hash, ref path } => {
988 write_tlv_fields!(writer, {
989 (0, payment_id, required),
990 (2, payment_hash, required),
991 (4, path.hops, vec_type),
992 (6, path.blinded_tail, option),
995 &Event::ProbeFailed { ref payment_id, ref payment_hash, ref path, ref short_channel_id } => {
997 write_tlv_fields!(writer, {
998 (0, payment_id, required),
999 (2, payment_hash, required),
1000 (4, path.hops, vec_type),
1001 (6, short_channel_id, option),
1002 (8, path.blinded_tail, option),
1005 &Event::HTLCHandlingFailed { ref prev_channel_id, ref failed_next_destination } => {
1006 25u8.write(writer)?;
1007 write_tlv_fields!(writer, {
1008 (0, prev_channel_id, required),
1009 (2, failed_next_destination, required),
1013 &Event::BumpTransaction(ref event)=> {
1014 27u8.write(writer)?;
1016 // We never write the ChannelClose|HTLCResolution events as they'll be replayed
1017 // upon restarting anyway if they remain unresolved.
1018 BumpTransactionEvent::ChannelClose { .. } => {}
1019 BumpTransactionEvent::HTLCResolution { .. } => {}
1021 write_tlv_fields!(writer, {}); // Write a length field for forwards compat
1023 &Event::ChannelReady { ref channel_id, ref user_channel_id, ref counterparty_node_id, ref channel_type } => {
1024 29u8.write(writer)?;
1025 write_tlv_fields!(writer, {
1026 (0, channel_id, required),
1027 (2, user_channel_id, required),
1028 (4, counterparty_node_id, required),
1029 (6, channel_type, required),
1032 &Event::ChannelPending { ref channel_id, ref user_channel_id, ref former_temporary_channel_id, ref counterparty_node_id, ref funding_txo } => {
1033 31u8.write(writer)?;
1034 write_tlv_fields!(writer, {
1035 (0, channel_id, required),
1036 (2, user_channel_id, required),
1037 (4, former_temporary_channel_id, required),
1038 (6, counterparty_node_id, required),
1039 (8, funding_txo, required),
1042 // Note that, going forward, all new events must only write data inside of
1043 // `write_tlv_fields`. Versions 0.0.101+ will ignore odd-numbered events that write
1044 // data via `write_tlv_fields`.
1049 impl MaybeReadable for Event {
1050 fn read<R: io::Read>(reader: &mut R) -> Result<Option<Self>, msgs::DecodeError> {
1051 match Readable::read(reader)? {
1052 // Note that we do not write a length-prefixed TLV for FundingGenerationReady events,
1053 // unlike all other events, thus we return immediately here.
1057 let mut payment_hash = PaymentHash([0; 32]);
1058 let mut payment_preimage = None;
1059 let mut payment_secret = None;
1060 let mut amount_msat = 0;
1061 let mut receiver_node_id = None;
1062 let mut _user_payment_id = None::<u64>; // For compatibility with 0.0.103 and earlier
1063 let mut via_channel_id = None;
1064 let mut claim_deadline = None;
1065 let mut via_user_channel_id = None;
1066 let mut onion_fields = None;
1067 read_tlv_fields!(reader, {
1068 (0, payment_hash, required),
1069 (1, receiver_node_id, option),
1070 (2, payment_secret, option),
1071 (3, via_channel_id, option),
1072 (4, amount_msat, required),
1073 (5, via_user_channel_id, option),
1074 (6, _user_payment_id, option),
1075 (7, claim_deadline, option),
1076 (8, payment_preimage, option),
1077 (9, onion_fields, option),
1079 let purpose = match payment_secret {
1080 Some(secret) => PaymentPurpose::InvoicePayment {
1082 payment_secret: secret
1084 None if payment_preimage.is_some() => PaymentPurpose::SpontaneousPayment(payment_preimage.unwrap()),
1085 None => return Err(msgs::DecodeError::InvalidValue),
1087 Ok(Some(Event::PaymentClaimable {
1093 via_user_channel_id,
1102 let mut payment_preimage = PaymentPreimage([0; 32]);
1103 let mut payment_hash = None;
1104 let mut payment_id = None;
1105 let mut fee_paid_msat = None;
1106 read_tlv_fields!(reader, {
1107 (0, payment_preimage, required),
1108 (1, payment_hash, option),
1109 (3, payment_id, option),
1110 (5, fee_paid_msat, option),
1112 if payment_hash.is_none() {
1113 payment_hash = Some(PaymentHash(Sha256::hash(&payment_preimage.0[..]).into_inner()));
1115 Ok(Some(Event::PaymentSent {
1118 payment_hash: payment_hash.unwrap(),
1127 let error_code = Readable::read(reader)?;
1129 let error_data = Readable::read(reader)?;
1130 let mut payment_hash = PaymentHash([0; 32]);
1131 let mut payment_failed_permanently = false;
1132 let mut network_update = None;
1133 let mut blinded_tail: Option<BlindedTail> = None;
1134 let mut path: Option<Vec<RouteHop>> = Some(vec![]);
1135 let mut short_channel_id = None;
1136 let mut payment_id = None;
1137 let mut failure_opt = None;
1138 read_tlv_fields!(reader, {
1139 (0, payment_hash, required),
1140 (1, network_update, upgradable_option),
1141 (2, payment_failed_permanently, required),
1142 (4, blinded_tail, option),
1143 (5, path, vec_type),
1144 (7, short_channel_id, option),
1145 (11, payment_id, option),
1146 (13, failure_opt, upgradable_option),
1148 let failure = failure_opt.unwrap_or_else(|| PathFailure::OnPath { network_update });
1149 Ok(Some(Event::PaymentPathFailed {
1152 payment_failed_permanently,
1154 path: Path { hops: path.unwrap(), blinded_tail },
1167 let mut outputs = WithoutLength(Vec::new());
1168 read_tlv_fields!(reader, {
1169 (0, outputs, required),
1171 Ok(Some(Event::SpendableOutputs { outputs: outputs.0 }))
1176 let mut payment_hash = PaymentHash([0; 32]);
1177 let mut intercept_id = InterceptId([0; 32]);
1178 let mut requested_next_hop_scid = InterceptNextHop::FakeScid { requested_next_hop_scid: 0 };
1179 let mut inbound_amount_msat = 0;
1180 let mut expected_outbound_amount_msat = 0;
1181 read_tlv_fields!(reader, {
1182 (0, intercept_id, required),
1183 (2, requested_next_hop_scid, required),
1184 (4, payment_hash, required),
1185 (6, inbound_amount_msat, required),
1186 (8, expected_outbound_amount_msat, required),
1188 let next_scid = match requested_next_hop_scid {
1189 InterceptNextHop::FakeScid { requested_next_hop_scid: scid } => scid
1191 Ok(Some(Event::HTLCIntercepted {
1193 requested_next_hop_scid: next_scid,
1194 inbound_amount_msat,
1195 expected_outbound_amount_msat,
1201 let mut fee_earned_msat = None;
1202 let mut prev_channel_id = None;
1203 let mut claim_from_onchain_tx = false;
1204 let mut next_channel_id = None;
1205 let mut outbound_amount_forwarded_msat = None;
1206 read_tlv_fields!(reader, {
1207 (0, fee_earned_msat, option),
1208 (1, prev_channel_id, option),
1209 (2, claim_from_onchain_tx, required),
1210 (3, next_channel_id, option),
1211 (5, outbound_amount_forwarded_msat, option),
1213 Ok(Some(Event::PaymentForwarded {
1214 fee_earned_msat, prev_channel_id, claim_from_onchain_tx, next_channel_id,
1215 outbound_amount_forwarded_msat
1222 let mut channel_id = [0; 32];
1223 let mut reason = UpgradableRequired(None);
1224 let mut user_channel_id_low_opt: Option<u64> = None;
1225 let mut user_channel_id_high_opt: Option<u64> = None;
1226 read_tlv_fields!(reader, {
1227 (0, channel_id, required),
1228 (1, user_channel_id_low_opt, option),
1229 (2, reason, upgradable_required),
1230 (3, user_channel_id_high_opt, option),
1233 // `user_channel_id` used to be a single u64 value. In order to remain
1234 // backwards compatible with versions prior to 0.0.113, the u128 is serialized
1235 // as two separate u64 values.
1236 let user_channel_id = (user_channel_id_low_opt.unwrap_or(0) as u128) +
1237 ((user_channel_id_high_opt.unwrap_or(0) as u128) << 64);
1239 Ok(Some(Event::ChannelClosed { channel_id, user_channel_id, reason: _init_tlv_based_struct_field!(reason, upgradable_required) }))
1245 let mut channel_id = [0; 32];
1246 let mut transaction = Transaction{ version: 2, lock_time: PackedLockTime::ZERO, input: Vec::new(), output: Vec::new() };
1247 read_tlv_fields!(reader, {
1248 (0, channel_id, required),
1249 (2, transaction, required),
1251 Ok(Some(Event::DiscardFunding { channel_id, transaction } ))
1257 _init_and_read_tlv_fields!(reader, {
1258 (0, payment_id, required),
1259 (2, payment_hash, option),
1260 (4, path, vec_type),
1261 (6, blinded_tail, option),
1263 Ok(Some(Event::PaymentPathSuccessful {
1264 payment_id: payment_id.0.unwrap(),
1266 path: Path { hops: path.unwrap(), blinded_tail },
1273 let mut payment_hash = PaymentHash([0; 32]);
1274 let mut payment_id = PaymentId([0; 32]);
1275 let mut reason = None;
1276 read_tlv_fields!(reader, {
1277 (0, payment_id, required),
1278 (1, reason, upgradable_option),
1279 (2, payment_hash, required),
1281 Ok(Some(Event::PaymentFailed {
1290 // Value 17 is used for `Event::OpenChannelRequest`.
1295 let mut payment_hash = PaymentHash([0; 32]);
1296 let mut purpose = UpgradableRequired(None);
1297 let mut amount_msat = 0;
1298 let mut receiver_node_id = None;
1299 read_tlv_fields!(reader, {
1300 (0, payment_hash, required),
1301 (1, receiver_node_id, option),
1302 (2, purpose, upgradable_required),
1303 (4, amount_msat, required),
1305 Ok(Some(Event::PaymentClaimed {
1308 purpose: _init_tlv_based_struct_field!(purpose, upgradable_required),
1316 _init_and_read_tlv_fields!(reader, {
1317 (0, payment_id, required),
1318 (2, payment_hash, required),
1319 (4, path, vec_type),
1320 (6, blinded_tail, option),
1322 Ok(Some(Event::ProbeSuccessful {
1323 payment_id: payment_id.0.unwrap(),
1324 payment_hash: payment_hash.0.unwrap(),
1325 path: Path { hops: path.unwrap(), blinded_tail },
1332 _init_and_read_tlv_fields!(reader, {
1333 (0, payment_id, required),
1334 (2, payment_hash, required),
1335 (4, path, vec_type),
1336 (6, short_channel_id, option),
1337 (8, blinded_tail, option),
1339 Ok(Some(Event::ProbeFailed {
1340 payment_id: payment_id.0.unwrap(),
1341 payment_hash: payment_hash.0.unwrap(),
1342 path: Path { hops: path.unwrap(), blinded_tail },
1350 let mut prev_channel_id = [0; 32];
1351 let mut failed_next_destination_opt = UpgradableRequired(None);
1352 read_tlv_fields!(reader, {
1353 (0, prev_channel_id, required),
1354 (2, failed_next_destination_opt, upgradable_required),
1356 Ok(Some(Event::HTLCHandlingFailed {
1358 failed_next_destination: _init_tlv_based_struct_field!(failed_next_destination_opt, upgradable_required),
1366 let mut channel_id = [0; 32];
1367 let mut user_channel_id: u128 = 0;
1368 let mut counterparty_node_id = RequiredWrapper(None);
1369 let mut channel_type = RequiredWrapper(None);
1370 read_tlv_fields!(reader, {
1371 (0, channel_id, required),
1372 (2, user_channel_id, required),
1373 (4, counterparty_node_id, required),
1374 (6, channel_type, required),
1377 Ok(Some(Event::ChannelReady {
1380 counterparty_node_id: counterparty_node_id.0.unwrap(),
1381 channel_type: channel_type.0.unwrap()
1388 let mut channel_id = [0; 32];
1389 let mut user_channel_id: u128 = 0;
1390 let mut former_temporary_channel_id = None;
1391 let mut counterparty_node_id = RequiredWrapper(None);
1392 let mut funding_txo = RequiredWrapper(None);
1393 read_tlv_fields!(reader, {
1394 (0, channel_id, required),
1395 (2, user_channel_id, required),
1396 (4, former_temporary_channel_id, required),
1397 (6, counterparty_node_id, required),
1398 (8, funding_txo, required),
1401 Ok(Some(Event::ChannelPending {
1404 former_temporary_channel_id,
1405 counterparty_node_id: counterparty_node_id.0.unwrap(),
1406 funding_txo: funding_txo.0.unwrap()
1411 // Versions prior to 0.0.100 did not ignore odd types, instead returning InvalidValue.
1412 // Version 0.0.100 failed to properly ignore odd types, possibly resulting in corrupt
1414 x if x % 2 == 1 => {
1415 // If the event is of unknown type, assume it was written with `write_tlv_fields`,
1416 // which prefixes the whole thing with a length BigSize. Because the event is
1417 // odd-type unknown, we should treat it as `Ok(None)` even if it has some TLV
1418 // fields that are even. Thus, we avoid using `read_tlv_fields` and simply read
1419 // exactly the number of bytes specified, ignoring them entirely.
1420 let tlv_len: BigSize = Readable::read(reader)?;
1421 FixedLengthReader::new(reader, tlv_len.0)
1422 .eat_remaining().map_err(|_| msgs::DecodeError::ShortRead)?;
1425 _ => Err(msgs::DecodeError::InvalidValue)
1430 /// An event generated by ChannelManager which indicates a message should be sent to a peer (or
1431 /// broadcast to most peers).
1432 /// These events are handled by PeerManager::process_events if you are using a PeerManager.
1433 #[derive(Clone, Debug)]
1434 pub enum MessageSendEvent {
1435 /// Used to indicate that we've accepted a channel open and should send the accept_channel
1436 /// message provided to the given peer.
1438 /// The node_id of the node which should receive this message
1440 /// The message which should be sent.
1441 msg: msgs::AcceptChannel,
1443 /// Used to indicate that we've accepted a V2 channel open and should send the accept_channel2
1444 /// message provided to the given peer.
1445 SendAcceptChannelV2 {
1446 /// The node_id of the node which should receive this message
1448 /// The message which should be sent.
1449 msg: msgs::AcceptChannelV2,
1451 /// Used to indicate that we've initiated a channel open and should send the open_channel
1452 /// message provided to the given peer.
1454 /// The node_id of the node which should receive this message
1456 /// The message which should be sent.
1457 msg: msgs::OpenChannel,
1459 /// Used to indicate that we've initiated a V2 channel open and should send the open_channel2
1460 /// message provided to the given peer.
1462 /// The node_id of the node which should receive this message
1464 /// The message which should be sent.
1465 msg: msgs::OpenChannelV2,
1467 /// Used to indicate that a funding_created message should be sent to the peer with the given node_id.
1468 SendFundingCreated {
1469 /// The node_id of the node which should receive this message
1471 /// The message which should be sent.
1472 msg: msgs::FundingCreated,
1474 /// Used to indicate that a funding_signed message should be sent to the peer with the given node_id.
1476 /// The node_id of the node which should receive this message
1478 /// The message which should be sent.
1479 msg: msgs::FundingSigned,
1481 /// Used to indicate that a tx_add_input message should be sent to the peer with the given node_id.
1483 /// The node_id of the node which should receive this message
1485 /// The message which should be sent.
1486 msg: msgs::TxAddInput,
1488 /// Used to indicate that a tx_add_output message should be sent to the peer with the given node_id.
1490 /// The node_id of the node which should receive this message
1492 /// The message which should be sent.
1493 msg: msgs::TxAddOutput,
1495 /// Used to indicate that a tx_remove_input message should be sent to the peer with the given node_id.
1497 /// The node_id of the node which should receive this message
1499 /// The message which should be sent.
1500 msg: msgs::TxRemoveInput,
1502 /// Used to indicate that a tx_remove_output message should be sent to the peer with the given node_id.
1503 SendTxRemoveOutput {
1504 /// The node_id of the node which should receive this message
1506 /// The message which should be sent.
1507 msg: msgs::TxRemoveOutput,
1509 /// Used to indicate that a tx_complete message should be sent to the peer with the given node_id.
1511 /// The node_id of the node which should receive this message
1513 /// The message which should be sent.
1514 msg: msgs::TxComplete,
1516 /// Used to indicate that a tx_signatures message should be sent to the peer with the given node_id.
1518 /// The node_id of the node which should receive this message
1520 /// The message which should be sent.
1521 msg: msgs::TxSignatures,
1523 /// Used to indicate that a tx_init_rbf message should be sent to the peer with the given node_id.
1525 /// The node_id of the node which should receive this message
1527 /// The message which should be sent.
1528 msg: msgs::TxInitRbf,
1530 /// Used to indicate that a tx_ack_rbf message should be sent to the peer with the given node_id.
1532 /// The node_id of the node which should receive this message
1534 /// The message which should be sent.
1535 msg: msgs::TxAckRbf,
1537 /// Used to indicate that a tx_abort message should be sent to the peer with the given node_id.
1539 /// The node_id of the node which should receive this message
1541 /// The message which should be sent.
1542 msg: msgs::TxAddInput,
1544 /// Used to indicate that a channel_ready message should be sent to the peer with the given node_id.
1546 /// The node_id of the node which should receive these message(s)
1548 /// The channel_ready message which should be sent.
1549 msg: msgs::ChannelReady,
1551 /// Used to indicate that an announcement_signatures message should be sent to the peer with the given node_id.
1552 SendAnnouncementSignatures {
1553 /// The node_id of the node which should receive these message(s)
1555 /// The announcement_signatures message which should be sent.
1556 msg: msgs::AnnouncementSignatures,
1558 /// Used to indicate that a series of HTLC update messages, as well as a commitment_signed
1559 /// message should be sent to the peer with the given node_id.
1561 /// The node_id of the node which should receive these message(s)
1563 /// The update messages which should be sent. ALL messages in the struct should be sent!
1564 updates: msgs::CommitmentUpdate,
1566 /// Used to indicate that a revoke_and_ack message should be sent to the peer with the given node_id.
1568 /// The node_id of the node which should receive this message
1570 /// The message which should be sent.
1571 msg: msgs::RevokeAndACK,
1573 /// Used to indicate that a closing_signed message should be sent to the peer with the given node_id.
1575 /// The node_id of the node which should receive this message
1577 /// The message which should be sent.
1578 msg: msgs::ClosingSigned,
1580 /// Used to indicate that a shutdown message should be sent to the peer with the given node_id.
1582 /// The node_id of the node which should receive this message
1584 /// The message which should be sent.
1585 msg: msgs::Shutdown,
1587 /// Used to indicate that a channel_reestablish message should be sent to the peer with the given node_id.
1588 SendChannelReestablish {
1589 /// The node_id of the node which should receive this message
1591 /// The message which should be sent.
1592 msg: msgs::ChannelReestablish,
1594 /// Used to send a channel_announcement and channel_update to a specific peer, likely on
1595 /// initial connection to ensure our peers know about our channels.
1596 SendChannelAnnouncement {
1597 /// The node_id of the node which should receive this message
1599 /// The channel_announcement which should be sent.
1600 msg: msgs::ChannelAnnouncement,
1601 /// The followup channel_update which should be sent.
1602 update_msg: msgs::ChannelUpdate,
1604 /// Used to indicate that a channel_announcement and channel_update should be broadcast to all
1605 /// peers (except the peer with node_id either msg.contents.node_id_1 or msg.contents.node_id_2).
1607 /// Note that after doing so, you very likely (unless you did so very recently) want to
1608 /// broadcast a node_announcement (e.g. via [`PeerManager::broadcast_node_announcement`]). This
1609 /// ensures that any nodes which see our channel_announcement also have a relevant
1610 /// node_announcement, including relevant feature flags which may be important for routing
1611 /// through or to us.
1613 /// [`PeerManager::broadcast_node_announcement`]: crate::ln::peer_handler::PeerManager::broadcast_node_announcement
1614 BroadcastChannelAnnouncement {
1615 /// The channel_announcement which should be sent.
1616 msg: msgs::ChannelAnnouncement,
1617 /// The followup channel_update which should be sent.
1618 update_msg: Option<msgs::ChannelUpdate>,
1620 /// Used to indicate that a channel_update should be broadcast to all peers.
1621 BroadcastChannelUpdate {
1622 /// The channel_update which should be sent.
1623 msg: msgs::ChannelUpdate,
1625 /// Used to indicate that a node_announcement should be broadcast to all peers.
1626 BroadcastNodeAnnouncement {
1627 /// The node_announcement which should be sent.
1628 msg: msgs::NodeAnnouncement,
1630 /// Used to indicate that a channel_update should be sent to a single peer.
1631 /// In contrast to [`Self::BroadcastChannelUpdate`], this is used when the channel is a
1632 /// private channel and we shouldn't be informing all of our peers of channel parameters.
1634 /// The node_id of the node which should receive this message
1636 /// The channel_update which should be sent.
1637 msg: msgs::ChannelUpdate,
1639 /// Broadcast an error downstream to be handled
1641 /// The node_id of the node which should receive this message
1643 /// The action which should be taken.
1644 action: msgs::ErrorAction
1646 /// Query a peer for channels with funding transaction UTXOs in a block range.
1647 SendChannelRangeQuery {
1648 /// The node_id of this message recipient
1650 /// The query_channel_range which should be sent.
1651 msg: msgs::QueryChannelRange,
1653 /// Request routing gossip messages from a peer for a list of channels identified by
1654 /// their short_channel_ids.
1656 /// The node_id of this message recipient
1658 /// The query_short_channel_ids which should be sent.
1659 msg: msgs::QueryShortChannelIds,
1661 /// Sends a reply to a channel range query. This may be one of several SendReplyChannelRange events
1662 /// emitted during processing of the query.
1663 SendReplyChannelRange {
1664 /// The node_id of this message recipient
1666 /// The reply_channel_range which should be sent.
1667 msg: msgs::ReplyChannelRange,
1669 /// Sends a timestamp filter for inbound gossip. This should be sent on each new connection to
1670 /// enable receiving gossip messages from the peer.
1671 SendGossipTimestampFilter {
1672 /// The node_id of this message recipient
1674 /// The gossip_timestamp_filter which should be sent.
1675 msg: msgs::GossipTimestampFilter,
1679 /// A trait indicating an object may generate message send events
1680 pub trait MessageSendEventsProvider {
1681 /// Gets the list of pending events which were generated by previous actions, clearing the list
1683 fn get_and_clear_pending_msg_events(&self) -> Vec<MessageSendEvent>;
1686 /// A trait indicating an object may generate onion messages to send
1687 pub trait OnionMessageProvider {
1688 /// Gets the next pending onion message for the peer with the given node id.
1689 fn next_onion_message_for_peer(&self, peer_node_id: PublicKey) -> Option<msgs::OnionMessage>;
1692 /// A trait indicating an object may generate events.
1694 /// Events are processed by passing an [`EventHandler`] to [`process_pending_events`].
1696 /// Implementations of this trait may also feature an async version of event handling, as shown with
1697 /// [`ChannelManager::process_pending_events_async`] and
1698 /// [`ChainMonitor::process_pending_events_async`].
1702 /// When using this trait, [`process_pending_events`] will call [`handle_event`] for each pending
1703 /// event since the last invocation.
1705 /// In order to ensure no [`Event`]s are lost, implementors of this trait will persist [`Event`]s
1706 /// and replay any unhandled events on startup. An [`Event`] is considered handled when
1707 /// [`process_pending_events`] returns, thus handlers MUST fully handle [`Event`]s and persist any
1708 /// relevant changes to disk *before* returning.
1710 /// Further, because an application may crash between an [`Event`] being handled and the
1711 /// implementor of this trait being re-serialized, [`Event`] handling must be idempotent - in
1712 /// effect, [`Event`]s may be replayed.
1714 /// Note, handlers may call back into the provider and thus deadlocking must be avoided. Be sure to
1715 /// consult the provider's documentation on the implication of processing events and how a handler
1716 /// may safely use the provider (e.g., see [`ChannelManager::process_pending_events`] and
1717 /// [`ChainMonitor::process_pending_events`]).
1719 /// (C-not implementable) As there is likely no reason for a user to implement this trait on their
1722 /// [`process_pending_events`]: Self::process_pending_events
1723 /// [`handle_event`]: EventHandler::handle_event
1724 /// [`ChannelManager::process_pending_events`]: crate::ln::channelmanager::ChannelManager#method.process_pending_events
1725 /// [`ChainMonitor::process_pending_events`]: crate::chain::chainmonitor::ChainMonitor#method.process_pending_events
1726 /// [`ChannelManager::process_pending_events_async`]: crate::ln::channelmanager::ChannelManager::process_pending_events_async
1727 /// [`ChainMonitor::process_pending_events_async`]: crate::chain::chainmonitor::ChainMonitor::process_pending_events_async
1728 pub trait EventsProvider {
1729 /// Processes any events generated since the last call using the given event handler.
1731 /// See the trait-level documentation for requirements.
1732 fn process_pending_events<H: Deref>(&self, handler: H) where H::Target: EventHandler;
1735 /// A trait implemented for objects handling events from [`EventsProvider`].
1737 /// An async variation also exists for implementations of [`EventsProvider`] that support async
1738 /// event handling. The async event handler should satisfy the generic bounds: `F:
1739 /// core::future::Future, H: Fn(Event) -> F`.
1740 pub trait EventHandler {
1741 /// Handles the given [`Event`].
1743 /// See [`EventsProvider`] for details that must be considered when implementing this method.
1744 fn handle_event(&self, event: Event);
1747 impl<F> EventHandler for F where F: Fn(Event) {
1748 fn handle_event(&self, event: Event) {
1753 impl<T: EventHandler> EventHandler for Arc<T> {
1754 fn handle_event(&self, event: Event) {
1755 self.deref().handle_event(event)