Expose API to update a channel's ChannelConfig#1527
Merged
TheBlueMatt merged 5 commits intolightningdevkit:mainfrom Jun 21, 2022
Merged
Expose API to update a channel's ChannelConfig#1527TheBlueMatt merged 5 commits intolightningdevkit:mainfrom
TheBlueMatt merged 5 commits intolightningdevkit:mainfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A new
update_channel_configmethod is exposed on theChannelMangerto update the ChannelConfig for a set of channels atomically. New ChannelUpdate events are generated for each eligible channel.Note that as currently implemented, a buggy and/or auto-policy-management client could spam the network with updates as there is no rate-limiting in place. This could already be done with
broadcast_node_announcement, though users are less inclined to update that as frequently as its data is mostly static.Fixes #216.