Lightning Specification Meeting 2024/01/15

[t-bast]

The meeting will take place on Monday 2024/01/15 at 7pm UTC (5:30am Adelaide time) on Libera Chat IRC #lightning-dev. It is open to the public.

A video link is available for higher bandwidth communication: https://meet.jit.si/Lightning-Spec-Meeting

Special topics

• Mailing list host ending support in 2023, did that really happen?
• v3 transactions and ephemeral anchors support in lightning

Recently Updated Proposals / Seeking Review

This section contains changes that have been opened or updated recently and need feedback from the meeting participants.

• Dual funding interactive-tx: Add dual-funding flow, using the interactive tx protocol (feature 28/29) #851
• Simplified mutual close option_simple_close (features 60/61) #1096
• Trampoline routing Trampoline Routing (2021 edition) (Feature 56/57) #829 and Trampoline onion format (Feature 56/57) #836 (2024 is going to be the year of trampoline 🎉)
• Liquidity ads option_will_fund: liquidity ads #878
• Quiescence BOLT 2: quiescence protocol (feature 34/35) option_quiesce #869
• Offers Offers #798
• Taproot extension-bolt: simple taproot channels (feature 80/81) #995
• Taproot gossip extension-bolt: taproot gossip (features 32/33) #1059
• Attributable errors Attributable errors (feature 36/37) #1044
• Channel jamming draft: Staking Credentials token issuance/redemption #1043 draft: HTLC Endorsement to Mitigate Channel Jamming #1071
• Splicing Splice draft (feature 62/63) #863 vs Dynamic Commitments Extension/dynamic commitments #1117 vs Upgrade on reestablish BOLT 2: upgrade protocol on reestablish #868
• Peer storage backup Peer backup storage (feature 40/41/42/43) #881 or Peer storage for nodes to distribute small encrypted blobs. #1110
• Clarify channel_reestablish requirements Clarify channel_reestablish requirements #1049 or Rework channel_reestablish requirements #1051

Stale Proposals

This section contains pending changes that may not need feedback from the meeting participants, unless someone explicitly asks for it during the meeting. These changes are usually waiting for implementation work to happen to drive more feedback.

• Inbound fees Inbound routing fees blips#18 and Add a bLIP for backwards-compatible inbound fees blips#22

Waiting for interop

This section contains changes that have been conceptually ACKed and are waiting for at least two implementations to fully interoperate.
They most likely don't need to be covered during the meeting, unless someone asks for updates.

• Spec clean-up Clean up: remove two unused features, assume four more #1092
• Don't force close until error is received after channel_reestablish Nodes shouldn't publish their commitment when receiving outdated channel_reestablish #934

Long Term Updates

This section contains long-term changes that need review, but require a substantial implementation effort.

• Simplified commitment Feature 106/107: option_simplified_update. #867
• Hold htlcs before forwarding Add the ability to hold HTLCs before forwarding (FEAT 52/53) #989
• lnprototest (https://github.com/rustyrussell/lnprototest)

[instagibbs]

v3 transactions and ephemeral anchors support in lightning

Some reading which may help discussion on monday:

https://delvingbitcoin.org/t/an-overview-of-the-cluster-mempool-proposal/393

[carlaKC]

I've updated lightning/blips#27 with a write up of how we could roll out experimental endorsement signaling. Interested in hearing opinions on whether it should also include an experimental feature flag to help pick a flag day.

[ariard]

See https://lists.linuxfoundation.org/pipermail/lightning-dev/2023-June/003994.html and #1126. I won’t take part to the organization finally, as this year is very busy on my side. Apologies - I still owe the community a summit organization.

If there is still a summit happening this year, I’ll see to fit the dates in my agenda and comes to explain what are fee-dependent timelocks and why they matter for LN.

[ariard]

Of other interest for LN, all the conversation on v3 and its limits: bitcoin/bitcoin#28948 (comment)

[carlaKC]

Transcript: bitcointranscripts/bitcointranscripts#398