Matt Corallo 989cb064b5 Move broadcast_node_announcement to PeerManager ... Some `NodeFeatures` will, in the future, represent features which are not enabled by the `ChannelManager`, but by other message handlers handlers. Thus, it doesn't make sense to determine the node feature bits in the `ChannelManager`. The simplest fix for this is to change to generating the node_announcement in `PeerManager`, asking all the connected handlers which feature bits they support and simply OR'ing them together. While this may not be sufficient in the future as it doesn't consider feature bit dependencies, support for those could be handled at the feature level in the future. This commit moves the `broadcast_node_announcement` function to `PeerHandler` but does not yet implement feature OR'ing.		2022-09-08 19:50:36 +00:00
..
src	Move broadcast_node_announcement to PeerManager	2022-09-08 19:50:36 +00:00
Cargo.toml	Merge pull request #1657 from TheBlueMatt/2022-08-async-man-update	2022-09-06 16:06:06 -04:00