[−][src]Module lnpbp::lnp::application
Re-exports
pub use extension::ChannelExtension; |
pub use extension::Extension; |
pub use extension::GossipExtension; |
pub use extension::RoutingExtension; |
pub use message::Messages; |
pub use message::OnionPacket; |
pub use message::LNPWP_UNMARSHALLER; |
pub use message::LNPWP_UNMARSHALLER; |
pub use peer_connection::PeerConnection; |
pub use peer_connection::PeerReceiver; |
pub use peer_connection::PeerSender; |
pub use peer_connection::RecvMessage; |
pub use peer_connection::SendMessage; |
pub use rpc_connection::RpcConnection; |
Modules
| channel | |
| extension | |
| factories | |
| message | |
| payment | |
| peer_connection | BOLT-1. Manages state of the remote peer and handles direct communications with it. Relies on transport layer (BOLT-8-based) protocol. |
| prometheus | |
| rpc_connection | |
| storm |
Structs
| FeatureFlag | |
| Features | Flags are numbered from the least-significant bit, at bit 0 (i.e. 0x1, an even bit). They are generally assigned in pairs so that features can be introduced as optional (odd bits) and later upgraded to be compulsory (even bits), which will be refused by outdated nodes: see BOLT #1: The init Message. |
Enums
| FeatureContext | Some features don't make sense on a per-channels or per-node basis, so each feature defines how it is presented in those contexts. Some features may be required for opening a channel, but not a requirement for use of the channel, so the presentation of those features depends on the feature itself. |