X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=blobdiff_plain;ds=sidebyside;f=src%2Fln%2Fmod.rs;h=9b1b442a9237ff1ff2ccfba7117904241c6a169c;hb=f99acc6d35ba30f37f772dbaaf15711889fc6563;hp=1f5fa460afbf7d71972da1b7ba3283b1d5e41340;hpb=6185a2819090bd077954244c5e2adaab5efcaa1a;p=rust-lightning

diff --git a/src/ln/mod.rs b/src/ln/mod.rs
index 1f5fa460..9b1b442a 100644
--- a/src/ln/mod.rs
+++ b/src/ln/mod.rs
@@ -1,9 +1,32 @@
+//! High level lightning structs and impls live here.
+//!
+//! You probably want to create a channelmanager::ChannelManager, and a router::Router first.
+//! Then, you probably want to pass them both on to a peer_handler::PeerManager and use that to
+//! create/manage connections and call get_and_clear_pending_events after each action, handling
+//! them appropriately.
+//!
+//! When you want to open/close a channel or send a payment, call into your ChannelManager and when
+//! you want to learn things about the network topology (eg get a route for sending a payment),
+//! call into your Router.
+
 pub mod channelmanager;
-pub mod channel;
 pub mod channelmonitor;
 pub mod msgs;
 pub mod router;
-pub mod peer_channel_encryptor;
 pub mod peer_handler;
 
+#[cfg(feature = "fuzztarget")]
+pub mod peer_channel_encryptor;
+#[cfg(not(feature = "fuzztarget"))]
+pub(crate) mod peer_channel_encryptor;
+
+mod channel;
 mod chan_utils;
+mod onion_utils;
+
+#[cfg(test)]
+#[macro_use] mod functional_test_utils;
+#[cfg(test)]
+mod functional_tests;
+#[cfg(test)]
+mod chanmon_update_fail_tests;