-
Notifications
You must be signed in to change notification settings - Fork 366
Meeting Notes 2021 08 23
Elias Rohrer edited this page Aug 9, 2022
·
1 revision
-
0.0.100 release last week! Woo
- Arik still working on a few ios bindings things. Otherwise bindings good
-
0.0.101 up next
-
997
- Event::ClosedChannel
- Need to fix tests
- todo(antoine): fix tests after the meeting
-
993 auto close on update_fee delay
- Matt: if we wanna update the fee, we should close if it takes too long. But currently we’ll send feeupdates even if the fee’s only increased by 1sat/vbyte. So we should have logic for, if the fee has gone up by at least X and has stayed up for at least X and there’s still an update_fee delay, THEN auto close
- We should also have logic for if the counterparty needs to update the fee
- Matt: might wanna use a diff fee estimator for need-to-close logic. We use FeeEstimator’s Normal rate for outbound case, but can use Background fee est for force close case
- Ariard: should check on what other impl’s are doing, then post on the PR
-
999
- Adding total fee paid to PaymentSent
-
1034 expose in-flight claim balances
- Val assigned to review
-
1041 check for outbound feerate affordability before sending
- 1054 PR solves it
- Ariard: need to do the test coverage on this one
-
1042 consider regenerating PendingHTLCsForwardable event
- Matt: should be quick
-
1043 part of jeff work on payment retries + scoring. Lot of precursor work
- Jeff to reply to last round of comments
- Getting there
- Jeff to have another PR open tonight. Finishing up tests and docs.
- Not too complicated but more than maybe preferred
-
- 1031 is adding ways to parse and handle custom msgs on LN
- Jeff left comments
- 619 has WIP DLC support
-
1013 warnings
- Pending rusty rebasing + answering qs
- No action item
-
1015 compression algo for advertising
- Matt: pending spec work. Need rebase.
- Action item: Matt to follow up w/ t-bast
-
1039
- Mostly done
- Action item: val to re-ack today
-
1055
- Just started
- Overall
- Blocked by needing anchor support in remote signer itself
- Don’t need fancy policy stuff, just anchor formatting in the outputs then we’re off and running
- Looking for a simple start on that
-
Release schedule
- Do we wanna be more rigorous about timing? Are we ok with the current somewhat ad-hoc?
- Jeff suggest continuing w/ current ad hoc. We’re faster than 6-8 weeks atm. Maybe as we mature more than get closer to 0.1, more schedule.
- Ariard: want more warning to say “the release is coming on this date” before making a release candidate. Fine with short cycle.
-
Bindings
- Steve did a call out for wasm/js support
- Matt: the problem is we have a lot of work, bindings are already a lot of work. We’d like to work on it but no time.
- We are down to fund someone to build this but no specific ideas rn
- Val+jeff met w/ conor this morning
- We’ll keep iterating. Expect to see some sort of draft out about ways to reorganize the docs
- Conor has a separate branch on lightningdevkit.org repo
- Folks in bitcoin design community came up w/ general look and feel
- LDK vs RL
- Ariard: i think we need to use LDK, even w/ other lightning devs
- Jeff: +1. RL is more of an implementation detail
- Matt: +1 i’ve been writing LDK
- Ariard: i think we need to use LDK, even w/ other lightning devs
- Community section
- Ariard to chat w/ conor about this
- Keysend bLIP
- Turbo spec