Lightning Dev Kit

The Lightning Dev Kit project is building tools and libraries that make it easy to integrate Lightning features in #Bitcoin wallets.

[Lightning Dev Kit @lightningdevkit]

1/ In case you missed the announcement from @benthecarman, we are releasing a production-grade Lightning node for servers.

Everything that powers the likes of @CashApp, @Square, @moneydevkit, @lightspark, @lexeapp, and @getalby is packaged as a daemon anyone can run.

[Tony @tonklaus]

Here's the Stable Channels Lightning Server dashboard UX 👇 built on @lightningdevkit by @benthecarman, @_tnull @Biresh_Biswas et al. (node IDs/numbers changed)

Little ⓘ buttons explain Lightning jargon throughout. We hope to bring it to Umbrel ASAP when LDK Server ships!

[Lightning Dev Kit @lightningdevkit]

@ProjectLoupe @nishant282003 We'd also like to thank Aziz Pulatov for helping to find issues.

[Lightning Dev Kit @lightningdevkit]

Thanks to @ProjectLoupe, @nishant282003, and Erick Cestari for reporting these issues.

2/4

[Lightning Dev Kit @lightningdevkit]

LDK development has moved to Forgejo. You can still find the code on GitHub, where it will stay in sync.

Release notes:
0.1.13: https://t.co/CQSHOSA8CB
0.2.7: https://t.co/3xdmz5GQXm
0.3-rc3: https://t.co/FGNUGBZGkq

4/4

[Lightning Dev Kit @lightningdevkit]

LDK 0.3 is getting close. It adds splicing improvements, async signing, LSPS1 service support, and BOLT 12 payer proofs.

Please test rc3 and read the compatibility notes before upgrading.

3/4

[Lightning Dev Kit @lightningdevkit]

LDK 0.1.13, 0.2.7, and 0.3-rc3 are now available, with fixes for several security vulnerabilities, including fund theft.

If you run LDK in production with untrusted channel counterparties, we recommend upgrading today. If you’re testing 0.3, update to rc3.

1/4

[EVAN KALOUDIS @evankaloudis]

Just got a demo of splicing in @ZeusLN's LDK 'node in the phone' wallet.

This means paying and receiving via Lightning and on-chain with a single balance. Also a great UX improvement on current swaps functionality.

Hoping to get it in everyone's hands by end of year.

[Lightning Dev Kit @lightningdevkit]

https://t.co/rhfDZu9H2M

[Lightning Dev Kit @lightningdevkit]

LDK Server is still in pre-release, but you can already manage a node with an AI agent.

ldk-server-mcp exposes every node RPC as a tool over MCP — Claude Code, Codex CLI, Goose or any MCP client.

Ask "which channels are low on outbound liquidity?" instead of doing the math ⬇️

[Tony @tonklaus]

Me waiting for the next @lightningdevkit releases

[Lexe @lexeapp]

Lexe now supports zero-reserve and zero-fee commitment transactions (0FC)! After updating your node to v0.10.0, new channels can spend their balance all the way down to 0, finally solving the "unspendable balance" UX issue. 🎉

0FC arriving in Lexe is only the final step in a long chain of work 😉 across multiple software layers, open-source devs, and companies. Many thanks to:
- @glozow and @theinstagibbs for shipping TRUC (v3) txs, P2A, 1P1C package relay, and ephemeral dust in Bitcoin Core v29+
- @lightningdevkit, @spiral_xyz, @TheBlueMatt, @tankyleo, Wilmer Paulino for working on the spec and shipping LDK 0.3.0-beta1 with 0FC and 0 punishment reserve support
- @Blockstream, @mempool, @bitcoindevkit for Esplora submitpackage support

[Lightning Dev Kit @lightningdevkit]

2/ We recommend upgrading at your next opportunity.

https://t.co/T0FnQUTF97
https://t.co/UwmaVK7cnN

[Lightning Dev Kit @lightningdevkit]

1/ New releases: LDK 0.1.12 and 0.2.5 are on https://t.co/gUofsf0RcT with a handful of security fixes from our ongoing code review efforts. Release notes have the full rundown ⬇️

[Tony @tonklaus]

Over $250B of value sits in stablecoins instead of Bitcoin. Stable Channels is built to change that.

This demo 👇 features the @stablechannels server and iOS app, powered by splicing, just-in-time channels, and new server tech from @lightningdevkit, @bitcoindevkit & @spiral_xyz

[grubles @notgrubles]

Really enjoyed looking into this. The componentry provided by @lightningdevkit is really what helped enable it.

It's great because the benefits gained aren't necessarily Bark-specific. The mobile Lightning wallet ecosystem more generally can take advantage too. ⚡️

[Second @secondhq]

1/ Wallet apps built on Bark have never done their own Lightning pathfinding: the Ark server works out the best path on their behalf. It works great, but some users want more control, or don't want to share destination data. New research from @notgrubles explores an alternative.

[Renat Skitsan @skitsanr]

True power of @lightningdevkit and RLN(RGB Lightning Node)

Remember this?
https://t.co/mwry6PQYPn

Lightning in the browser is back - with BTC and USDT support

[Vincenzo Palazzo 🟥 @PalazzoVincenzo]

Payer proof is now merged in @lightningdevkit and ack on the Bolts PR

https://t.co/BUB5Uk5qbe

6 months and more than 500 PR comments, just to show how much we care about code quality

Now, fix the broken zap on nostr with bolt12 and shill https://t.co/LMkg3Va21r for a client-side payer proof rendering

[Lightning Dev Kit @lightningdevkit]

No custodian. No capacity tied up across the network. Async payments are in beta (LDK-to-LDK for now) and ready to explore:

📖 Blog: https://t.co/j88ojL9CYp
🛠️ Integration guide: https://t.co/Ahdw5NBhxd

[Lightning Dev Kit @lightningdevkit]

1/ Receiving a Lightning payment has always meant being online at the right moment. That assumption breaks down on mobile, where your app often can't wake up to claim an incoming payment.

Async payments fix this👇

[Lightning Dev Kit @lightningdevkit]

2/ With async payments, an often-offline node (like the phone in your pocket) can receive Lightning payments without:

🚫 trusting a custodian with your funds
🚫 locking up network liquidity

An LSP holds a static invoice and relays the release message until you're back online.