Add bLIP 51: Channel Requests (LSPS1) #53
Conversation
This file contains 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
tnull
force-pushed
the
2024-12-add-lsps1
branch
from
b803f57 to
75ebac1
Compare
t-bast
reviewed
Dec 12, 2024
tnull
force-pushed
the
2024-12-add-lsps1
branch
from
75ebac1 to
f62b7f7
Compare
Done! |
The goal of LSPS1 is to provide a standardized LSP API based on LSPS0 that allows clients to purchase a channel from an LSP directly. The given protocol has been previously stabilized by the LSP Spec group and is live in production with several LSP and client implementations today. As previously discussed on multiple occasions, the LSP Spec group is however moving to a bLIP-centric process, which is why we 'upstream' these previously-stabilized specifications here.
tnull
force-pushed
the
2024-12-add-lsps1
branch
from
f62b7f7 to
db51380
Compare
|
Rebased after #55 landed (and squashed one fixup). |
t-bast
approved these changes
Dec 13, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Based on #52
The goal of LSPS1 is to provide a standardized LSP API based on LSPS0 that allows clients to purchase a channel from an LSP directly.
The given protocol has been previously stabilized by the LSP Spec group and is live in production with several LSP and client implementations today.
As previously discussed on multiple occasions, the LSP Spec group is however moving to a bLIP-centric process, which is why we 'upstream' these previously-stabilized specifications here.
(cc the original author @SeverinAlexB)