-
Notifications
You must be signed in to change notification settings - Fork 17
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
tnull
wants to merge
11
commits into
lightningdevkit:main
Choose a base branch
from
tnull:2024-07-update-lsps1
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
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-07-update-lsps1
branch
3 times, most recently
from
July 11, 2024 10:07
af8a822
to
e8a06f8
Compare
tnull
changed the title
LSPS1: Update and get it working
LSPS1: Update message format and get client working
Aug 8, 2024
tnull
force-pushed
the
2024-07-update-lsps1
branch
from
August 8, 2024 11:45
0e647a5
to
5210925
Compare
tnull
force-pushed
the
2024-07-update-lsps1
branch
5 times, most recently
from
August 14, 2024 10:36
ed65742
to
b014a08
Compare
.. 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.
.. as of LSPS#101.
.. 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.
tnull
force-pushed
the
2024-07-update-lsps1
branch
from
November 28, 2024 13:03
ca3c923
to
87e37fd
Compare
We allow de/serializing if the field is absent and mirror it back in `CreateOrderResponse`, as per recent spec change.
.. as per spec.
tnull
force-pushed
the
2024-07-update-lsps1
branch
from
November 28, 2024 13:09
87e37fd
to
177ff80
Compare
CI failure on the |
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.
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.