Lightning Dev Kit primary sources — 2026-05-02
Project status in this pass
- No canonical standalone whitepaper or litepaper surfaced.
- The clearest current source of truth is the official Lightning Dev Kit site, getting-started and sample-node docs, the LDK Node announcement post, and the public
rust-lightning/ldk-nodeREADMEs. - The materials consistently frame LDK as a modular Lightning SDK ecosystem rather than a monolithic node product.
Primary-source snapshots
1) Official homepage
- URL: https://lightningdevkit.org/
- Key excerpt:
- The homepage emphasizes LDK as “Flexible and customizable,” specifically naming persistence, networking, chain sourcing, routing, and key management.
- It also says LDK performs on small-footprint devices and scales in the cloud.
- The homepage further says LDK provides a multi-language native API for mobile, web, HSMs, LSPs, and existing infrastructure.
2) Getting-started docs
- URL: https://lightningdevkit.org/building-a-node-with-ldk/installation/
- Key excerpt:
- The installation docs show LDK being consumed through multiple crates and languages rather than as one compiled application.
- They provide install guidance for Rust, Kotlin, and Swift, which supports the view that LDK is a developer toolkit intended for embedding.
3) Running a sample LDK node
- URL: https://lightningdevkit.org/running-a-sample-ldk-node/
- Key excerpt:
- The guide says the sample setup is a quick start and “NOT recommended for production environments.”
- It also says “LDK doesn’t come with a pre-packaged node but gives you the tools to build a node from scratch.”
- This is one of the clearest single lines for categorizing LDK as infrastructure rather than turnkey wallet software.
4) rust-lightning README
- URL: https://raw.githubusercontent.com/lightningdevkit/rust-lightning/main/README.md
- Key excerpt:
- The README defines LDK /
rust-lightningas a “highly performant and flexible implementation of the Lightning Network protocol.” - It says the project implements all BOLT specifications and has been in production use since 2021.
- It enumerates a multi-crate architecture including
lightning,lightning-background-processor,lightning-block-sync,lightning-invoice,lightning-net-tokio,lightning-persister, andlightning-rapid-gossip-sync. - The README also explicitly says LDK is not itself a node and is instead for teams that want to integrate Lightning with custom chain sync, key management, storage/backup logic, or networking.
- It further notes that private keys can be supplied via custom APIs, including hardware-wallet-style setups, and that on-disk storage and networking are intentionally left open.
- The README defines LDK /
5) LDK Node announcement
- URL: https://lightningdevkit.org/blog/announcing-ldk-node/
- Key excerpt:
- The post says LDK fully implements Lightning as a highly modular Rust library but that its flexibility can raise integration complexity.
- It contrasts LDK’s “more than 900 exposed methods” with
ldk-node’s much smaller API surface of roughly 30 API calls. - It explains that
ldk-nodewas created to simplify self-custodial Lightning integration while remaining configurable enough for varied use cases. - The post also highlights mobile-first deployment, Esplora + Rapid Gossip Sync, integrated BDK wallet support, and Swift/Kotlin/Python bindings.
6) ldk-node README
- URL: https://raw.githubusercontent.com/lightningdevkit/ldk-node/main/README.md
- Key excerpt:
- The README defines LDK Node as “a self-custodial Lightning node in library form.”
- It says the main abstraction is a
Nodebuilt through a configurableBuilder, then controlled through methods such asstart,stop,open_channel, andsend. - It documents an opinionated but modular stack with integrated BDK wallet, Bitcoin Core RPC / Electrum / Esplora chain sources, SQLite/filesystem/custom persistence, Rapid Gossip Sync, BIP39 or raw-byte entropy, and Swift/Kotlin/Python bindings.
Working conclusion
Lightning Dev Kit is best cataloged as a modular Lightning integration stack for self-custodial applications, not as a single wallet or node product. The crucial evidence in this pass was the combination of the rust-lightning README’s explicit “LDK isn’t, in itself, a node” language and the separate ldk-node layer that packages a narrower, more opinionated self-custodial node library on top of the broader SDK.