1 //! Events are returned from various bits in the library which indicate some action must be taken
4 //! Because we don't have a built-in runtime, its up to the client to call events at a time in the
5 //! future, as well as generate and broadcast funding transactions handle payment preimages and a
8 //! Note that many events are handled for you by PeerHandler, so in the common design of having a
9 //! PeerManager which marshalls messages to ChannelManager and Router you only need to call
10 //! process_events on the PeerHandler and then get_and_clear_pending_events and handle the events
11 //! that bubble up to the surface. If, however, you do not have a PeerHandler managing a
12 //! ChannelManager you need to handle all of the events which may be generated.
13 //TODO: We need better separation of event types ^
16 use chain::transaction::OutPoint;
18 use bitcoin::blockdata::script::Script;
20 use secp256k1::key::PublicKey;
22 use std::time::Instant;
24 /// An Event which you should probably take some action in response to.
26 // Events a user will probably have to handle
27 /// Used to indicate that the client should generate a funding transaction with the given
28 /// parameters and then call ChannelManager::funding_transaction_generated.
29 /// Generated in ChannelManager message handling.
30 FundingGenerationReady {
31 /// The random channel_id we picked which you'll need to pass into
32 /// ChannelManager::funding_transaction_generated.
33 temporary_channel_id: [u8; 32],
34 /// The value, in satoshis, that the output should have.
35 channel_value_satoshis: u64,
36 /// The script which should be used in the transaction output.
37 output_script: Script,
38 /// The value passed in to ChannelManager::create_channel
41 /// Used to indicate that the client may now broadcast the funding transaction it created for a
42 /// channel. Broadcasting such a transaction prior to this event may lead to our counterparty
43 /// trivially stealing all funds in the funding transaction!
44 FundingBroadcastSafe {
45 /// The output, which was passed to ChannelManager::funding_transaction_generated, which is
46 /// now safe to broadcast.
47 funding_txo: OutPoint,
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, you must call ChannelManager::fail_htlc_backwards
54 /// to free up resources for this HTLC.
56 /// The hash for which the preimage should be handed to the ChannelManager.
57 payment_hash: [u8; 32],
58 /// The value, in thousandths of a satoshi, that this payment is for.
61 /// Indicates an outbound payment we made succeeded (ie it made it all the way to its target
62 /// and we got back the payment preimage for it).
64 /// The preimage to the hash given to ChannelManager::send_payment.
65 /// Note that this serves as a payment receipt, if you wish to have such a thing, you must
67 payment_preimage: [u8; 32],
69 /// Indicates an outbound payment we made failed. Probably some intermediary node dropped
70 /// something. You may wish to retry with a different route.
72 /// The hash which was given to ChannelManager::send_payment.
73 payment_hash: [u8; 32],
75 /// Used to indicate that ChannelManager::process_pending_htlc_forwards should be called at a
76 /// time in the future.
77 PendingHTLCsForwardable {
78 /// The earliest time at which process_pending_htlc_forwards should be called.
79 time_forwardable: Instant,
82 // Events indicating the network loop should send a message to a peer:
83 // TODO: Move these into a separate struct and make a top-level enum
84 /// Used to indicate that we've initialted a channel open and should send the open_channel
85 /// message provided to the given peer.
87 /// This event is handled by PeerManager::process_events if you are using a PeerManager.
89 /// The node_id of the node which should receive this message
91 /// The message which should be sent.
92 msg: msgs::OpenChannel,
94 /// Used to indicate that a funding_created message should be sent to the peer with the given node_id.
96 /// This event is handled by PeerManager::process_events if you are using a PeerManager.
98 /// The node_id of the node which should receive this message
100 /// The message which should be sent.
101 msg: msgs::FundingCreated,
103 /// Used to indicate that a funding_locked message should be sent to the peer with the given node_id.
105 /// This event is handled by PeerManager::process_events if you are using a PeerManager.
107 /// The node_id of the node which should receive these message(s)
109 /// The funding_locked message which should be sent.
110 msg: msgs::FundingLocked,
111 /// An optional additional announcement_signatures message which should be sent.
112 announcement_sigs: Option<msgs::AnnouncementSignatures>,
114 /// Used to indicate that a series of HTLC update messages, as well as a commitment_signed
115 /// message should be sent to the peer with the given node_id.
117 /// This event is handled by PeerManager::process_events if you are using a PeerManager.
119 /// The node_id of the node which should receive these message(s)
121 /// The update messages which should be sent. ALL messages in the struct should be sent!
122 updates: msgs::CommitmentUpdate,
124 /// Used to indicate that a shutdown message should be sent to the peer with the given node_id.
126 /// This event is handled by PeerManager::process_events if you are using a PeerManager.
128 /// The node_id of the node which should receive this message
130 /// The message which should be sent.
133 /// Used to indicate that a channel_announcement and channel_update should be broadcast to all
134 /// peers (except the peer with node_id either msg.contents.node_id_1 or msg.contents.node_id_2).
136 /// This event is handled by PeerManager::process_events if you are using a PeerManager.
137 BroadcastChannelAnnouncement {
138 /// The channel_announcement which should be sent.
139 msg: msgs::ChannelAnnouncement,
140 /// The followup channel_update which should be sent.
141 update_msg: msgs::ChannelUpdate,
143 /// Used to indicate that a channel_update should be broadcast to all peers.
145 /// This event is handled by PeerManager::process_events if you are using a PeerManager.
146 BroadcastChannelUpdate {
147 /// The channel_update which should be sent.
148 msg: msgs::ChannelUpdate,
152 /// Broadcast an error downstream to be handled
154 /// This event is handled by PeerManager::process_events if you are using a PeerManager.
156 /// The node_id of the node which should receive this message
158 /// The action which should be taken.
159 action: Option<msgs::ErrorAction>
163 /// A trait indicating an object may generate events
164 pub trait EventsProvider {
165 /// Gets the list of pending events which were generated by previous actions, clearing the list
167 fn get_and_clear_pending_events(&self) -> Vec<Event>;