-
Notifications
You must be signed in to change notification settings - Fork 492
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 2021/06/21 #879
Comments
As usual, feel free to add topics, especially @rustyrussell if there's a topic you'd like to cover among quiescence, protocol upgrade, or the other PRs you started working on. |
Would like to add this topic #873 as well, I updated it with a comment to address IRC comments. I'll be available during the spec meeting to talk about it also. |
We can definitely talk about it during the meeting if you think it's necessary. |
Meeting logs can be found here: https://lightningd.github.io/meetings/ln_spec_meeting/2021/ln_spec_meeting.2021-06-21-20.06.log.html |
The meeting will take place on Monday 2021/06/21 at 8pm UTC on Libera Chat IRC #lightning-dev. It is open to the public.
Pull Request Review
channel_type
negotiation BOLT 2: send channel_type in open/accept #880Clarify when max-accepted-htlcs applies clarification: when does max_accepted_htlcs apply? #745Long Term Updates
Dual funding interactive-tx: Add dual-funding flow, using the interactive tx protocol (feature 28/29) #851Splicing Splice draft (feature 62/63) #863Trampoline routing Trampoline Routing (2021 edition) (Feature 56/57) #829 and Trampoline onion format (Feature 56/57) #836 (@t-bast)Offers Offers #798 (@rustyrussell)Upfront payments / DoS protection Hold fees #843Blinded paths Route Blinding (Feature 24/25) #765 (@t-bast)Backlog
The following are topics that we should discuss at some point, so if we have time to discuss them great, otherwise they slip to the next meeting.
Hornet (@cfromknecht)lnprototest https://github.com/rustyrussell/lnprototest (@rustyrussell)The text was updated successfully, but these errors were encountered: