Why it exists
BIP 353 maps a human-readable payment name to Bitcoin payment instructions using DNS. DNSSEC signatures let a wallet verify the answer rather than trusting a resolver’s claim. This can make a recipient easier to find while still presenting the actual payment method for approval.
How it works
For an identifier such as alice@example.com, the instructions live in a TXT record at alice.user._bitcoin-payment.example.com. The record contains a bitcoin: URI. The wallet reconstructs it, validates the DNSSEC chain and any aliases, then parses the supported payment instructions.
The wallet must perform DNSSEC validation itself rather than accepting a remote resolver’s assurance. Records have bounded lifetimes, and ambiguous multiple payment records are rejected. Direct addresses or explicit payment URIs should be preferred when they already provide the needed destination.
A practical example
An illustrative café identifier could resolve to a URI containing a Lightning offer or Silent Payments instruction. A wallet that supports the relevant method shows the resolved request and asks the customer to approve. The domain is an example, not a real payment destination.
What to keep in mind
DNSSEC authenticates control within the DNS hierarchy; it does not prove that the domain belongs to the person you intended. Domain compromise, confusing names and stale records remain important. A static on-chain address in a record can create address-reuse privacy problems.
Status & implementation
BIP 353 is Complete. Its official reference section links DNSSEC proof-generation and validation code, while BIP 321 defines modern URI contents. Both the recipient’s DNS setup and the sender’s wallet must support the scheme.
Specification status: Complete · Sources checked 13 November 2026
