-
Notifications
You must be signed in to change notification settings - Fork 30
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
Create LSP ML post and bLIP #30
Comments
LSPS0 merged, anyone willing to do this? |
are we in a huge rush? i'd say seeing some of this adopted in production would be a good milestone, LSPS1 was finalized once before:) |
@niftynei wrote on the Lightning-dev mailing list: https://lists.linuxfoundation.org/pipermail/lightning-dev/2023-April/003915.html , I think it is appropriate to bring this up to a larger discussion group rather than present it as a fiat accompli. True, this project is on a public github repo, but is it public enough? |
I think it might be a good idea to write a "Call for review" for LSPS1 & LSPS2 on the mailing list. These specs, even though not 100% finished yet, are pretty mature and it would be a good idea to ask for more reviews. What do you guys think? |
Anyone willing to volunteer for this? |
So do we close this now? |
I don't think so? When we land a bit more we still should write-up a bLIP to have the LSPS type registered. |
Should we start a bLIP now? |
IIRC, last time this was discussed in the call the conclusion was that we'd wait until we have first interop between two clients, and that I should then draft a bLIP. Happy to revisit that though if we think this should happen sooner rather than later? |
Since we now had the first interop on mainnet I think it might be time to pick this up. Will see to write a bLIP draft soon. |
Once we all agree on the general protocol structure and standardization process (e.g., after merging LSPS0), we should write-up a concise description and post to the mailing list to update the wider Lightning community on the progress. Moreover, we should then open a bLIP PR to have the message type and feature bit registered.
The text was updated successfully, but these errors were encountered: