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

Human Readable Names Support #1447

Open
TheBlueMatt opened this issue May 18, 2024 · 0 comments
Open

Human Readable Names Support #1447

TheBlueMatt opened this issue May 18, 2024 · 0 comments
Labels
new feature New feature or request

Comments

@TheBlueMatt
Copy link

bitcoin/bips#1551 describes a mechanism for mapping human-readable names (in the Buser@domain form) to BIP 21 URIs (targeting mostly silent payment addresses and BOLT12 offers). It would be nice if BDK came with support built-in for doing the lookups (or at least verifying DNSSEC proofs using https://git.bitcoin.ninja/index.cgi?p=dnssec-prover) and mapping them to a BIP 21 URI (and then resolving that to payment instructions).

We should probably have a discussion about where this kind of general payment instruction lookup logic should live - maybe LDK should refactor its BOLT12 offer and BOLT11 invoice parsing code into crates that don't depend on lightning so that we can have some generic "bitcoin payment instruction resolver" crate that BDK and LDK can use to resolve human readable names/BIP 21 URIs/bitcoin addresses to a list of payment instructions.

@TheBlueMatt TheBlueMatt added the new feature New feature or request label May 18, 2024
@notmandatory notmandatory added this to BDK May 18, 2024
@notmandatory notmandatory moved this to Discussion in BDK May 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
new feature New feature or request
Projects
Status: Discussion
Development

No branches or pull requests

1 participant