-
Notifications
You must be signed in to change notification settings - Fork 45
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
sdk-common: Expose if BIP353 is used for parsing #1164
base: main
Are you sure you want to change the base?
Conversation
Looks good to me, I just prefer to review this once again together with the PR for breez/breez-sdk-liquid#714. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Concept ACK. Need flutter/bindings updating
Done. Updated CC: @danielgranhao |
e53f76a
to
aac8d2f
Compare
3222a5a
to
ec87da4
Compare
|
ec87da4
to
f6951d1
Compare
Adjusted the PR according to the feedback from breez/breez-sdk-liquid#718 (comment) |
f6951d1
to
43a2000
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
One NIT comment regarding documentation.
This adds a bip353_address field to Bolt12 and LnUrlPay input types to allow users of
parse()
to tell if a particular input was a BIP353 address.This is needed in the nodeless SDK for breez/breez-sdk-liquid#714.