X-Git-Url: http://git.bitcoin.ninja/index.cgi?a=blobdiff_plain;f=ARCH.md;h=9efccd9c9ddcec9d9812e0d0eb420975b3a0e98c;hb=6351a99935e81320abefb4c7e51c05c5fc8a62df;hp=e48568bdee476ec2ffa934385592fc6450f16156;hpb=dcffefae3dbc2b1fadc6b42ad39960bb4bc301d7;p=rust-lightning diff --git a/ARCH.md b/ARCH.md index e48568bd..9efccd9c 100644 --- a/ARCH.md +++ b/ARCH.md @@ -11,10 +11,10 @@ receive `ChannelMonitorUpdate`s from `ChannelManager` and persist them to disk b channel steps forward. There are two additional important structures that you may use either on the same device -as the `ChannelManager` or on a separate one. `NetGraphMsgHandler` handles receiving channel +as the `ChannelManager` or on a separate one. `P2PGossipSync` handles receiving channel and node announcements, which are then used to calculate routes by `find_route` for sending payments. `PeerManager` handles the authenticated and encrypted communication protocol, -monitoring for liveness of peers, routing messages to `ChannelManager` and `NetGraphMsgHandler` +monitoring for liveness of peers, routing messages to `ChannelManager` and `P2PGossipSync` instances directly, and receiving messages from them via the `EventsProvider` interface. These structs communicate with each other using a public API, so that you can easily add @@ -56,7 +56,7 @@ At a high level, some of the common interfaces fit together as follows: | ----------------- \ / ---------------- | ^ \ / | (as RoutingMessageHandler) | v v - \ ---------------------- --------- ----------------- - -----------------> | NetGraphMsgHandler | | Event | | chain::Filter | - ---------------------- --------- ----------------- + \ ----------------- --------- ----------------- + -----------------> | P2PGossipSync | | Event | | chain::Filter | + ----------------- --------- ----------------- ```