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 chain::keysinterface::SpendableOutputDescriptor;
18 use ln::channelmanager::PaymentId;
19 use ln::channel::FUNDING_CONF_DEADLINE_BLOCKS;
21 use ln::msgs::DecodeError;
22 use ln::{PaymentPreimage, PaymentHash, PaymentSecret};
23 use routing::network_graph::NetworkUpdate;
24 use util::ser::{BigSize, FixedLengthReader, Writeable, Writer, MaybeReadable, Readable, VecReadWrapper, VecWriteWrapper};
25 use routing::router::{RouteHop, RouteParameters};
27 use bitcoin::Transaction;
28 use bitcoin::blockdata::script::Script;
29 use bitcoin::hashes::Hash;
30 use bitcoin::hashes::sha256::Hash as Sha256;
31 use bitcoin::secp256k1::key::PublicKey;
35 use core::time::Duration;
39 /// Some information provided on receipt of payment depends on whether the payment received is a
40 /// spontaneous payment or a "conventional" lightning payment that's paying an invoice.
41 #[derive(Clone, Debug)]
42 pub enum PaymentPurpose {
43 /// Information for receiving a payment that we generated an invoice for.
45 /// The preimage to the payment_hash, if the payment hash (and secret) were fetched via
46 /// [`ChannelManager::create_inbound_payment`]. If provided, this can be handed directly to
47 /// [`ChannelManager::claim_funds`].
49 /// [`ChannelManager::create_inbound_payment`]: crate::ln::channelmanager::ChannelManager::create_inbound_payment
50 /// [`ChannelManager::claim_funds`]: crate::ln::channelmanager::ChannelManager::claim_funds
51 payment_preimage: Option<PaymentPreimage>,
52 /// The "payment secret". This authenticates the sender to the recipient, preventing a
53 /// number of deanonymization attacks during the routing process.
54 /// It is provided here for your reference, however its accuracy is enforced directly by
55 /// [`ChannelManager`] using the values you previously provided to
56 /// [`ChannelManager::create_inbound_payment`] or
57 /// [`ChannelManager::create_inbound_payment_for_hash`].
59 /// [`ChannelManager`]: crate::ln::channelmanager::ChannelManager
60 /// [`ChannelManager::create_inbound_payment`]: crate::ln::channelmanager::ChannelManager::create_inbound_payment
61 /// [`ChannelManager::create_inbound_payment_for_hash`]: crate::ln::channelmanager::ChannelManager::create_inbound_payment_for_hash
62 payment_secret: PaymentSecret,
64 /// Because this is a spontaneous payment, the payer generated their own preimage rather than us
65 /// (the payee) providing a preimage.
66 SpontaneousPayment(PaymentPreimage),
69 #[derive(Clone, Debug, PartialEq)]
70 /// The reason the channel was closed. See individual variants more details.
71 pub enum ClosureReason {
72 /// Closure generated from receiving a peer error message.
74 /// Our counterparty may have broadcasted their latest commitment state, and we have
76 CounterpartyForceClosed {
77 /// The error which the peer sent us.
79 /// The string should be sanitized before it is used (e.g emitted to logs
80 /// or printed to stdout). Otherwise, a well crafted error message may exploit
81 /// a security vulnerability in the terminal emulator or the logging subsystem.
84 /// Closure generated from [`ChannelManager::force_close_channel`], called by the user.
86 /// [`ChannelManager::force_close_channel`]: crate::ln::channelmanager::ChannelManager::force_close_channel.
88 /// The channel was closed after negotiating a cooperative close and we've now broadcasted
89 /// the cooperative close transaction. Note the shutdown may have been initiated by us.
90 //TODO: split between CounterpartyInitiated/LocallyInitiated
92 /// A commitment transaction was confirmed on chain, closing the channel. Most likely this
93 /// commitment transaction came from our counterparty, but it may also have come from
94 /// a copy of our own `ChannelMonitor`.
95 CommitmentTxConfirmed,
96 /// The funding transaction failed to confirm in a timely manner on an inbound channel.
98 /// Closure generated from processing an event, likely a HTLC forward/relay/reception.
100 /// A developer-readable error message which we generated.
103 /// The `PeerManager` informed us that we've disconnected from the peer. We close channels
104 /// if the `PeerManager` informed us that it is unlikely we'll be able to connect to the
105 /// peer again in the future or if the peer disconnected before we finished negotiating
106 /// the channel open. The first case may be caused by incompatible features which our
107 /// counterparty, or we, require.
108 //TODO: split between PeerUnconnectable/PeerDisconnected ?
110 /// Closure generated from `ChannelManager::read` if the ChannelMonitor is newer than
111 /// the ChannelManager deserialized.
112 OutdatedChannelManager
115 impl core::fmt::Display for ClosureReason {
116 fn fmt(&self, f: &mut core::fmt::Formatter) -> Result<(), core::fmt::Error> {
117 f.write_str("Channel closed because ")?;
119 ClosureReason::CounterpartyForceClosed { peer_msg } => {
120 f.write_str("counterparty force-closed with message ")?;
121 f.write_str(&peer_msg)
123 ClosureReason::HolderForceClosed => f.write_str("user manually force-closed the channel"),
124 ClosureReason::CooperativeClosure => f.write_str("the channel was cooperatively closed"),
125 ClosureReason::CommitmentTxConfirmed => f.write_str("commitment or closing transaction was confirmed on chain."),
126 ClosureReason::FundingTimedOut => write!(f, "funding transaction failed to confirm within {} blocks", FUNDING_CONF_DEADLINE_BLOCKS),
127 ClosureReason::ProcessingError { err } => {
128 f.write_str("of an exception: ")?;
131 ClosureReason::DisconnectedPeer => f.write_str("the peer disconnected prior to the channel being funded"),
132 ClosureReason::OutdatedChannelManager => f.write_str("the ChannelManager read from disk was stale compared to ChannelMonitor(s)"),
137 impl_writeable_tlv_based_enum_upgradable!(ClosureReason,
138 (0, CounterpartyForceClosed) => { (1, peer_msg, required) },
139 (1, FundingTimedOut) => {},
140 (2, HolderForceClosed) => {},
141 (6, CommitmentTxConfirmed) => {},
142 (4, CooperativeClosure) => {},
143 (8, ProcessingError) => { (1, err, required) },
144 (10, DisconnectedPeer) => {},
145 (12, OutdatedChannelManager) => {},
148 /// An Event which you should probably take some action in response to.
150 /// Note that while Writeable and Readable are implemented for Event, you probably shouldn't use
151 /// them directly as they don't round-trip exactly (for example FundingGenerationReady is never
152 /// written as it makes no sense to respond to it after reconnecting to peers).
153 #[derive(Clone, Debug)]
155 /// Used to indicate that the client should generate a funding transaction with the given
156 /// parameters and then call [`ChannelManager::funding_transaction_generated`].
157 /// Generated in [`ChannelManager`] message handling.
158 /// Note that *all inputs* in the funding transaction must spend SegWit outputs or your
159 /// counterparty can steal your funds!
161 /// [`ChannelManager`]: crate::ln::channelmanager::ChannelManager
162 /// [`ChannelManager::funding_transaction_generated`]: crate::ln::channelmanager::ChannelManager::funding_transaction_generated
163 FundingGenerationReady {
164 /// The random channel_id we picked which you'll need to pass into
165 /// ChannelManager::funding_transaction_generated.
166 temporary_channel_id: [u8; 32],
167 /// The value, in satoshis, that the output should have.
168 channel_value_satoshis: u64,
169 /// The script which should be used in the transaction output.
170 output_script: Script,
171 /// The `user_channel_id` value passed in to [`ChannelManager::create_channel`], or 0 for
172 /// an inbound channel.
174 /// [`ChannelManager::create_channel`]: crate::ln::channelmanager::ChannelManager::create_channel
175 user_channel_id: u64,
177 /// Indicates we've received money! Just gotta dig out that payment preimage and feed it to
178 /// [`ChannelManager::claim_funds`] to get it....
179 /// Note that if the preimage is not known, you should call
180 /// [`ChannelManager::fail_htlc_backwards`] to free up resources for this HTLC and avoid
181 /// network congestion.
182 /// If you fail to call either [`ChannelManager::claim_funds`] or
183 /// [`ChannelManager::fail_htlc_backwards`] within the HTLC's timeout, the HTLC will be
184 /// automatically failed.
187 /// LDK will not stop an inbound payment from being paid multiple times, so multiple
188 /// `PaymentReceived` events may be generated for the same payment.
190 /// [`ChannelManager::claim_funds`]: crate::ln::channelmanager::ChannelManager::claim_funds
191 /// [`ChannelManager::fail_htlc_backwards`]: crate::ln::channelmanager::ChannelManager::fail_htlc_backwards
193 /// The hash for which the preimage should be handed to the ChannelManager. Note that LDK will
194 /// not stop you from registering duplicate payment hashes for inbound payments.
195 payment_hash: PaymentHash,
196 /// The value, in thousandths of a satoshi, that this payment is for.
198 /// Information for claiming this received payment, based on whether the purpose of the
199 /// payment is to pay an invoice or to send a spontaneous payment.
200 purpose: PaymentPurpose,
202 /// Indicates an outbound payment we made succeeded (i.e. it made it all the way to its target
203 /// and we got back the payment preimage for it).
205 /// Note for MPP payments: in rare cases, this event may be preceded by a `PaymentPathFailed`
206 /// event. In this situation, you SHOULD treat this payment as having succeeded.
208 /// The id returned by [`ChannelManager::send_payment`] and used with
209 /// [`ChannelManager::retry_payment`].
211 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
212 /// [`ChannelManager::retry_payment`]: crate::ln::channelmanager::ChannelManager::retry_payment
213 payment_id: Option<PaymentId>,
214 /// The preimage to the hash given to ChannelManager::send_payment.
215 /// Note that this serves as a payment receipt, if you wish to have such a thing, you must
216 /// store it somehow!
217 payment_preimage: PaymentPreimage,
218 /// The hash that was given to [`ChannelManager::send_payment`].
220 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
221 payment_hash: PaymentHash,
222 /// The total fee which was spent at intermediate hops in this payment, across all paths.
224 /// Note that, like [`Route::get_total_fees`] this does *not* include any potential
225 /// overpayment to the recipient node.
227 /// If the recipient or an intermediate node misbehaves and gives us free money, this may
228 /// overstate the amount paid, though this is unlikely.
230 /// [`Route::get_total_fees`]: crate::routing::router::Route::get_total_fees
231 fee_paid_msat: Option<u64>,
233 /// Indicates an outbound HTLC we sent failed. Probably some intermediary node dropped
234 /// something. You may wish to retry with a different route.
236 /// Note that this does *not* indicate that all paths for an MPP payment have failed, see
237 /// [`Event::PaymentFailed`] and [`all_paths_failed`].
239 /// [`all_paths_failed`]: Self::all_paths_failed
241 /// The id returned by [`ChannelManager::send_payment`] and used with
242 /// [`ChannelManager::retry_payment`] and [`ChannelManager::abandon_payment`].
244 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
245 /// [`ChannelManager::retry_payment`]: crate::ln::channelmanager::ChannelManager::retry_payment
246 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
247 payment_id: Option<PaymentId>,
248 /// The hash that was given to [`ChannelManager::send_payment`].
250 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
251 payment_hash: PaymentHash,
252 /// Indicates the payment was rejected for some reason by the recipient. This implies that
253 /// the payment has failed, not just the route in question. If this is not set, you may
254 /// retry the payment via a different route.
255 rejected_by_dest: bool,
256 /// Any failure information conveyed via the Onion return packet by a node along the failed
259 /// Should be applied to the [`NetworkGraph`] so that routing decisions can take into
260 /// account the update. [`NetGraphMsgHandler`] is capable of doing this.
262 /// [`NetworkGraph`]: crate::routing::network_graph::NetworkGraph
263 /// [`NetGraphMsgHandler`]: crate::routing::network_graph::NetGraphMsgHandler
264 network_update: Option<NetworkUpdate>,
265 /// For both single-path and multi-path payments, this is set if all paths of the payment have
266 /// failed. This will be set to false if (1) this is an MPP payment and (2) other parts of the
267 /// larger MPP payment were still in flight when this event was generated.
269 /// Note that if you are retrying individual MPP parts, using this value to determine if a
270 /// payment has fully failed is race-y. Because multiple failures can happen prior to events
271 /// being processed, you may retry in response to a first failure, with a second failure
272 /// (with `all_paths_failed` set) still pending. Then, when the second failure is processed
273 /// you will see `all_paths_failed` set even though the retry of the first failure still
274 /// has an associated in-flight HTLC. See (1) for an example of such a failure.
276 /// If you wish to retry individual MPP parts and learn when a payment has failed, you must
277 /// call [`ChannelManager::abandon_payment`] and wait for a [`Event::PaymentFailed`] event.
279 /// (1) <https://github.com/lightningdevkit/rust-lightning/issues/1164>
281 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
282 all_paths_failed: bool,
283 /// The payment path that failed.
285 /// The channel responsible for the failed payment path.
287 /// If this is `Some`, then the corresponding channel should be avoided when the payment is
288 /// retried. May be `None` for older [`Event`] serializations.
289 short_channel_id: Option<u64>,
290 /// Parameters needed to compute a new [`Route`] when retrying the failed payment path.
292 /// See [`find_route`] for details.
294 /// [`Route`]: crate::routing::router::Route
295 /// [`find_route`]: crate::routing::router::find_route
296 retry: Option<RouteParameters>,
298 error_code: Option<u16>,
300 error_data: Option<Vec<u8>>,
302 /// Indicates an outbound payment failed. Individual [`Event::PaymentPathFailed`] events
303 /// provide failure information for each MPP part in the payment.
305 /// This event is provided once there are no further pending HTLCs for the payment and the
306 /// payment is no longer retryable, either due to a several-block timeout or because
307 /// [`ChannelManager::abandon_payment`] was previously called for the corresponding payment.
309 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
311 /// The id returned by [`ChannelManager::send_payment`] and used with
312 /// [`ChannelManager::retry_payment`] and [`ChannelManager::abandon_payment`].
314 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
315 /// [`ChannelManager::retry_payment`]: crate::ln::channelmanager::ChannelManager::retry_payment
316 /// [`ChannelManager::abandon_payment`]: crate::ln::channelmanager::ChannelManager::abandon_payment
317 payment_id: PaymentId,
318 /// The hash that was given to [`ChannelManager::send_payment`].
320 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
321 payment_hash: PaymentHash,
323 /// Used to indicate that [`ChannelManager::process_pending_htlc_forwards`] should be called at
324 /// a time in the future.
326 /// [`ChannelManager::process_pending_htlc_forwards`]: crate::ln::channelmanager::ChannelManager::process_pending_htlc_forwards
327 PendingHTLCsForwardable {
328 /// The minimum amount of time that should be waited prior to calling
329 /// process_pending_htlc_forwards. To increase the effort required to correlate payments,
330 /// you should wait a random amount of time in roughly the range (now + time_forwardable,
331 /// now + 5*time_forwardable).
332 time_forwardable: Duration,
334 /// Used to indicate that an output which you should know how to spend was confirmed on chain
335 /// and is now spendable.
336 /// Such an output will *not* ever be spent by rust-lightning, and are not at risk of your
337 /// counterparty spending them due to some kind of timeout. Thus, you need to store them
338 /// somewhere and spend them when you create on-chain transactions.
340 /// The outputs which you should store as spendable by you.
341 outputs: Vec<SpendableOutputDescriptor>,
343 /// This event is generated when a payment has been successfully forwarded through us and a
344 /// forwarding fee earned.
346 /// The fee, in milli-satoshis, which was earned as a result of the payment.
348 /// Note that if we force-closed the channel over which we forwarded an HTLC while the HTLC
349 /// was pending, the amount the next hop claimed will have been rounded down to the nearest
350 /// whole satoshi. Thus, the fee calculated here may be higher than expected as we still
351 /// claimed the full value in millisatoshis from the source. In this case,
352 /// `claim_from_onchain_tx` will be set.
354 /// If the channel which sent us the payment has been force-closed, we will claim the funds
355 /// via an on-chain transaction. In that case we do not yet know the on-chain transaction
356 /// fees which we will spend and will instead set this to `None`. It is possible duplicate
357 /// `PaymentForwarded` events are generated for the same payment iff `fee_earned_msat` is
359 fee_earned_msat: Option<u64>,
360 /// If this is `true`, the forwarded HTLC was claimed by our counterparty via an on-chain
362 claim_from_onchain_tx: bool,
364 /// Used to indicate that a channel with the given `channel_id` is in the process of closure.
366 /// The channel_id of the channel which has been closed. Note that on-chain transactions
367 /// resolving the channel are likely still awaiting confirmation.
368 channel_id: [u8; 32],
369 /// The `user_channel_id` value passed in to [`ChannelManager::create_channel`], or 0 for
370 /// an inbound channel. This will always be zero for objects serialized with LDK versions
371 /// prior to 0.0.102.
373 /// [`ChannelManager::create_channel`]: crate::ln::channelmanager::ChannelManager::create_channel
374 user_channel_id: u64,
375 /// The reason the channel was closed.
376 reason: ClosureReason
378 /// Used to indicate to the user that they can abandon the funding transaction and recycle the
379 /// inputs for another purpose.
381 /// The channel_id of the channel which has been closed.
382 channel_id: [u8; 32],
383 /// The full transaction received from the user
384 transaction: Transaction
386 /// Indicates that a path for an outbound payment was successful.
388 /// Always generated after [`Event::PaymentSent`] and thus useful for scoring channels. See
389 /// [`Event::PaymentSent`] for obtaining the payment preimage.
390 PaymentPathSuccessful {
391 /// The id returned by [`ChannelManager::send_payment`] and used with
392 /// [`ChannelManager::retry_payment`].
394 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
395 /// [`ChannelManager::retry_payment`]: crate::ln::channelmanager::ChannelManager::retry_payment
396 payment_id: PaymentId,
397 /// The hash that was given to [`ChannelManager::send_payment`].
399 /// [`ChannelManager::send_payment`]: crate::ln::channelmanager::ChannelManager::send_payment
400 payment_hash: Option<PaymentHash>,
401 /// The payment path that was successful.
403 /// May contain a closed channel if the HTLC sent along the path was fulfilled on chain.
408 impl Writeable for Event {
409 fn write<W: Writer>(&self, writer: &mut W) -> Result<(), io::Error> {
411 &Event::FundingGenerationReady { .. } => {
413 // We never write out FundingGenerationReady events as, upon disconnection, peers
414 // drop any channels which have not yet exchanged funding_signed.
416 &Event::PaymentReceived { ref payment_hash, ref amt, ref purpose } => {
418 let mut payment_secret = None;
419 let payment_preimage;
421 PaymentPurpose::InvoicePayment { payment_preimage: preimage, payment_secret: secret } => {
422 payment_secret = Some(secret);
423 payment_preimage = *preimage;
425 PaymentPurpose::SpontaneousPayment(preimage) => {
426 payment_preimage = Some(*preimage);
429 write_tlv_fields!(writer, {
430 (0, payment_hash, required),
431 (2, payment_secret, option),
433 (6, 0u64, required), // user_payment_id required for compatibility with 0.0.103 and earlier
434 (8, payment_preimage, option),
437 &Event::PaymentSent { ref payment_id, ref payment_preimage, ref payment_hash, ref fee_paid_msat } => {
439 write_tlv_fields!(writer, {
440 (0, payment_preimage, required),
441 (1, payment_hash, required),
442 (3, payment_id, option),
443 (5, fee_paid_msat, option),
446 &Event::PaymentPathFailed {
447 ref payment_id, ref payment_hash, ref rejected_by_dest, ref network_update,
448 ref all_paths_failed, ref path, ref short_channel_id, ref retry,
456 error_code.write(writer)?;
458 error_data.write(writer)?;
459 write_tlv_fields!(writer, {
460 (0, payment_hash, required),
461 (1, network_update, option),
462 (2, rejected_by_dest, required),
463 (3, all_paths_failed, required),
465 (7, short_channel_id, option),
467 (11, payment_id, option),
470 &Event::PendingHTLCsForwardable { time_forwardable: _ } => {
472 // Note that we now ignore these on the read end as we'll re-generate them in
473 // ChannelManager, we write them here only for backwards compatibility.
475 &Event::SpendableOutputs { ref outputs } => {
477 write_tlv_fields!(writer, {
478 (0, VecWriteWrapper(outputs), required),
481 &Event::PaymentForwarded { fee_earned_msat, claim_from_onchain_tx } => {
483 write_tlv_fields!(writer, {
484 (0, fee_earned_msat, option),
485 (2, claim_from_onchain_tx, required),
488 &Event::ChannelClosed { ref channel_id, ref user_channel_id, ref reason } => {
490 write_tlv_fields!(writer, {
491 (0, channel_id, required),
492 (1, user_channel_id, required),
493 (2, reason, required)
496 &Event::DiscardFunding { ref channel_id, ref transaction } => {
498 write_tlv_fields!(writer, {
499 (0, channel_id, required),
500 (2, transaction, required)
503 &Event::PaymentPathSuccessful { ref payment_id, ref payment_hash, ref path } => {
505 write_tlv_fields!(writer, {
506 (0, payment_id, required),
507 (2, payment_hash, option),
511 &Event::PaymentFailed { ref payment_id, ref payment_hash } => {
513 write_tlv_fields!(writer, {
514 (0, payment_id, required),
515 (2, payment_hash, required),
518 // Note that, going forward, all new events must only write data inside of
519 // `write_tlv_fields`. Versions 0.0.101+ will ignore odd-numbered events that write
520 // data via `write_tlv_fields`.
525 impl MaybeReadable for Event {
526 fn read<R: io::Read>(reader: &mut R) -> Result<Option<Self>, msgs::DecodeError> {
527 match Readable::read(reader)? {
528 // Note that we do not write a length-prefixed TLV for FundingGenerationReady events,
529 // unlike all other events, thus we return immediately here.
533 let mut payment_hash = PaymentHash([0; 32]);
534 let mut payment_preimage = None;
535 let mut payment_secret = None;
537 let mut _user_payment_id = None::<u64>; // For compatibility with 0.0.103 and earlier
538 read_tlv_fields!(reader, {
539 (0, payment_hash, required),
540 (2, payment_secret, option),
542 (6, _user_payment_id, option),
543 (8, payment_preimage, option),
545 let purpose = match payment_secret {
546 Some(secret) => PaymentPurpose::InvoicePayment {
548 payment_secret: secret
550 None if payment_preimage.is_some() => PaymentPurpose::SpontaneousPayment(payment_preimage.unwrap()),
551 None => return Err(msgs::DecodeError::InvalidValue),
553 Ok(Some(Event::PaymentReceived {
563 let mut payment_preimage = PaymentPreimage([0; 32]);
564 let mut payment_hash = None;
565 let mut payment_id = None;
566 let mut fee_paid_msat = None;
567 read_tlv_fields!(reader, {
568 (0, payment_preimage, required),
569 (1, payment_hash, option),
570 (3, payment_id, option),
571 (5, fee_paid_msat, option),
573 if payment_hash.is_none() {
574 payment_hash = Some(PaymentHash(Sha256::hash(&payment_preimage.0[..]).into_inner()));
576 Ok(Some(Event::PaymentSent {
579 payment_hash: payment_hash.unwrap(),
588 let error_code = Readable::read(reader)?;
590 let error_data = Readable::read(reader)?;
591 let mut payment_hash = PaymentHash([0; 32]);
592 let mut rejected_by_dest = false;
593 let mut network_update = None;
594 let mut all_paths_failed = Some(true);
595 let mut path: Option<Vec<RouteHop>> = Some(vec![]);
596 let mut short_channel_id = None;
597 let mut retry = None;
598 let mut payment_id = None;
599 read_tlv_fields!(reader, {
600 (0, payment_hash, required),
601 (1, network_update, ignorable),
602 (2, rejected_by_dest, required),
603 (3, all_paths_failed, option),
605 (7, short_channel_id, option),
607 (11, payment_id, option),
609 Ok(Some(Event::PaymentPathFailed {
614 all_paths_failed: all_paths_failed.unwrap(),
629 let mut outputs = VecReadWrapper(Vec::new());
630 read_tlv_fields!(reader, {
631 (0, outputs, required),
633 Ok(Some(Event::SpendableOutputs { outputs: outputs.0 }))
639 let mut fee_earned_msat = None;
640 let mut claim_from_onchain_tx = false;
641 read_tlv_fields!(reader, {
642 (0, fee_earned_msat, option),
643 (2, claim_from_onchain_tx, required),
645 Ok(Some(Event::PaymentForwarded { fee_earned_msat, claim_from_onchain_tx }))
651 let mut channel_id = [0; 32];
652 let mut reason = None;
653 let mut user_channel_id_opt = None;
654 read_tlv_fields!(reader, {
655 (0, channel_id, required),
656 (1, user_channel_id_opt, option),
657 (2, reason, ignorable),
659 if reason.is_none() { return Ok(None); }
660 let user_channel_id = if let Some(id) = user_channel_id_opt { id } else { 0 };
661 Ok(Some(Event::ChannelClosed { channel_id, user_channel_id, reason: reason.unwrap() }))
667 let mut channel_id = [0; 32];
668 let mut transaction = Transaction{ version: 2, lock_time: 0, input: Vec::new(), output: Vec::new() };
669 read_tlv_fields!(reader, {
670 (0, channel_id, required),
671 (2, transaction, required),
673 Ok(Some(Event::DiscardFunding { channel_id, transaction } ))
679 let mut payment_id = PaymentId([0; 32]);
680 let mut payment_hash = None;
681 let mut path: Option<Vec<RouteHop>> = Some(vec![]);
682 read_tlv_fields!(reader, {
683 (0, payment_id, required),
684 (2, payment_hash, option),
687 Ok(Some(Event::PaymentPathSuccessful {
697 let mut payment_hash = PaymentHash([0; 32]);
698 let mut payment_id = PaymentId([0; 32]);
699 read_tlv_fields!(reader, {
700 (0, payment_id, required),
701 (2, payment_hash, required),
703 Ok(Some(Event::PaymentFailed {
710 // Versions prior to 0.0.100 did not ignore odd types, instead returning InvalidValue.
711 // Version 0.0.100 failed to properly ignore odd types, possibly resulting in corrupt
714 // If the event is of unknown type, assume it was written with `write_tlv_fields`,
715 // which prefixes the whole thing with a length BigSize. Because the event is
716 // odd-type unknown, we should treat it as `Ok(None)` even if it has some TLV
717 // fields that are even. Thus, we avoid using `read_tlv_fields` and simply read
718 // exactly the number of bytes specified, ignoring them entirely.
719 let tlv_len: BigSize = Readable::read(reader)?;
720 FixedLengthReader::new(reader, tlv_len.0)
721 .eat_remaining().map_err(|_| msgs::DecodeError::ShortRead)?;
724 _ => Err(msgs::DecodeError::InvalidValue)
729 /// An event generated by ChannelManager which indicates a message should be sent to a peer (or
730 /// broadcast to most peers).
731 /// These events are handled by PeerManager::process_events if you are using a PeerManager.
732 #[derive(Clone, Debug)]
733 pub enum MessageSendEvent {
734 /// Used to indicate that we've accepted a channel open and should send the accept_channel
735 /// message provided to the given peer.
737 /// The node_id of the node which should receive this message
739 /// The message which should be sent.
740 msg: msgs::AcceptChannel,
742 /// Used to indicate that we've initiated a channel open and should send the open_channel
743 /// message provided to the given peer.
745 /// The node_id of the node which should receive this message
747 /// The message which should be sent.
748 msg: msgs::OpenChannel,
750 /// Used to indicate that a funding_created message should be sent to the peer with the given node_id.
752 /// The node_id of the node which should receive this message
754 /// The message which should be sent.
755 msg: msgs::FundingCreated,
757 /// Used to indicate that a funding_signed message should be sent to the peer with the given node_id.
759 /// The node_id of the node which should receive this message
761 /// The message which should be sent.
762 msg: msgs::FundingSigned,
764 /// Used to indicate that a funding_locked message should be sent to the peer with the given node_id.
766 /// The node_id of the node which should receive these message(s)
768 /// The funding_locked message which should be sent.
769 msg: msgs::FundingLocked,
771 /// Used to indicate that an announcement_signatures message should be sent to the peer with the given node_id.
772 SendAnnouncementSignatures {
773 /// The node_id of the node which should receive these message(s)
775 /// The announcement_signatures message which should be sent.
776 msg: msgs::AnnouncementSignatures,
778 /// Used to indicate that a series of HTLC update messages, as well as a commitment_signed
779 /// message should be sent to the peer with the given node_id.
781 /// The node_id of the node which should receive these message(s)
783 /// The update messages which should be sent. ALL messages in the struct should be sent!
784 updates: msgs::CommitmentUpdate,
786 /// Used to indicate that a revoke_and_ack message should be sent to the peer with the given node_id.
788 /// The node_id of the node which should receive this message
790 /// The message which should be sent.
791 msg: msgs::RevokeAndACK,
793 /// Used to indicate that a closing_signed message should be sent to the peer with the given node_id.
795 /// The node_id of the node which should receive this message
797 /// The message which should be sent.
798 msg: msgs::ClosingSigned,
800 /// Used to indicate that a shutdown message should be sent to the peer with the given node_id.
802 /// The node_id of the node which should receive this message
804 /// The message which should be sent.
807 /// Used to indicate that a channel_reestablish message should be sent to the peer with the given node_id.
808 SendChannelReestablish {
809 /// The node_id of the node which should receive this message
811 /// The message which should be sent.
812 msg: msgs::ChannelReestablish,
814 /// Used to indicate that a channel_announcement and channel_update should be broadcast to all
815 /// peers (except the peer with node_id either msg.contents.node_id_1 or msg.contents.node_id_2).
817 /// Note that after doing so, you very likely (unless you did so very recently) want to call
818 /// ChannelManager::broadcast_node_announcement to trigger a BroadcastNodeAnnouncement event.
819 /// This ensures that any nodes which see our channel_announcement also have a relevant
820 /// node_announcement, including relevant feature flags which may be important for routing
821 /// through or to us.
822 BroadcastChannelAnnouncement {
823 /// The channel_announcement which should be sent.
824 msg: msgs::ChannelAnnouncement,
825 /// The followup channel_update which should be sent.
826 update_msg: msgs::ChannelUpdate,
828 /// Used to indicate that a node_announcement should be broadcast to all peers.
829 BroadcastNodeAnnouncement {
830 /// The node_announcement which should be sent.
831 msg: msgs::NodeAnnouncement,
833 /// Used to indicate that a channel_update should be broadcast to all peers.
834 BroadcastChannelUpdate {
835 /// The channel_update which should be sent.
836 msg: msgs::ChannelUpdate,
838 /// Used to indicate that a channel_update should be sent to a single peer.
839 /// In contrast to [`Self::BroadcastChannelUpdate`], this is used when the channel is a
840 /// private channel and we shouldn't be informing all of our peers of channel parameters.
842 /// The node_id of the node which should receive this message
844 /// The channel_update which should be sent.
845 msg: msgs::ChannelUpdate,
847 /// Broadcast an error downstream to be handled
849 /// The node_id of the node which should receive this message
851 /// The action which should be taken.
852 action: msgs::ErrorAction
854 /// Query a peer for channels with funding transaction UTXOs in a block range.
855 SendChannelRangeQuery {
856 /// The node_id of this message recipient
858 /// The query_channel_range which should be sent.
859 msg: msgs::QueryChannelRange,
861 /// Request routing gossip messages from a peer for a list of channels identified by
862 /// their short_channel_ids.
864 /// The node_id of this message recipient
866 /// The query_short_channel_ids which should be sent.
867 msg: msgs::QueryShortChannelIds,
869 /// Sends a reply to a channel range query. This may be one of several SendReplyChannelRange events
870 /// emitted during processing of the query.
871 SendReplyChannelRange {
872 /// The node_id of this message recipient
874 /// The reply_channel_range which should be sent.
875 msg: msgs::ReplyChannelRange,
879 /// A trait indicating an object may generate message send events
880 pub trait MessageSendEventsProvider {
881 /// Gets the list of pending events which were generated by previous actions, clearing the list
883 fn get_and_clear_pending_msg_events(&self) -> Vec<MessageSendEvent>;
886 /// A trait indicating an object may generate events.
888 /// Events are processed by passing an [`EventHandler`] to [`process_pending_events`].
892 /// See [`process_pending_events`] for requirements around event processing.
894 /// When using this trait, [`process_pending_events`] will call [`handle_event`] for each pending
895 /// event since the last invocation. The handler must either act upon the event immediately
896 /// or preserve it for later handling.
898 /// Note, handlers may call back into the provider and thus deadlocking must be avoided. Be sure to
899 /// consult the provider's documentation on the implication of processing events and how a handler
900 /// may safely use the provider (e.g., see [`ChannelManager::process_pending_events`] and
901 /// [`ChainMonitor::process_pending_events`]).
903 /// (C-not implementable) As there is likely no reason for a user to implement this trait on their
906 /// [`process_pending_events`]: Self::process_pending_events
907 /// [`handle_event`]: EventHandler::handle_event
908 /// [`ChannelManager::process_pending_events`]: crate::ln::channelmanager::ChannelManager#method.process_pending_events
909 /// [`ChainMonitor::process_pending_events`]: crate::chain::chainmonitor::ChainMonitor#method.process_pending_events
910 pub trait EventsProvider {
911 /// Processes any events generated since the last call using the given event handler.
913 /// Subsequent calls must only process new events. However, handlers must be capable of handling
914 /// duplicate events across process restarts. This may occur if the provider was recovered from
915 /// an old state (i.e., it hadn't been successfully persisted after processing pending events).
916 fn process_pending_events<H: Deref>(&self, handler: H) where H::Target: EventHandler;
919 /// A trait implemented for objects handling events from [`EventsProvider`].
920 pub trait EventHandler {
921 /// Handles the given [`Event`].
923 /// See [`EventsProvider`] for details that must be considered when implementing this method.
924 fn handle_event(&self, event: &Event);
927 impl<F> EventHandler for F where F: Fn(&Event) {
928 fn handle_event(&self, event: &Event) {
933 impl<T: EventHandler> EventHandler for Arc<T> {
934 fn handle_event(&self, event: &Event) {
935 self.deref().handle_event(event)