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)
62b5eedb4a
* BOLT 2: allow more leniancy with forks during channel establishment. Christoper points out that two nodes with aggressive minimum-depth settings may see different blocks and the protocol requires they close the channel since their funding_locked messages will disagree. This can also happen when only one side has an aggressive minimum-depth setting: if it sends funding_locked referring to a block which is orphaned, it can't update it. There are three changes here, two optional. - Allow sending of an updated funding_locked. This fixes this case where one side is on an orphan and uses a v. low minimum-depth. - Require accepting of an updated funding_locked. - Allow waiting instead of immediate failure if funding_lock disagrees. eg. you might wait another block or two to see if one side reorgs. Reported-by: Christopher Jämthagen Closes: #73 Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> |
||
|---|---|---|
| tools | ||
| 00-introduction.md | ||
| 01-messaging.md | ||
| 02-peer-protocol.md | ||
| 03-transactions.md | ||
| 04-onion-routing.md | ||
| 05-onchain.md | ||
| 06-irc-announcements.md | ||
| 07-routing-gossip.md | ||
| 08-transport.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.