Run · Payments
mainnet
mainnet
BIP-353 pay codes
DNSSEC-signed payment instructions carrying sp= and lno=.
Connect
piers.user._bitcoin-payment.pay.mineracks.comWhat it is
BIP-353 puts payment instructions in DNS: a name like user@domain resolves, through a DNSSEC-signed TXT record, to a BIP-21 URI that can carry an on-chain address, a silent-payment address, a BOLT12 offer or all three. Unlike a Lightning address there is no web server in the loop, and the DNSSEC chain lets the wallet prove the answer was not tampered with.
Wallets that support it (Bitcoin Core 30, Phoenix, Zeus, Cake and others) let you type the name and pay. Ours are published on our own DNS with DNSSEC on.
What people use it for
- A single human-readable name that works for on-chain and Lightning payments.
- Reusable payment instructions that survive wallet migrations, because the name points to the record you control.
- Testing a wallet's BIP-353 resolution against a record that is known to be valid.
How we run it
Resolve the TXT record over DoH with the AD bit set; wallets that speak BIP-353 do this for you.
Learn more
- BIP-353: DNS payment instructions github.com
- BIP-21: URI scheme github.com
- BOLT12 offers bolt12.org
- Bitcoin Optech on BIP-353 bitcoinops.org