Skip to content
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

LSPS1: Update message format and get client working #140

Open
wants to merge 11 commits into
base: main
Choose a base branch
from

Conversation

tnull
Copy link
Collaborator

@tnull tnull commented Jul 9, 2024

Closes #87
Closes #144
Closes #146

We refactor LSPS1-related client code and remove the cfg gate for these parts. Should be good for review, we can always iterate to improve the API etc. over time.

@tnull tnull marked this pull request as draft July 9, 2024 11:28
@tnull tnull force-pushed the 2024-07-update-lsps1 branch 3 times, most recently from af8a822 to e8a06f8 Compare July 11, 2024 10:07
@tnull tnull changed the title LSPS1: Update and get it working LSPS1: Update message format and get client working Aug 8, 2024
@tnull tnull force-pushed the 2024-07-update-lsps1 branch 5 times, most recently from ed65742 to b014a08 Compare August 14, 2024 10:36
.. to make it easier to switch back-and-forth when testing.
We previously didn't advertise the supported protocols, even if the
corresponding service handlers were available.
.. we tremendously simplify the client logic, also dropping any state
tracking for now (possibly to be re-added in the future).

We also get the LSPS1 API closer to LSPS2 and make sure the API/docs is
more consistent.
.. as we have no real way to check the network at the point of
deserialzation, and we want to handle `bitcoin::Addresses`, not uncheck
addresses, in particular when it comes to serialization.
We allow de/serializing if the field is absent and mirror it back in
`CreateOrderResponse`, as per recent spec change.
.. as per spec.
@tnull tnull marked this pull request as ready for review November 28, 2024 13:38
@tnull
Copy link
Collaborator Author

tnull commented Nov 28, 2024

CI failure on the beta channel is unrelated: lightningdevkit/rust-lightning#3424

@tnull tnull requested a review from G8XSU November 28, 2024 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant