Most Lightning software answers the question "how do I run a node". LDK answers a different one: how does an application that already exists add Lightning without inheriting somebody else's node.
The core is rust-lightning, whose repository dates from February 2018 and which is
dual-licensed under Apache 2.0 or MIT at the user's option. Its README states that the
project implements all of the BOLT specifications and has been in production use since
2021. The primary lightning crate is runtime-agnostic and supports no_std. Persistence,
chain data, networking and key management are not provided: you supply them, or you use one
of LDK's sample modules. That is the whole design argument. A wallet that already has an
encrypted database, a chain source and a key hierarchy does not want a second copy of any
of them, and a hardware security module or an embedded device may not be able to run one.
LDK is not itself a node. ldk-sample and ldk-node exist for people who want the
out-of-the-box version, and LDK Server is a deployable node built on the same libraries.
The project also publishes bindings so the same code runs from languages other than Rust.
What it changed is visible in who uses it. The project's own case studies cover Alby Hub's self-custodial wallet, the Fedimint Lightning gateway, Lexe running self-custodial nodes inside Intel SGX enclaves, Lightspark's infrastructure, and LQWD's liquidity service. The project has also shipped infrastructure the whole ecosystem borrows from, including the Versioned Storage Service for server-side storage of mobile and hosted wallet state, announced in March 2025, and work on asynchronous payments that lets an often-offline node receive without a custodian and without long-lived HTLCs.
The project publishes under its contributors' own names: the write-up of how LDK's pathfinder works is authored by Matt Corallo, and the async payments post by Valentine Wallace and Conor Okus.
Governance is the gap. The site's copyright reads "LDK Developers" and no legal entity, foundation or steward is published anywhere on it, so no structure is recorded here.