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)
93b7ee031b
As noted previously, `channel_update`s in the onion failure packets are massive gaping fingerprintign vulnerabilities - if a node applies them in a publicly-visible way the err'ing node can easily identify the sender of an HTLC. While the updates are still arguably marginally useful for nodes to use in their pathfinding local to retires of the same payment, this too will eventually become an issue with PTLCs. Further, we shouldn't be letting nodes get away with delaying payments by failing to announce the latest channel parameters or enforcing new parameters too soon, so treating the node as having indicated insufficient liquidity (or other general failure) is appropriate in the general case. Thus, here, we begin phasing out the `channel_update` field, requiring nodes ignore it outside of the current payment and making it formally optional (though nodes have been doing this for some time due to various bugs). Because some nodes may want to use update data on mobile when they have stale gossip data, it is left optional. |
||
---|---|---|
bolt04 | ||
bolt07 | ||
proposals | ||
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.