Splice draft (feature 62/63) #863

Signed-off-by: Rusty Russell <[email protected]>

This is especially useful for protocols such as splicing; for simplified commitment transactions, there is already an implied initiator at each point, so having the negotiation at splicing time would be redundant. Signed-off-by: Rusty Russell <[email protected]>

@niftynei

… channel. The initiator (in the case of simultaneity, the higher feepayer) pays for the input and output, and sets the feerate. We freeze the channel while this construction is going on: it should be quick. Signed-off-by: Rusty Russell <[email protected]> Header from folded patch 'fixup3.patch': fixup! splicing: use the generic negotiation mechanism to splice in/out of a channel. - Remove 1 per minute restriction: 25% growth limits us a lot (@niftynei) - Nomenclature: initiator, splice transaction, channel funding output. - Weaken reserve check to only cover iff they extract funds.

This is much simpler. Signed-off-by: Rusty Russell <[email protected]>

Signed-off-by: Rusty Russell <[email protected]>

Signed-off-by: Rusty Russell <[email protected]> Header from folded patch 'fixup2.patch': fixup! splice_locked: terminate this splice once one reaches agreed depths. Use 6; we need to start announcing then anyway, so keep it simple.

This was Matt Corallo's idea; a simple flag means you should keep using the channel as it's being replaced. Signed-off-by: Rusty Russell <[email protected]>

Signed-off-by: Rusty Russell <[email protected]> Header from folded patch 'fixup.patch': fixup! gossip: make sure to send new announcement_signatures post-splice. It's called `splice_locked` and it's always sent 6 blocks.

…etting fees. Any changes must be valid for all possible commitment transactions. A minor change, but for implementations which quote the spec and check those quotes this will highlight the changes needed. Signed-off-by: Rusty Russell <[email protected]>

`commitment_signed` is valid when a splice is candidate added.

* the commitment tx includes the splice transaction commitment signatures (not the splice transaction’s own signatures). * “in progress” -> “awaiting confirmation” to add clarity. * No longer need a 10 block delay for splice closes since all close events are delayed 12 blocks.

@niftynei

Adding @niftynei’s shutdown updates. Her notes: `shutdown` MAY be sent while the splice is pending confirmation. New splice negotiations MAY BE initiated while the channel is in `shutdown`. The `shutdown` phase MUST NOT be considered concluded until all htlcs are resolved and the channel has exited the pending splice phase (`splice_locked` has been exchanged).

The closing process, begining with `closing_signed` must not begin until one of the candidate splices is confirmed.

instead of a (potentially large) commitment_tlv

for a bundle of `commitment_signed` messages.

Splice now uses single `commitment_signed` message and `tx_signatures` order is enoucrage to be smaller added amount first but is not required.

* commitment_signed is now sent a single time while a splice is being negotiated * adding a spec for `splice_locked` * additional logic for avoding splice_locked race condition

…ut of a channel. Co-authored-by: ProofOfKeags <[email protected]>

…epths.

Using relative sat amounts simplifies multiple aspects of the protocol.

In cases where one side has sent `splice_locked` but the peer is attempting to resume splicing negotiation via reestablish we must re-send `splice_locked` This can occur if only one side has received splice signatures, and the peer goes offline. During this time the transaction may be published and confirmed. When the peer comes online it will be requesting splice signatures (via `next_funding_txid`) but since the transaction is already confirmed we must jump ahead to `splice_locked`.

A pending splice is one waiting for confirmation which is seperate from an ongoing splice negotation. Adjusting the language to remove ambiguity.

The interactive tx protocol must only use confirmed inputs.

Formally known as `funding_locked`

Jump to message numer 80 to avoid conflicts with `stfu` etc

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Splice draft (feature 62/63) #863

Splice draft (feature 62/63) #863

Commits on Feb 13, 2024