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
Would like to add "taproot" to the long-term updates section. Possibly both the nearer term taproot-ification, as well as the possible paths to inclusion in the gossip layer.
The meeting will take place on Monday 2022/01/03 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
Pull Request Review
channel_reestablish
requirements Clarify and relax requirements onchannel_reestablish
#932Route blinding Route Blinding (Feature 24/25) #765Onion messages BOLT 7: Onion message support (features 38/39) #759Add dust exposure threshold Add amax_dust_htlc_exposure_msat
#919Simple turbo channels enablement Explicitly allow funding_locked early, and support alias scids (feat 46/47/50/51) #910Dynamic DNS support in gossip messages BOLT 7: add gossip address descriptor type DNS hostname #911 or BOLT 1: adds remote address to optional init_tlvs (IP discovery) #917Long Term Updates
Dual funding interactive-tx: Add dual-funding flow, using the interactive tx protocol (feature 28/29) #851Liquidity ads option_will_fund: liquidity ads #878Splicing Splice draft (feature 62/63) #863Offers Offers #798Simplified commitment Feature 106/107: option_simplified_update. #867Trampoline routing Trampoline Routing (2021 edition) (Feature 56/57) #829 and Trampoline onion format (Feature 56/57) #836Upfront payments / DoS protection Hold fees #843Peer storage backup Peer backup storage (feature 40/41/42/43) #881Anonymous gossipTaproot updatesBacklog
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.
lnprototest (https://github.com/rustyrussell/lnprototest)The text was updated successfully, but these errors were encountered: