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

Draft
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

WIP

.. to make it easier to switch back-and-forth when testing.
@tnull tnull marked this pull request as draft July 9, 2024 11:28
@tnull tnull force-pushed the 2024-07-update-lsps1 branch 2 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
We previously didn't advertise the supported protocols, even if the
corresponding service handlers were available.
@tnull tnull force-pushed the 2024-07-update-lsps1 branch 3 times, most recently from 75cfa55 to ed65742 Compare August 13, 2024 12:23
.. 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.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

LSPS1: Disallow compiler warnings once implementation is finished
1 participant