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/07/01 #1175

Closed
16 of 23 tasks
t-bast opened this issue Jun 26, 2024 · 1 comment
Closed
16 of 23 tasks

Lightning Specification Meeting 2024/07/01 #1175

t-bast opened this issue Jun 26, 2024 · 1 comment

Comments

@t-bast
Copy link
Collaborator

t-bast commented Jun 26, 2024

The meeting will take place on Monday 2024/07/01 at 8pm 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 Jun 26, 2024
@Roasbeef
Copy link
Collaborator

Roasbeef commented Jul 1, 2024

blinded paths example:

blinded paths in legacy invoice format:

  • blinded paths have to use it
    • has a required feature bit
    • no hop hints
    • random pubkey (not actually in graph)
  • could also expose via bolt12 invoice as well, would need to ignore some existing fields

Offers:

  • shipping Phoenix w/ BOLT12 this week! on testnet rn, tested w/ LDK, minor issue w/ CLN interop
  • edge case re blinded paths:
    • if you give us a blinded path that leads to us, need to detect it
  • dummy hops:
    • for the Offer only use a single hop
    • for the actual blinded path invoice, use 3 of them, one of them is the real node (6 nodes by default?)

taproot:

  • bug fixes for 2 issues roasbeef brought up addressed (sequence mismatch, and local/remote script pattern matching)
  • eclair nearly finished implementation wise
    • need to add a commit to add extra nonces for the splice use case

channel jamming:

  • lnd now has APis that allow deciding if the endorsement bit should be propagated or not
  • carla working on integrating new APIs for more dynamic logic

async payments:

  • pushed update modifying a feature bit in the onion
  • waiting for feedback
  • lot of focus on shipping BOLT12, can check this out more deeply after shipped

splicing:

  • dusty checking out the spec again
  • eclair doesn't support with custom channels, using temporary values and messages types for public channels

dyn commits:

  • splitting dyn commits into kick off related stuff, and just the param or commitment output changes
  • 3 diff categories:
    • changes to boundaries on state space (max htlc, etc)
    • change to params to render state into a commitment txn (needs re-signing, anchor update, etc)
    • funding output conversion (may use kick off)

liquidity ads:

  • nearly completed impl of on the fly funding, looking for feedback on the format, etc

@t-bast t-bast unpinned this issue Jul 12, 2024
@t-bast t-bast closed this as completed Jul 12, 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

2 participants