Lightning Address

Overview

A Lightning Address is a human-readable identifier, usually formatted like an email address, that lets a compatible Bitcoin Lightning wallet request payment details from a recipient’s server. The wallet resolves the domain’s LNURL-pay endpoint, requests an amount-specific invoice, and then pays that invoice over the Lightning Network. It is not a reusable Lightning invoice, an email account, or a blockchain address, and the recipient domain remains an important trust and availability dependency. Important risks include domain takeover, unavailable LNURL services, invoice substitution, privacy leakage, amount-limit mismatch, routing failure, and users trusting lookalike names.

Applications should verify the exact identifier, HTTPS endpoint, callback response, amount limits, returned invoice, payment hash, settlement result, and recipient confirmation. A complete record for Lightning Address should show where it depends on Lightning Invoice and how it differs from Lightning Service Provider (LSP). That distinction lets teams reconcile Lightning Address without treating a related interface or event as final financial evidence.

For Lightning Address, address lifecycle controls should include generation limits, key or custodian security, monitoring health, rotation or revocation, late-arriving deposits, unsupported-token handling, and reconciliation between blockchain receipts and internal balances. When Lightning Address interacts with Lightning Invoice, reusable addresses need stronger privacy and attribution controls than single-use addresses because several payments can reach the same destination over time.

For Lightning Address, an address-based payment workflow must bind the destination to an exact network, asset representation, account or invoice, custody source, and active period. When Lightning Address interacts with Lightning Invoice, the same visible address can exist on different networks, while token contracts on one network can represent unrelated assets. In the relationship between Lightning Address and Lightning Service Provider (LSP), systems should therefore validate chain and contract identity, monitor the correct ledger, and reject unsupported transfers rather than crediting by symbol alone.