mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2024-11-19 01:50:03 +01:00
Code Issues Projects Releases Wiki Activity

BOLT 9: remove feature bit for channels_public

Browse Source 
This commit removes the feature bit for channels_public as they have
been deprecated by the addition of the `announce_channel` field in the
`open_channel` message.
This commit is contained in:
Olaoluwa Osuntokun 2017-05-15 12:33:02 -07:00 committed by Rusty Russell
parent 667ca1fdd6
commit 5e666b6c99
1 changed files with 0 additions and 20 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
09-features.md
View File

@ -17,7 +17,6 @@ These flags may only be used in the `init` message:
| Bits | Name |Description | Link |
|------|------------------|------------------------------------------------|---------------------------------------------------------------------|
| 0/1 | `channels_public` | The sending node wishes to announce channels | [BOLT #7](07-routing-gossip.md#the-announcement_signatures-message) |
| 3 | `initial_routing_sync` | The sending node needs a complete routing information dump | [BOLT #7](07-routing-gossip.md#initial-sync) |
## Assigned `globalfeatures` flags
@ -27,31 +26,12 @@ These flags may only be used in the `init` message:
(Note that the requirements for feature bits which are not defined
above, can be found in [BOLT #1: The `init` message](#the-init-message)). The requirements when receiving set bits are defined in the linked section in the table above).
Additional requirements:
* `channels_public`: the sender MUST set exactly one of these bits if
it wants to announce the channel publicly, otherwise it MUST set
neither. If it sets one it MUST set the even bit if it will fail the
connection if the other node does not also set one of the
`channels_public` bits, otherwise it MUST set the odd bit. The
receiver MUST terminate the connection if neither `channels_public`
bit is set and it set the even `channels_public` bit on the `init`
message it sent, otherwise the receiver SHOULD treat either bit the
same.
## Rationale
There's little point insisting on an `initial_routing_sync` (you can't
tell if the remote node complies, and it has to know what it means as
it's defined in the initial spec) so there's no even bit for that.
There is a some point in insisting on channels being public: a node
may not want to serve any private channels, and this gives clear
indication, so that uses both bits. You can read these bits as "odd:
I would like the channel to be public" and "even: I require that the
channel be public".
![Creative Commons License](https://i.creativecommons.org/l/by/4.0/88x31.png "License CC-BY")
<br>
This work is licensed under a [Creative Commons Attribution 4.0 International License](http://creativecommons.org/licenses/by/4.0/).