Imagine a future where we could link multiple Lightning addresses from different wallets on platforms like Nostr—or anywhere else. Why is this important? If one address goes offline, you’d have a backup ready, ensuring you never miss a zap.
I recently noticed that BTCPay Server allows you to create multiple Lightning addresses, which is incredibly useful. However, there’s a limitation: all those addresses are tied to the same instance. If the entire instance goes down—rare, but not impossible—the backup plan falls apart.
A potential solution could be running two separate BTCPay Server instances, with one serving as a backup. While this adds complexity, it’s a step towards true resilience.
BTCPay is still in its early stages with Lightning, but it has immense potential to dominate the space. Its features make it an excellent tool for being self-sovereign, eliminating reliance on third-party Lightning wallets. That said, Lightning itself remains a bit finicky, and even with my own Lightning node, I frequently encounter errors.
Still, the future is promising. BTCPay could lead the way in creating robust solutions like this. It’s just an idea to inspire developers to think about what’s next.
Note ID:
note1zl20kckvh3vctxln90henx9nuv4yp2p5xxl4mug25amsu240lvgsz207w0
Post#171