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

Define a feature bit for extended gossip queries

Browse Source
This commit is contained in:
sstone 2019-08-06 11:40:10 +02:00 committed by Fabrice Drouin
parent 2f3514fe75
commit 30485af1df
2 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
07-routing-gossip.md
View File

@ -588,6 +588,8 @@ Query messages can be extended with optional fields that can help reduce the num
- timestamp-based filtering of `channel_update` messages: only ask for `channel_update` messages that are newer than the ones you already have. - timestamp-based filtering of `channel_update` messages: only ask for `channel_update` messages that are newer than the ones you already have.
- checksum-based filtering of `channel_update` messages: only ask for `channel_update` messages that carry different information from the ones you already have. - checksum-based filtering of `channel_update` messages: only ask for `channel_update` messages that carry different information from the ones you already have.
Nodes can signal that they support extended gossip queries with the `gossip_queries_ex` feature bit.
### The `query_short_channel_ids`/`reply_short_channel_ids_end` Messages ### The `query_short_channel_ids`/`reply_short_channel_ids_end` Messages
1. type: 261 (`query_short_channel_ids`) (`gossip_queries`) 1. type: 261 (`query_short_channel_ids`) (`gossip_queries`)

14
09-features.md
View File

@ -20,12 +20,13 @@ see [BOLT #1: The `init` Message](01-messaging.md#the-init-message).
These flags may only be used in the `init` message: These flags may only be used in the `init` message:
| Bits | Name | Description | Link | | Bits | Name | Description | Link |
|------|----------------------------------|---------------------------------------------------------------------------|------------------------------| |-------|----------------------------------|---------------------------------------------------------------------------|------------------------------|
| 0/1 | `option_data_loss_protect` | Requires or supports extra `channel_reestablish` fields | [BOLT #2][bolt02-retransmit] | | 0/1 | `option_data_loss_protect` | Requires or supports extra `channel_reestablish` fields | [BOLT #2][bolt02-retransmit] |
| 3 | `initial_routing_sync` | Indicates that the sending node needs a complete routing information dump | [BOLT #7][bolt07-sync] | | 3 | `initial_routing_sync` | Indicates that the sending node needs a complete routing information dump | [BOLT #7][bolt07-sync] |
| 4/5 | `option_upfront_shutdown_script` | Commits to a shutdown scriptpubkey when opening channel | [BOLT #2][bolt02-open] | | 4/5 | `option_upfront_shutdown_script` | Commits to a shutdown scriptpubkey when opening channel | [BOLT #2][bolt02-open] |
| 6/7 | `gossip_queries` | More sophisticated gossip control | [BOLT #7][bolt07-query] | | 6/7 | `gossip_queries` | More sophisticated gossip control | [BOLT #7][bolt07-query] |
| 10/11 | `gossip_queries_ex` | Gossip queries can include additional information | [BOLT #7][bolt07-query] |
## Assigned `globalfeatures` flags ## Assigned `globalfeatures` flags
@ -35,7 +36,6 @@ The following `globalfeatures` bits are currently assigned by this specification
|------|-------------------|--------------------------------------------------------------------|---------------------------------------| |------|-------------------|--------------------------------------------------------------------|---------------------------------------|
| 8/9 | `var_onion_optin` | This node requires/supports variable-length routing onion payloads | [Routing Onion Specification][bolt04] | | 8/9 | `var_onion_optin` | This node requires/supports variable-length routing onion payloads | [Routing Onion Specification][bolt04] |
## Requirements ## Requirements
The requirements for receiving specific bits are defined in the linked sections in the table above. The requirements for receiving specific bits are defined in the linked sections in the table above.