Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Lightning Specification Meeting 2024/12/02 #1210

Closed
12 of 19 tasks
t-bast opened this issue Nov 22, 2024 · 4 comments
Closed
12 of 19 tasks

Lightning Specification Meeting 2024/12/02 #1210

t-bast opened this issue Nov 22, 2024 · 4 comments

Comments

@t-bast
Copy link
Collaborator

t-bast commented Nov 22, 2024

The meeting will take place on Monday 2024/12/02 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

Recently Updated Proposals / Seeking Review

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

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.

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.

Long Term Updates

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

@t-bast t-bast pinned this issue Nov 22, 2024
@t-bast
Copy link
Collaborator Author

t-bast commented Nov 22, 2024

I'm back in a timezone that is more friendly to the spec meeting ;)

@vincenzopalazzo
Copy link
Contributor

I'm back in a timezone that is more friendly to the spec meeting ;)

Welcome back :)

@vincenzopalazzo
Copy link
Contributor

Probably before the end of the meeting next week, we can discuss the following PRs

I feel that these just need a decision to close or merge them, in this way, we have less PRs stuck in the queue

@Roasbeef
Copy link
Collaborator

Roasbeef commented Dec 2, 2024

rbf close:

  • t-bast and roasbeef to do final interop this week
  • fabrice has updated with the taproot branch, and works w/ the extra nonces
  • main change:
    • when you resend a shutdown, other party should also send a response
    • makes the taproot add on easier, can just add the nonces along

liquidity ads:

  • updated the TLV values to not conflict with the older version of liquidity ads
    • lets you run the new and the old versions concurrently, now has distinct TLV types
  • ready for impl and review

peer storage back ups:

  • eclair has a version for cross compat
  • do the others have a fully updated version?
  • (CLN <-> eclair) to do interop testing
  • bluematt has some outstanding comments, adi to respond+update PR

taproot gossip:

bip 353 invoice request:

splicing:

  • interop zone w/ eclair <-> CLN
  • eclair before only had support for unannounced channels
  • dusty was able to test w/ un announced channels, everything worked fine -- need to test the gossip part
    • super close, just have one core change in CLN
    • related to rotating pubkeys, more depth than at the surface

dyn commits:

  • lnd working on impl still

channel jamming:

  • carla catching up w/ post tokyo revisions
  • lnd PR to start to set endorsements

async payments:

  • trampoline routing w/ blinded payments ready to go

blinded path related errors:

  • how do you handle blinded paths 1 one hop?
    • you could simulate failures, and penalize the introduction node?
      • eclair: don't punish blinded path intro nodes at all
      • CLN: we'll remember insufficient capacity for that payment session
  • BOLT 12 version:
    • onion messaging addition gives an ability to send more error information
      * soft errors:
    • send this back, but don't close the error
    • more specific solution than using onion messaging

@t-bast t-bast unpinned this issue Dec 9, 2024
@t-bast t-bast closed this as completed Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants