Skip to content

Meeting Notes 2025 04 28

Elias Rohrer edited this page Apr 28, 2025 · 1 revision

LDK Releases

LDK Node Release

Language bindings

  • Will do a release with the new release today, language bindings in a day or two

Developer support

Feature progress

  • Attributable failures
    • No progress on LDK side but got updates from acinq and LL that they are working on it
    • Acinq has a new PR on it, +300 diff to get the feature in for them. Pretty compact
  • Async payments
    • Arik: been busy last week but back on it refactoring the trampoline forwarding PR taking advantage of the outbound payment module to get free retries
    • Got informed by shaavan that in a PR he’s working on there’s a regression in a trampoline unit test, so taking a look at that as well
  • RGS
    • Been stable, may take it off the agenda
  • VSS
  • Dual funding
    • Jkczyz meeting with dunxen on wednesday about this, just need review from one outstanding PR from wpaulino. Finishing DF for accepting
    • Have a draft PR for contributing inputs out
  • Splicing
    • Moving along, paused last week for travel
    • Jeff’s PR on splice_locked handling should be good for review soon
    • Working with leo on figuring out some of the monitor refactors we want to do for HTLC sources when we have multiple commitments to sign for
    • Have a design, just need to write the code now. Should unblock monitor work
    • Expect to have updates by the next sync

Open Q&A

  • Wvanlint: looking into memory issues with LDK java bindings
  • Previously, people were experimenting with jdmalloc. There was instruction to use ld_preload for that, but didn’t have the expected results
  • LDK java bindings: are they statically compiled? Does it include the allocator as well, meaning we can’t switch it out with LD_PRELOAD?
  • Matt: don’t think so. See whether it links libc. If you dump the symbols it links against, should see malloc in there, should be dynamically linked
  • M: based on previous data that showed consistent slow growth over time, didn’t seem as likely to be mem fragmentation where jdmalloc would solve it, seemed like an actual leak. Should chat offline more
Clone this wiki locally