-
Notifications
You must be signed in to change notification settings - Fork 43
Adds LQWD case study #290
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Adds LQWD case study #290
Changes from 2 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
fae4cd4
Adds LQWD case study
ConorOkus b912275
Add LQWD diagram
ConorOkus 912cc59
Update date
ConorOkus ca1e9ea
Update docs/_blog/lqwd-liquidity-provider-get-liquidity-when-you-need…
ConorOkus 45680d4
Update docs/_blog/lqwd-liquidity-provider-get-liquidity-when-you-need…
ConorOkus 39b9db8
Update docs/_blog/lqwd-liquidity-provider-get-liquidity-when-you-need…
ConorOkus 0f0ffa9
Update docs/_blog/lqwd-liquidity-provider-get-liquidity-when-you-need…
ConorOkus 5097969
Update docs/_blog/lqwd-liquidity-provider-get-liquidity-when-you-need…
ConorOkus 49e395c
Update docs/_blog/lqwd-liquidity-provider-get-liquidity-when-you-need…
ConorOkus 49d2633
Update docs/_blog/lqwd-liquidity-provider-get-liquidity-when-you-need…
ConorOkus b77721a
Update docs/_blog/lqwd-liquidity-provider-get-liquidity-when-you-need…
ConorOkus File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
49 changes: 49 additions & 0 deletions
49
docs/_blog/lqwd-liquidity-provider-get-liquidity-when-you-need-it.md
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,49 @@ | ||
--- | ||
title: "LQWD Liquidity Provider: Get Liquidity When You Need It" | ||
description: "Learn how LQWD built a custom LSP" | ||
date: "2025-01-13" | ||
authors: | ||
- Aziz Pulatov | ||
tags: | ||
- Case-Studies | ||
--- | ||
|
||
The rapid growth of the Lightning Network has created unprecedented demand for liquidity. Traditionally, receiving payments on the Lightning Network required pre-established channels which posed barriers to new users and hindered scalability. With the introduction of [LSPS2](https://github.com/lightning/blips/blob/master/blip-0052.md) and its Just-In-Time (JIT) channel negotiation capabilities, the Lightning Network can now provide liquidity exactly when needed, improving both accessibility and efficiency. By leveraging [LDK Node](https://lightningdevkit.org/blog/announcing-ldk-node/) (a higher-level wrapper of LDK) and the [Lightning Liquidity crate](https://github.com/lightningdevkit/rust-lightning/tree/main/lightning-liquidity)—both Rust-based implementations—we developed a specialized LSP Node [(LQwD)](https://lqwdtech.com/). This node enables real-time liquidity provisioning by dynamically creating channels, ensuring payments can be received without prior investments in channel capacity. | ||
|
||
# Challenges Before LSPS2 | ||
ConorOkus marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
Before the advent of LSPS2, receiving payments on the Lightning Network was fraught with limitations. Users were required to have pre-established channels, creating significant friction during the onboarding process and hindering adoption. | ||
ConorOkus marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
Liquidity allocation was inefficient: static channels often resulted in unused capacity, tying up valuable funds that could have been better utilized elsewhere. Furthermore, scaling liquidity across the network required substantial investment and extensive pre-planning, making it | ||
challenging to achieve the flexibility and responsiveness required for a growing user base. | ||
|
||
 | ||
|
||
# Why LSPS2 with LDK Node and Lightning Liquidity? | ||
ConorOkus marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
LSPS2, integrated with LDK Node and the Lightning Liquidity crate, offers a transformative solution to these challenges. Its dynamic liquidity management enables channels to be created on demand, perfectly aligning with real-time payment requirements and eliminating the need for | ||
ConorOkus marked this conversation as resolved.
Show resolved
Hide resolved
|
||
pre-established liquidity. | ||
|
||
The flexible and modular design of LDK Node, built on Rust and enhanced by the Lightning Liquidity crate, allows for the development of a highly customized and efficient LSP Node tailored to meet dynamic liquidity needs. | ||
|
||
# Building the LSP Node (LQwD) | ||
|
||
The integration of LDK and Lightning Liquidity allowed us to create a streamlined and algorithmically driven LSP Node capable of managing liquidity requests dynamically. | ||
|
||
The process begins when a client initiates a liquidity request by interacting with the LSP Node. In response, the LSP Node generates a Short Channel ID (SCID), accompanied by routing information and timeout parameters, and sends these details back to the client. | ||
|
||
Following this, the client prepares an invoice that embeds the SCID and the LSP Node ID as route hints, ensuring that the payment route is well-defined. This invoice is then shared with the payer. | ||
|
||
When the payment is received with the SCID, the LSP Node takes over to execute a Just-In-Time(JIT) channel creation. A zero-confirmation channel is opened to the client, facilitating the payment transfer. The LSP Node seamlessly forwards the payment to the client while deducting | ||
ConorOkus marked this conversation as resolved.
Show resolved
Hide resolved
|
||
the applicable channel fees, ensuring both efficiency and reliability throughout the process | ||
|
||
# Immediate Benefits | ||
|
||
The implementation of LSPS2 brings significant advantages to liquidity management on the Lightning Network. Clients can now receive funds without the need for pre-established channels, which greatly reduces friction during the onboarding process. The dynamic nature of channel | ||
ConorOkus marked this conversation as resolved.
Show resolved
Hide resolved
|
||
creation eliminates the necessity for upfront investments in liquidity, making the solution both scalable and cost-effective. Furthermore, payment processing is optimized, with Just-In-Timechannels ensuring faster and more reliable transactions, enhancing the overall user experience. | ||
|
||
# Conclusion | ||
|
||
The LSP Liquidity Provider (LQwD), built on LDK Node and the Lightning Liquidity crate, showcases how LSPS2 can revolutionize liquidity management on the Lightning Network. By offering JIT channels, this solution simplifies onboarding, reduces costs, and aligns network resources with real-time needs, paving the way for a more accessible and scalable Lightning Network. | ||
ConorOkus marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
||
For more information or collaboration opportunities, visit the LQwD [website](https://lqwdtech.com/). |
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.