mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2025-03-13 11:35:41 +01:00
Code Issues Projects Releases Wiki Activity
BOLT: Basis of Lightning Technology (Lightning Network Specifications)
1077 commits 17 branches 1 tag 8 MiB
Markdown 98.4%
Shell 0.8%
Python 0.8%
Find a file
Matt Corallo 6849c33d86 Do not unnecessarily retransmit commitment_signed in dual funding 
On reconnection in the middle of the dual-funding flow, if both
nodes have exchanged the initial `commitment_signed` and node A
had sent its (initial) `tx_signatures` but node B never received
them, both nodes should send a `channel_reestablish` with
`next_funding_txid` set and a `next_commitment_number` of 1 (as
they've already received the commitment transaction for commitment
number 0).

The spec indicates in this case that both nodes should retransmit
their `commitment_signed`, however, as this is only gated on
`next_funding_txid` and not the `next_commitment_number` field.
This may cause implementations which assume that each new
`commitment_signed` is for a new state to fail and potentially
fail the channel.

Instead, we should rely both the presence of `next_funding_txid`
*and* `next_commitment_number` being zero to decide if we need to
resend our `commitment_signed`. Sadly, we cannot rely on just
`next_commitment_number` as that is used to request a force-closure
in a non-standard way to work around implementations not honoring
the `error` message.
2025-01-14 16:53:46 +00:00
bolt04 BOLT 4: fix nomenclature in bolt04/route-blinding-test.json 2024-07-30 06:57:20 +09:30
bolt07 Add test vector for extended queries 2019-09-16 22:36:59 +02:00
bolt12 Leftover renaming of path_key in blinded paths 2024-12-03 12:21:43 +10:30
proposals Leftover renaming of path_key in blinded paths 2024-12-03 12:21:43 +10:30
tools tools/spellcheck.sh: more generally ignore things inside ``. 2024-09-24 19:40:59 +09:00
.aspell.en.pws BOLT 12: offers, sixth draft 2024-09-24 19:40:59 +09:00
.copy-edit-stylesheet-checklist.md Fix typos 2019-09-26 06:12:41 +00:00
.gitattributes Make Markdown linguist-detectable (#930) 2021-10-25 20:55:05 +02:00
.travis.yml spelling: check all the .md files 2019-07-28 07:03:19 +00:00
00-introduction.md Fix typo: 'them' instead of 'her' (#1005) 2022-06-27 08:24:41 +02:00
01-messaging.md Add a sciddir_or_pubkey fundamental type 2024-09-24 19:40:59 +09:00
02-peer-protocol.md Do not unnecessarily retransmit commitment_signed in dual funding 2025-01-14 16:53:46 +00:00
03-transactions.md Fix broken links to anchor section (#1000) 2024-09-18 13:32:39 +02:00
04-onion-routing.md BOLT 4: add bolt12 payloads to onion message payloads. 2024-09-24 19:40:59 +09:00
05-onchain.md Clean-up: follow-up on removing spec features 2024-05-21 10:58:55 +02:00
07-routing-gossip.md BOlT07: clarify dont_forward bit use cases. (#1198) 2024-09-18 13:37:56 +02:00
08-transport.md BOLT 8: make it clear that there are *two* chaining keys. 2023-07-18 05:38:27 +09:30
09-features.md Make blinded link work (#1190) 2024-08-12 17:00:39 +02:00
10-dns-bootstrap.md BOLT 10 copy edit (#440) 2018-08-07 00:10:11 +00:00
11-payment-encoding.md Bolt 11: add example SHA256 hash of description (#994) 2024-09-18 11:09:49 +02:00
12-offer-encoding.md Include BIP 353 name info in invoice_requests 2024-10-21 19:28:22 +00:00
CoC.md Add the folks who signed up as CoC members 2024-11-04 21:48:13 +00:00
CONTRIBUTING.md CONTRIBUTING.md: modern feature bit assignment. 2023-09-26 05:42:35 +09:30
README.md Fix typo in name mailing list name (#931) 2021-10-27 15:54:09 +02:00

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

Creative Commons License
This work is licensed under a Creative Commons Attribution 4.0 International License.