Skip to content

Add a feature bit to allow nodes to opt-out of channel updates #218

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
Roasbeef wants to merge 2 commits into from
Closed

Add a feature bit to allow nodes to opt-out of channel updates #218

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
7561ac4
BOLT0007: add section on ability of nodes to opt out of dynamic updates
Roasbeef Aug 7, 2017
d36e7d8
BOLT0009: add a `no_channel_updates` feature bit
Roasbeef Aug 7, 2017
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
19 changes: 19 additions & 0 deletions 07-routing-gossip.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -423,6 +423,25 @@ Other more advanced considerations involve diversity of routes to
avoid single points of failure and detection, and channel balance
of local channels.

## Opting out of `channel_update` messages

A peer may wish to update out of receiving any `channel_update` messages as a
bandwidth and processing optimization. Note that opting out of `channel_update`
messages doesn't entirely affect a node's ability to interact with the network.
In the case of a node that wishes to send semi-frequent payments, if a payment
fails due to using an outdated routing policy for a particular channel link,
then the error response will contain the latest `channel_update` message for
that link. For nodes which are primarily focused on payment forwarding, the
extra traffic of `channel_update` messages are unnecessary.

In order to opt-out of `channel_update` messages the `no_channel_updates` flag
should be set within the `init` message that the node advertises to other peers
upon initial connection.

If a node receives an `init` message with the `no_channel_updates` flag set,
then the receiving not MUST NOT relay any channel update messages to the
Copy link
Copy Markdown

@jonathancross jonathancross Sep 2, 2017 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Minor typo: "...then the receiving node MUST NOT relay any..."

sending node.

## References

![Creative Commons License](https://i.creativecommons.org/l/by/4.0/88x31.png "License CC-BY")
Expand Down
1 change: 1 addition & 0 deletions 09-features.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ These flags may only be used in the `init` message:
| Bits | Name |Description | Link |
|------|------------------|------------------------------------------------|---------------------------------------------------------------------|
| 3 | `initial_routing_sync` | The sending node needs a complete routing information dump | [BOLT #7](07-routing-gossip.md#initial-sync) |
| 0xc | `no_channel_updates` | The sending node doesn't wish to receive any `channel_update` messages | [BOLT #7](07-routing-gossip.md) |

## Assigned `globalfeatures` flags

Expand Down