1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2025-03-13 19:37:31 +01:00

fixup! Make splice_locked atomic on reestablish

This commit is contained in:
t-bast 2025-02-28 11:10:55 +01:00
parent c79dca9696
commit 7a4053de28
No known key found for this signature in database
GPG key ID: 34F377B0100ED6BB

View file

@ -3271,6 +3271,9 @@ A node:
- if `next_commitment_number` is 1 in both the `channel_reestablish` it - if `next_commitment_number` is 1 in both the `channel_reestablish` it
sent and received: sent and received:
- MUST retransmit `channel_ready`. - MUST retransmit `channel_ready`.
- if `option_splice` was negotiated and `your_last_funding_locked` is not
set in the `channel_reestablish` it received:
- MUST retransmit `channel_ready`.
- otherwise: - otherwise:
- MUST NOT retransmit `channel_ready`, but MAY send `channel_ready` with - MUST NOT retransmit `channel_ready`, but MAY send `channel_ready` with
a different `short_channel_id` `alias` field. a different `short_channel_id` `alias` field.
@ -3417,7 +3420,7 @@ interactive transaction construction, or safely abort that transaction
if it was not signed by one of the peers, who has thus already removed if it was not signed by one of the peers, who has thus already removed
it from its state. it from its state.
`last_funding_locked` allows peers to detect that their `splice_locked` `your_last_funding_locked` allows peers to detect that their `splice_locked`
was lost during the disconnection and must be retransmitted. When a splice was lost during the disconnection and must be retransmitted. When a splice
transaction reaches acceptable depth while peers are disconnected, it also transaction reaches acceptable depth while peers are disconnected, it also
allows locking that splice transaction immediately after `channel_reestablish` allows locking that splice transaction immediately after `channel_reestablish`