Skip to content

Commit

Permalink
fixup! Make splice_locked atomic on reestablish
Browse files Browse the repository at this point in the history
  • Loading branch information
t-bast committed Feb 28, 2025
1 parent c79dca9 commit 7a4053d
Showing 1 changed file with 4 additions and 1 deletion.
5 changes: 4 additions & 1 deletion 02-peer-protocol.md
Original file line number Diff line number Diff line change
Expand Up @@ -3271,6 +3271,9 @@ A node:
- if `next_commitment_number` is 1 in both the `channel_reestablish` it
sent and received:
- 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:
- MUST NOT retransmit `channel_ready`, but MAY send `channel_ready` with
a different `short_channel_id` `alias` field.
Expand Down Expand Up @@ -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
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
transaction reaches acceptable depth while peers are disconnected, it also
allows locking that splice transaction immediately after `channel_reestablish`
Expand Down

0 comments on commit 7a4053d

Please sign in to comment.