You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
If there is enough compatibility testing between 2 implementations on #851, maybe it could be marked as finalized or landed. I think this is kinda a blocker to review / implement #863 as it unclear if it strictly building on it.
If there is enough compatibility testing between 2 implementations on #851, maybe it could be marked as finalized or landed.
We're getting close, but we're still missing interop tests on the channel_reestablish part. @niftynei is working on finalizing those on cln. Once those tests are done, we can do a final rebase of that PR and merge it 🚀
The meeting will take place on Monday 2023/08/28 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.
cltv_expiry
across implementations BOLT4: Specify max HTLC nLocktime for expiry_too_far #1086offer
blinded paths #1099Clarifychannel_reestablish
requirements Clarifychannel_reestablish
requirements #1049 or Reworkchannel_reestablish
requirements #1051Stale 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#22Liquidity ads option_will_fund: liquidity ads #878Sign commitments at various feerates Add option to sign commitments at various feerates (FEAT 32/33) #1036Waiting 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.
Dual funding interactive-tx: Add dual-funding flow, using the interactive tx protocol (feature 28/29) #851Don't force close until error is received afterchannel_reestablish
Nodes shouldn't publish their commitment when receiving outdatedchannel_reestablish
#934Websocket transport websocket address type: allow transport over RFC6455 #891 or Websocket address type: attempt 2 #1068Long Term Updates
This section contains long-term changes that need review, but require a substantial implementation effort.
Channel jamming draft: Staking Credentials token issuance/redemption #1043 draft: Upfront Fees to Mitigate Channel Jamming #1052 draft: HTLC Endorsement to Mitigate Channel Jamming #1071Peer storage backup Peer backup storage (feature 40/41/42/43) #881Hold htlcs before forwarding Add the ability to hold HTLCs before forwarding (FEAT 52/53) #989Trampoline routing Trampoline Routing (2021 edition) (Feature 56/57) #829 and Trampoline onion format (Feature 56/57) #836The text was updated successfully, but these errors were encountered: