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)
6ac177f95c
The spec already prepared a hook to add additional information to existing messages (additional bytes at the end of a message must be ignored). Since we're using TLV in many places, it makes sense to use that optional additional space at the end of each message to allow an optional tlv stream. This requires making a few previously optional fields mandatory: - channel_reestablish commitment points: it makes sense to always include those regardless of whether `option_dataloss_protect` or `option_static_remotekey` are set. - option_upfront_shutdown_script: if you're not using one, just set the length to 0. That field is moved to a TLV record because luckily, the resulting bytes are the same. This provides more flexibility to later remove the requirement of making this field mandatory. No need to change the `channel_update`'s `htlc_maximum_msat` because the `message_flags` encode its presence/absence. It can still be either included or omitted without causing issues to the extension stream. |
||
|---|---|---|
| bolt04 | ||
| bolt07 | ||
| tools | ||
| .aspell.en.pws | ||
| .copy-edit-stylesheet-checklist.md | ||
| .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 lighting-dev mailing list.
Start here for Table of Contents
This work is licensed under a Creative Commons Attribution 4.0 International License.