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 use ln::channelmanager::{PaymentPreimage, PaymentHash, PaymentSecret};
19 use chain::keysinterface::SpendableOutputDescriptor;
20 use util::ser::{Writeable, Writer, MaybeReadable, Readable};
22 use bitcoin::blockdata::script::Script;
24 use bitcoin::secp256k1::key::PublicKey;
26 use std::time::Duration;
28 /// An Event which you should probably take some action in response to.
30 /// Note that while Writeable and Readable are implemented for Event, you probably shouldn't use
31 /// them directly as they don't round-trip exactly (for example FundingGenerationReady is never
32 /// written as it makes no sense to respond to it after reconnecting to peers).
33 #[derive(Clone, Debug)]
35 /// Used to indicate that the client should generate a funding transaction with the given
36 /// parameters and then call ChannelManager::funding_transaction_generated.
37 /// Generated in ChannelManager message handling.
38 /// Note that *all inputs* in the funding transaction must spend SegWit outputs or your
39 /// counterparty can steal your funds!
40 FundingGenerationReady {
41 /// The random channel_id we picked which you'll need to pass into
42 /// ChannelManager::funding_transaction_generated.
43 temporary_channel_id: [u8; 32],
44 /// The value, in satoshis, that the output should have.
45 channel_value_satoshis: u64,
46 /// The script which should be used in the transaction output.
47 output_script: Script,
48 /// The value passed in to ChannelManager::create_channel
51 /// Indicates we've received money! Just gotta dig out that payment preimage and feed it to
52 /// ChannelManager::claim_funds to get it....
53 /// Note that if the preimage is not known or the amount paid is incorrect, you should call
54 /// ChannelManager::fail_htlc_backwards to free up resources for this HTLC and avoid
55 /// network congestion.
56 /// The amount paid should be considered 'incorrect' when it is less than or more than twice
57 /// the amount expected.
58 /// If you fail to call either ChannelManager::claim_funds or
59 /// ChannelManager::fail_htlc_backwards within the HTLC's timeout, the HTLC will be
60 /// automatically failed.
62 /// The hash for which the preimage should be handed to the ChannelManager.
63 payment_hash: PaymentHash,
64 /// The "payment secret". This authenticates the sender to the recipient, preventing a
65 /// number of deanonymization attacks during the routing process.
66 /// As nodes upgrade, the invoices you provide should likely migrate to setting the
67 /// payment_secret feature to required, at which point you should fail_backwards any HTLCs
68 /// which have a None here.
69 /// Until then, however, values of None should be ignored, and only incorrect Some values
70 /// should result in an HTLC fail_backwards.
71 /// Note that, in any case, this value must be passed as-is to any fail or claim calls as
72 /// the HTLC index includes this value.
73 payment_secret: Option<PaymentSecret>,
74 /// The value, in thousandths of a satoshi, that this payment is for. Note that you must
75 /// compare this to the expected value before accepting the payment (as otherwise you are
76 /// providing proof-of-payment for less than the value you expected!).
79 /// Indicates an outbound payment we made succeeded (ie it made it all the way to its target
80 /// and we got back the payment preimage for it).
81 /// Note that duplicative PaymentSent Events may be generated - it is your responsibility to
82 /// deduplicate them by payment_preimage (which MUST be unique)!
84 /// The preimage to the hash given to ChannelManager::send_payment.
85 /// Note that this serves as a payment receipt, if you wish to have such a thing, you must
87 payment_preimage: PaymentPreimage,
89 /// Indicates an outbound payment we made failed. Probably some intermediary node dropped
90 /// something. You may wish to retry with a different route.
91 /// Note that duplicative PaymentFailed Events may be generated - it is your responsibility to
92 /// deduplicate them by payment_hash (which MUST be unique)!
94 /// The hash which was given to ChannelManager::send_payment.
95 payment_hash: PaymentHash,
96 /// Indicates the payment was rejected for some reason by the recipient. This implies that
97 /// the payment has failed, not just the route in question. If this is not set, you may
98 /// retry the payment via a different route.
99 rejected_by_dest: bool,
101 error_code: Option<u16>,
103 error_data: Option<Vec<u8>>,
105 /// Used to indicate that ChannelManager::process_pending_htlc_forwards should be called at a
106 /// time in the future.
107 PendingHTLCsForwardable {
108 /// The minimum amount of time that should be waited prior to calling
109 /// process_pending_htlc_forwards. To increase the effort required to correlate payments,
110 /// you should wait a random amount of time in roughly the range (now + time_forwardable,
111 /// now + 5*time_forwardable).
112 time_forwardable: Duration,
114 /// Used to indicate that an output was generated on-chain which you should know how to spend.
115 /// Such an output will *not* ever be spent by rust-lightning, and are not at risk of your
116 /// counterparty spending them due to some kind of timeout. Thus, you need to store them
117 /// somewhere and spend them when you create on-chain transactions.
119 /// The outputs which you should store as spendable by you.
120 outputs: Vec<SpendableOutputDescriptor>,
124 impl Writeable for Event {
125 fn write<W: Writer>(&self, writer: &mut W) -> Result<(), ::std::io::Error> {
127 &Event::FundingGenerationReady { .. } => {
129 // We never write out FundingGenerationReady events as, upon disconnection, peers
130 // drop any channels which have not yet exchanged funding_signed.
132 &Event::PaymentReceived { ref payment_hash, ref payment_secret, ref amt } => {
134 payment_hash.write(writer)?;
135 payment_secret.write(writer)?;
138 &Event::PaymentSent { ref payment_preimage } => {
140 payment_preimage.write(writer)?;
142 &Event::PaymentFailed { ref payment_hash, ref rejected_by_dest,
149 payment_hash.write(writer)?;
150 rejected_by_dest.write(writer)?;
152 error_code.write(writer)?;
154 error_data.write(writer)?;
156 &Event::PendingHTLCsForwardable { time_forwardable: _ } => {
158 // We don't write the time_fordwardable out at all, as we presume when the user
159 // deserializes us at least that much time has elapsed.
161 &Event::SpendableOutputs { ref outputs } => {
163 (outputs.len() as u64).write(writer)?;
164 for output in outputs.iter() {
165 output.write(writer)?;
172 impl MaybeReadable for Event {
173 fn read<R: ::std::io::Read>(reader: &mut R) -> Result<Option<Self>, msgs::DecodeError> {
174 match Readable::read(reader)? {
176 1u8 => Ok(Some(Event::PaymentReceived {
177 payment_hash: Readable::read(reader)?,
178 payment_secret: Readable::read(reader)?,
179 amt: Readable::read(reader)?,
181 2u8 => Ok(Some(Event::PaymentSent {
182 payment_preimage: Readable::read(reader)?,
184 3u8 => Ok(Some(Event::PaymentFailed {
185 payment_hash: Readable::read(reader)?,
186 rejected_by_dest: Readable::read(reader)?,
188 error_code: Readable::read(reader)?,
190 error_data: Readable::read(reader)?,
192 4u8 => Ok(Some(Event::PendingHTLCsForwardable {
193 time_forwardable: Duration::from_secs(0)
196 let outputs_len: u64 = Readable::read(reader)?;
197 let mut outputs = Vec::new();
198 for _ in 0..outputs_len {
199 outputs.push(Readable::read(reader)?);
201 Ok(Some(Event::SpendableOutputs { outputs }))
203 _ => Err(msgs::DecodeError::InvalidValue)
208 /// An event generated by ChannelManager which indicates a message should be sent to a peer (or
209 /// broadcast to most peers).
210 /// These events are handled by PeerManager::process_events if you are using a PeerManager.
211 #[derive(Clone, Debug)]
212 pub enum MessageSendEvent {
213 /// Used to indicate that we've accepted a channel open and should send the accept_channel
214 /// message provided to the given peer.
216 /// The node_id of the node which should receive this message
218 /// The message which should be sent.
219 msg: msgs::AcceptChannel,
221 /// Used to indicate that we've initiated a channel open and should send the open_channel
222 /// message provided to the given peer.
224 /// The node_id of the node which should receive this message
226 /// The message which should be sent.
227 msg: msgs::OpenChannel,
229 /// Used to indicate that a funding_created message should be sent to the peer with the given node_id.
231 /// The node_id of the node which should receive this message
233 /// The message which should be sent.
234 msg: msgs::FundingCreated,
236 /// Used to indicate that a funding_signed message should be sent to the peer with the given node_id.
238 /// The node_id of the node which should receive this message
240 /// The message which should be sent.
241 msg: msgs::FundingSigned,
243 /// Used to indicate that a funding_locked message should be sent to the peer with the given node_id.
245 /// The node_id of the node which should receive these message(s)
247 /// The funding_locked message which should be sent.
248 msg: msgs::FundingLocked,
250 /// Used to indicate that an announcement_signatures message should be sent to the peer with the given node_id.
251 SendAnnouncementSignatures {
252 /// The node_id of the node which should receive these message(s)
254 /// The announcement_signatures message which should be sent.
255 msg: msgs::AnnouncementSignatures,
257 /// Used to indicate that a series of HTLC update messages, as well as a commitment_signed
258 /// message should be sent to the peer with the given node_id.
260 /// The node_id of the node which should receive these message(s)
262 /// The update messages which should be sent. ALL messages in the struct should be sent!
263 updates: msgs::CommitmentUpdate,
265 /// Used to indicate that a revoke_and_ack message should be sent to the peer with the given node_id.
267 /// The node_id of the node which should receive this message
269 /// The message which should be sent.
270 msg: msgs::RevokeAndACK,
272 /// Used to indicate that a closing_signed message should be sent to the peer with the given node_id.
274 /// The node_id of the node which should receive this message
276 /// The message which should be sent.
277 msg: msgs::ClosingSigned,
279 /// Used to indicate that a shutdown message should be sent to the peer with the given node_id.
281 /// The node_id of the node which should receive this message
283 /// The message which should be sent.
286 /// Used to indicate that a channel_reestablish message should be sent to the peer with the given node_id.
287 SendChannelReestablish {
288 /// The node_id of the node which should receive this message
290 /// The message which should be sent.
291 msg: msgs::ChannelReestablish,
293 /// Used to indicate that a channel_announcement and channel_update should be broadcast to all
294 /// peers (except the peer with node_id either msg.contents.node_id_1 or msg.contents.node_id_2).
296 /// Note that after doing so, you very likely (unless you did so very recently) want to call
297 /// ChannelManager::broadcast_node_announcement to trigger a BroadcastNodeAnnouncement event.
298 /// This ensures that any nodes which see our channel_announcement also have a relevant
299 /// node_announcement, including relevant feature flags which may be important for routing
300 /// through or to us.
301 BroadcastChannelAnnouncement {
302 /// The channel_announcement which should be sent.
303 msg: msgs::ChannelAnnouncement,
304 /// The followup channel_update which should be sent.
305 update_msg: msgs::ChannelUpdate,
307 /// Used to indicate that a node_announcement should be broadcast to all peers.
308 BroadcastNodeAnnouncement {
309 /// The node_announcement which should be sent.
310 msg: msgs::NodeAnnouncement,
312 /// Used to indicate that a channel_update should be broadcast to all peers.
313 BroadcastChannelUpdate {
314 /// The channel_update which should be sent.
315 msg: msgs::ChannelUpdate,
317 /// Broadcast an error downstream to be handled
319 /// The node_id of the node which should receive this message
321 /// The action which should be taken.
322 action: msgs::ErrorAction
324 /// When a payment fails we may receive updates back from the hop where it failed. In such
325 /// cases this event is generated so that we can inform the network graph of this information.
326 PaymentFailureNetworkUpdate {
327 /// The channel/node update which should be sent to NetGraphMsgHandler
328 update: msgs::HTLCFailChannelUpdate,
330 /// Query a peer for channels with funding transaction UTXOs in a block range.
331 SendChannelRangeQuery {
332 /// The node_id of this message recipient
334 /// The query_channel_range which should be sent.
335 msg: msgs::QueryChannelRange,
337 /// Request routing gossip messages from a peer for a list of channels identified by
338 /// their short_channel_ids.
340 /// The node_id of this message recipient
342 /// The query_short_channel_ids which should be sent.
343 msg: msgs::QueryShortChannelIds,
345 /// Sends a reply to a channel range query. This may be one of several SendReplyChannelRange events
346 /// emitted during processing of the query.
347 SendReplyChannelRange {
348 /// The node_id of this message recipient
350 /// The reply_channel_range which should be sent.
351 msg: msgs::ReplyChannelRange,
355 /// A trait indicating an object may generate message send events
356 pub trait MessageSendEventsProvider {
357 /// Gets the list of pending events which were generated by previous actions, clearing the list
359 fn get_and_clear_pending_msg_events(&self) -> Vec<MessageSendEvent>;
362 /// A trait indicating an object may generate events
363 pub trait EventsProvider {
364 /// Gets the list of pending events which were generated by previous actions, clearing the list
366 fn get_and_clear_pending_events(&self) -> Vec<Event>;