LUD-16: add optional default identifier shorthand#296
Open
andrerfneves wants to merge 1 commit into
Open
Conversation
This file contains hidden or 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
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.
Motivation
Lightning Address works well for hosted services, but personal domains often end up using placeholder local parts like
me@domain,pay@domain, orln@domaineven when the domain itself is the intended identifier. This came up in andrerfneves/lightning-address#28.Proposal
This extends LUD-16 with an entirely optional default identifier convention:
_@domainas the canonical default identifier@domainas shorthand for_@domain/.well-known/lnurlp/_This avoids introducing a new endpoint shape and keeps metadata aligned with the existing LUD-16
user@site.comidentifier format.Testing
Docs-only spec change; no tests run.