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👇

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.

No custodian. No capacity tied up across the network. Async payments are in beta (LDK-to-LDK for now) and ready to explore: 📖 Blog: lightningdevkit.org/blog/async-pay… 🛠️ Integration guide: lightningdevkit.org/async-payments

@lightningdevkit Hey, your blog post mentions "This server hands out reusable invoices that deliberately omit the payment hash." Why require a server here to hand out.the reusable invoice? If it's reusable, can the user get it and then hand it out on his own, or even post it publicly?