mirror of
https://github.com/aljazceru/lightning-address.git
synced 2025-12-17 05:14:22 +01:00
Merge branch 'master' of github.com:andrerfneves/lightning-address
This commit is contained in:
@@ -37,7 +37,7 @@ Considering you own the `domain.com` domain, you need to set up these DNS record
|
||||
|
||||
* TXT `_kind`.domain.com -> lnd
|
||||
* TXT `_host`.domain.com -> http(s)://`your-ip-or-whatever.com`
|
||||
* TXT `_macaroon`.domain.com -> `macaroon_as_base64`
|
||||
* TXT `_macaroon`.domain.com -> `macaroon_as_base64` (use an invoice macaroon, this is publicly visible!)
|
||||
|
||||
### Optional extras:
|
||||
|
||||
|
||||
3
DIY.md
3
DIY.md
@@ -17,6 +17,8 @@ Sending to a Lightning Address is essentially just doing some string transformat
|
||||
|
||||
After receiving the LNURL Pay payload, the rest of the flow is the exact same as the LNURL Pay flow, there's virtually no difference. Again, Lightning Addresses are essentially another way of sharing how a user can obtain another user's LNURL Pay details.
|
||||
|
||||
Requirement: HTTPS is expected to be used, since this is sensitive data, where MITM impacts actual money.
|
||||
|
||||
### Receiving
|
||||
|
||||
In order to support receiving to a Lightning Address on your own infrastructure/domain setup, you will need a handful of things outlined below.
|
||||
@@ -25,6 +27,7 @@ In order to support receiving to a Lightning Address on your own infrastructure/
|
||||
* [LNURL Pay support](https://github.com/fiatjaf/lnurl-rfc/blob/master/lnurl-pay.md)
|
||||
* [Internet Identifier metadata support](https://github.com/fiatjaf/lnurl-rfc/blob/luds/16.md)
|
||||
* [Commenting support](https://github.com/fiatjaf/lnurl-rfc/blob/luds/12.md) (Optional)
|
||||
* HTTPS security
|
||||
* Lightning Network node
|
||||
* Used to create BOLT11 invoices for LNURL Pay flow
|
||||
* Domain
|
||||
|
||||
Reference in New Issue
Block a user