mirror of
https://github.com/lightning/bolts.git
synced 2024-11-19 01:50:03 +01:00
BOLT: Basis of Lightning Technology (Lightning Network Specifications)
2e8f2095a3
Gossip query compression is not very useful - it was added for mobile clients to, in theory, sync the gossip data directly from P2P peers, but to my knowledge no mobile clients actually use it for that, or at least use it where the gossip *query* data is a substantial portion of their overall bandwidth usage. Further, because of the semantics of `gossip_timestamp_filter`, its impractical to ensure you receive a reliable, full view of the gossip data without re-downloading large portions of the gossip data on startup. Ultimately, gossip queries are a pretty non-optimal method of synchronizing the gossip data. If someone wants highly optimized gossip data synchronization a new method based on set reconciliation needs to be propose. Finally, the current gossip query encoding semantics do not allow for negotiation and instead require all lightning implementations take a zlib dependency in some form or another. Given the recent zlib decoding memory corruption vulnerability, this seems like an opportune time to simply remove the zlib support, requiring that nodes stop sending compressed gossip query data (though they can support reading such gossip query data as long as they wish). This is an alternative to the suggested gossip query encoding support in #825. |
||
---|---|---|
bolt04 | ||
bolt07 | ||
tools | ||
.aspell.en.pws | ||
.copy-edit-stylesheet-checklist.md | ||
.gitattributes | ||
.travis.yml | ||
00-introduction.md | ||
01-messaging.md | ||
02-peer-protocol.md | ||
03-transactions.md | ||
04-onion-routing.md | ||
05-onchain.md | ||
07-routing-gossip.md | ||
08-transport.md | ||
09-features.md | ||
10-dns-bootstrap.md | ||
11-payment-encoding.md | ||
CONTRIBUTING.md | ||
README.md |
Lightning Network In-Progress Specifications
The specifications are currently a work-in-progress and currently being drafted.
Pull requests and comments welcome, seeking input from community stakeholders.
Discussion available on the lightning-dev mailing list.
Start here for Table of Contents
This work is licensed under a Creative Commons Attribution 4.0 International License.