Lightning Specification Meeting 2025/04/07

by ADMIN 43 views

Overview

The Lightning Specification Meeting is a crucial event for the Lightning Network community, where developers and stakeholders gather to discuss and review recent updates, proposals, and long-term changes to the Lightning Network protocol. The meeting will take place on Monday, 2025/04/07, at 8pm UTC (5:30am Adelaide time) on Libera Chat IRC [#lightning-dev]. The meeting is open to the public, and a video link is available for higher bandwidth communication: https://meet.jit.si/Lightning-Spec-Meeting.

Recently Updated Proposals / Seeking Review

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

Assume payment_secret #1242

  • Proposal: Assume payment_secret is a valid payment secret.
  • Description: This proposal aims to simplify the payment process by assuming that the payment_secret is a valid payment secret. This change will reduce the complexity of the payment process and make it more user-friendly.
  • Impact: This change will simplify the payment process and reduce the complexity of the payment process.

Clarify Bolt 11 invoice requirements #1243

  • Proposal: Clarify the requirements for Bolt 11 invoices.
  • Description: This proposal aims to clarify the requirements for Bolt 11 invoices, ensuring that all parties involved in the payment process understand the requirements.
  • Impact: This change will ensure that all parties involved in the payment process understand the requirements for Bolt 11 invoices.

Remove CoC #1241

  • Proposal: Remove the Code of Conduct (CoC) from the Lightning Network protocol.
  • Description: This proposal aims to remove the CoC from the Lightning Network protocol, as it is no longer necessary.
  • Impact: This change will remove the CoC from the Lightning Network protocol.

Splicing #1160

  • Proposal: Implement splicing in the Lightning Network protocol.
  • Description: This proposal aims to implement splicing in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement splicing in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Taproot #995

  • Proposal: Implement Taproot in the Lightning Network protocol.
  • Description: This proposal aims to implement Taproot in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement Taproot in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Taproot gossip #1059

  • Proposal: Implement Taproot gossip in the Lightning Network protocol.
  • Description: This proposal aims to implement Taproot gossip in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement Taproot gossip in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Dual funding reconnect commit_sig retransmission #1214

  • Proposal: Implement dual funding reconnect commit_sig retransmission in the Lightning Network protocol.
  • Description: proposal aims to implement dual funding reconnect commit_sig retransmission in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement dual funding reconnect commit_sig retransmission in the Lightning Network protocol, allowing for more efficient and secure payment processing.

BOLT 12 recurrence #1240

  • Proposal: Implement BOLT 12 recurrence in the Lightning Network protocol.
  • Description: This proposal aims to implement BOLT 12 recurrence in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement BOLT 12 recurrence in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Allow non-initiator to RBF dual-funded channels #1236

  • Proposal: Allow non-initiator to RBF dual-funded channels in the Lightning Network protocol.
  • Description: This proposal aims to allow non-initiator to RBF dual-funded channels in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will allow non-initiator to RBF dual-funded channels in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Assume option_channel_type #1232

  • Proposal: Assume option_channel_type is a valid channel type.
  • Description: This proposal aims to simplify the payment process by assuming that the option_channel_type is a valid channel type.
  • Impact: This change will simplify the payment process and reduce the complexity of the payment process.

Trampoline routing #829 and #836

  • Proposal: Implement trampoline routing in the Lightning Network protocol.
  • Description: This proposal aims to implement trampoline routing in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement trampoline routing in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Async payments #1149

  • Proposal: Implement async payments in the Lightning Network protocol.
  • Description: This proposal aims to implement async payments in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement async payments in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Dynamic Commitments #1117

  • Proposal: Implement dynamic commitments in the Lightning Network protocol.
  • Description: This proposal aims to implement dynamic commitments in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement dynamic commitments in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Attributable errors #1044

  • Proposal: Implement attributable errors in the Lightning Network protocol.
  • Description: This proposal aims to implement attributable errors in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement attributable errors in the Lightning Network protocol, allowing for more efficient and secure payment processing.

0-fee commitments #1228

  • Proposal: Implement 0-fee commitments in the Lightning Network protocol.
  • Description: This proposal aims to 0-fee commitments in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement 0-fee commitments in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Channel jamming #1071 #1218

  • Proposal: Implement channel jamming in the Lightning Network protocol.
  • Description: This proposal aims to implement channel jamming in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement channel jamming in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Bolt 12 contacts: https://github.com/lightning/blips/pull/42

  • Proposal: Implement Bolt 12 contacts in the Lightning Network protocol.
  • Description: This proposal aims to implement Bolt 12 contacts in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement Bolt 12 contacts in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Liquidity ads #1153

  • Proposal: Implement liquidity ads in the Lightning Network protocol.
  • Description: This proposal aims to implement liquidity ads in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement liquidity ads in the Lightning Network protocol, allowing for more efficient and secure payment processing.

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 https://github.com/lightning/blips/pull/18 and https://github.com/lightning/blips/pull/22

  • Proposal: Implement inbound fees in the Lightning Network protocol.
  • Description: This proposal aims to implement inbound fees in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement inbound fees in the Lightning Network protocol, allowing for more efficient and secure payment processing.

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.

Zero reserve #1140 (follow-up on #1133 to include a feature bit)

  • Proposal: Implement zero reserve in the Lightning Network protocol.
  • Description: This proposal aims to implement zero reserve in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement zero reserve in the Lightning Network protocol, allowing for more efficient and secure payment processing.

Don't force close until error is received after channel_reestablish #934

  • Proposal: Implement don't force close until error is received after channel_reestablish in the Lightning Network protocol.
  • Description: This proposal aims to implement don't force close until error is received after channel_reestablish in the Lightning Network protocol, allowing for more efficient and secure payment processing.
  • Impact: This change will implement't force close until error is received after channel_reestablish in the Lightning Network protocol, allowing for more efficient and secure payment processing
    Lightning Specification Meeting 2025/04/07 Q&A =====================================================

Q: What is the purpose of the Lightning Specification Meeting?

A: The Lightning Specification Meeting is a crucial event for the Lightning Network community, where developers and stakeholders gather to discuss and review recent updates, proposals, and long-term changes to the Lightning Network protocol.

Q: What are the main topics that will be discussed during the meeting?

A: The main topics that will be discussed during the meeting include:

  • Recently updated proposals and their impact on the Lightning Network protocol
  • Stale proposals and their status
  • Waiting for interop changes and their implementation status
  • Long-term updates and their implementation status

Q: What is the format of the meeting?

A: The meeting will be held on Libera Chat IRC [#lightning-dev] and will be open to the public. A video link will also be available for higher bandwidth communication: https://meet.jit.si/Lightning-Spec-Meeting.

Q: Who can attend the meeting?

A: The meeting is open to the public, and anyone can attend.

Q: What is the agenda for the meeting?

A: The agenda for the meeting will include:

  • Review of recently updated proposals
  • Review of stale proposals
  • Review of waiting for interop changes
  • Review of long-term updates
  • Q&A session

Q: How can I participate in the meeting?

A: You can participate in the meeting by:

Q: What is the expected outcome of the meeting?

A: The expected outcome of the meeting is to:

  • Review and discuss recent updates, proposals, and long-term changes to the Lightning Network protocol
  • Provide feedback and input on the proposals and changes
  • Identify areas for improvement and potential solutions
  • Set the agenda for future meetings

Q: How can I get involved in the Lightning Network community?

A: You can get involved in the Lightning Network community by:

  • Attending meetings and events
  • Participating in discussions on Libera Chat IRC [#lightning-dev]
  • Contributing to the development of the Lightning Network protocol
  • Sharing your knowledge and expertise with the community

Q: What are the benefits of participating in the Lightning Specification Meeting?

A: The benefits of participating in the Lightning Specification Meeting include:

  • Staying up-to-date with the latest developments in the Lightning Network protocol
  • Providing feedback and input on proposals and changes
  • Identifying areas for improvement and potential solutions
  • Networking with other developers and stakeholders in the community

Q: How can I stay informed about the Lightning Network community?

A: You can stay informed about the Lightning Network community by:

  • Following the Lightning Network community on social media
  • Subscribing to Lightning Network community newsletter
  • Attending meetings and events
  • Participating in discussions on Libera Chat IRC [#lightning-dev]