Definition: DNS Payment Instructions (BIP 353) is a standard for resolving a human-readable Bitcoin payment name, such as ₿alice@example.com, to a bitcoin: payment URI stored in a DNS TXT record. A compatible wallet validates DNSSEC before using the instructions. BIP 353 defines DNS-based name resolution; it is not a blockchain domain system and does not guarantee support in every wallet.1
| Date created | BIP 353 was assigned on February 10, 2024, and its document is marked Complete in the BIP repository. That document status does not mean the feature was activated by Bitcoin consensus rules.1 |
|---|---|
| Protocol specification | Read BIP 353 |
| Directories | Bitcoin Technology & Infrastructure · Bitcoin Directory |
How a payment name resolves
A BIP 353 name has a user part and a domain, displayed as user@domain. The specification recommends showing a Bitcoin symbol before it, as in ₿user@domain, to distinguish the name from an email address. The symbol is only a display marker and is not part of the DNS label. For alice@example.com, the specified record name is alice.user._bitcoin-payment.example.com. The DNS TXT record contains a bitcoin: URI that a wallet parses as payment instructions.1
The URI can contain an on-chain address or other payment instructions supported by the wallet. BIP 353 uses a BOLT 12 Offer in its example. BIP 353 defines name resolution and DNS record handling; BIP 321 describes the URI format and the payment-instruction fields it can carry. The two specifications are related, but they address different parts of the flow.1 3
DNSSEC and trust boundaries
BIP 353 payment records must be signed with DNSSEC. A wallet resolving a name must validate the signature chain to the DNS root itself, rather than relying only on a remote resolver’s assurance. If a label has multiple matching bitcoin: TXT records, the instructions are invalid under the specification.1
DNSSEC authenticates the origin and integrity of DNS data, but it does not provide confidentiality. A lookup may still be visible to a resolver or another party on the network path. RFC 4033 describes DNSSEC’s security goals and limits; BIP 353 also discusses options such as Tor or a VPN to reduce exposure. DNSSEC therefore does not make a payment anonymous or hide all network activity.1 2
A valid DNSSEC proof shows that the data matches the record published by the domain. It does not prove that the domain owner is the person a payer expects or that a payment request is safe. Check the recipient, amount, and details shown in the wallet before approving a payment. Domain takeover, expiration, misconfiguration, and look-alike names remain risks.
Addresses, expiration, and privacy
When a record contains a reusable on-chain address, BIP 353 recommends rotating the address regularly, using a short DNS time-to-live (TTL), and rotating it after an on-chain payment confirms. If an address cannot be rotated, the specification recommends omitting it from the URI. Wallets also must not cache payment instructions beyond the relevant DNS TTLs. These practices can reduce stale instructions and address reuse, but their effect depends on how domain operators and wallets implement them.1
BIP 353 is intended to extend and eventually replace the Lightning Address pattern, which uses HTTPS to map a similar name to a Lightning BOLT 11 invoice. Compatible wallets may try Lightning Address resolution if DNS lookup fails. The BIP warns that an HTTPS request can reveal the sender’s IP address, so the fallback should not be assumed to provide the same privacy properties as DNS resolution. The specification does not establish that all wallets support either method.1
What BIP 353 does not do
BIP 353 does not register names, hold balances, or settle payments. It uses the existing DNS hierarchy and a signed TXT record to locate payment instructions. The wallet still interprets the URI, and the user still reviews and authorizes the payment. A BIP 353 name is therefore different from a blockchain naming service, an email address, a payment processor, or proof that a particular person controls an address.1
History
- February 10, 2024: BIP 353, “DNS Payment Instructions,” was assigned as an application-layer specification. The BIP repository marks the document Complete; this is a document status, not an announcement of protocol activation.1
Last updated: November 12, 2026
Related Terms
Related Articles
- What Happens to Bitcoin When All 21 Million Are Mined?
- Why Calling It a “Wallet” May Have Been Crypto’s Biggest Mistake
- How the 2024 Bitcoin ETF Changed Crypto: Institutional Adoption, Inflows, and the Market Shift
- Bitcoin as Collateral: Bank Loans, Mortgages, and DeFi Explained
See Also
Sources
- Corallo, Matt, and Bastien Teinturier. “BIP 353: DNS Payment Instructions.” Bitcoin Improvement Proposals. Assigned February 10, 2024. Accessed November 12, 2026.
- Arends, R., R. Austein, M. Larson, D. Massey, and S. Rose. “RFC 4033: DNS Security Introduction and Requirements.” Internet Engineering Task Force, March 2005.
- Bitcoin Improvement Proposals. “BIP 321: URI Scheme.” Accessed November 12, 2026.