Skip to content

LUD-16: add optional default identifier shorthand #296

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.

Sign up for GitHub

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

Open
andrerfneves wants to merge 1 commit into
base: luds
Choose a base branch
from
Open

LUD-16: add optional default identifier shorthand #296

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions 16.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,6 +13,16 @@ Upon seeing such an address, `WALLET` makes a GET request to `https://<domain>/.

The response from `SERVICE` then MUST be the same as in [LUD-06](06.md), step 3, and the flow is the same.

### Default identifier

A `SERVICE` MAY offer a default internet identifier for a domain by using `_` as the `<username>`.

Upon seeing an address in the format `@<domainname>`, a `WALLET` MAY treat it as shorthand for `_@<domainname>` and make a GET request to the `https://<domain>/.well-known/lnurlp/_` endpoint if `domain` is clearnet or `http://<domain>/.well-known/lnurlp/_` if `domain` is onion. For example, if the address is `@bitcoin.org`, the request is to be made to `https://bitcoin.org/.well-known/lnurlp/_`.

This shorthand is optional. A `WALLET` that does not implement it MAY reject `@<domainname>` as an invalid internet identifier, and a `SERVICE` that does not offer a default identifier MAY return an error or 404 for `/.well-known/lnurlp/_`. Existing `<username>@<domainname>` identifiers MUST continue to resolve as specified above.

If a `SERVICE` returns metadata for a default identifier, it SHOULD use `_@<domainname>` as the canonical `text/identifier` value.

If providing such a scheme, `SERVICE` MUST add to the `metadata` JSON array either a `text/email` entry or a `text/identifier` entry, as in examples below:

```
Expand Down