You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Do not always persist ChannelManager on channel_update messages
If we receive a `channel_update` message for a channel unrelated to
our own, we shouldn't trigger a persistence of our
`ChannelManager`. This avoids significant persistence traffic during
initial node startup.
// If the announcement is about a channel of ours which is public, some
3364
3365
// other peer may simply be forwarding all its gossip to us. Don't provide
3365
3366
// a scary-looking error message and return Ok instead.
3366
-
returnOk(());
3367
+
returnOk(NotifyOption::SkipPersist);
3367
3368
}
3368
3369
returnErr(MsgHandleErrInternal::send_err_msg_no_close("Got a channel_update for a channel from the wrong node - it shouldn't know about our private channels!".to_owned(), chan_id));
0 commit comments