Solo Mining Calculator: Estimate Odds and Timeframes
Use a solo mining calculator correctly: enter productive hashrate, network conditions, uptime and time horizon, then read expected time and probability without.
Read article
ASIC mining knowledge centre
BIP 15 Bitcoin Aliases Explained: Why the Proposal Closed
BIP 15 Bitcoin aliases explained as a closed proposal for human-readable payment identities, including discovery, authentication and substitution risks.
This guide explains BIP 15 Bitcoin aliases in plain English. It covers the problem behind the BIP, why it matters and whether the proposal is part of Bitcoin today.
TL;DR
- What it is: BIP 15 Bitcoin aliases proposed resolving human-readable identities into payment destinations so users would not need to exchange long addresses directly. The document explored discovery and certificate-backed verification, but it is closed and not a current Bitcoin payment standard.
- Why it matters: BIP 15 anticipated the demand for readable Bitcoin payment identities, but it did not become a deployed standard. Any modern alias system must be evaluated as a separate authenticated resolver with explicit privacy, expiry, substitution and fallback controls.
- Current position: The document explored discovery and certificate-backed verification, but it is closed and not a current Bitcoin payment standard.
What this means in simple English
A BIP is a document that proposes or explains a Bitcoin idea, standard or rule. A BIP number does not mean the idea is active. Some BIPs are widely used, while others are drafts or historical proposals.
You do not need to read code to understand the main point. Start with the status, the problem being addressed and the practical effect on ordinary users, wallets, miners or node operators.
Simple example
Think of the transaction as a form passed between several authorised signers. Each person or device checks the same payment details before adding approval. Passing the form around does not make the payment safe unless every signer checks what it contains.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
The usability goal
Readable identities can reduce copying errors and let a merchant update destination infrastructure without changing printed material. The resolver becomes a new trusted layer, however. A perfectly valid Bitcoin transaction can still pay an attacker if name resolution was compromised. Usability improves only when the identity-to-address binding is authenticated and visible to the payer.
Proposed discovery path
BIP 15 considered using established internet naming and service discovery to locate payment information associated with an alias. Each DNS lookup, redirect and endpoint adds availability and substitution assumptions. Operators must distinguish authenticated records from transport that merely returned data, and they need a safe failure mode when discovery is unavailable or contradictory.
Certificates and identity claims
Certificate-backed responses can bind a domain or service endpoint under a public-key infrastructure, but the certificate proves control under that system, not the commercial truth of every payment request. Users still need a recognisable identity and amount confirmation. Expiry, revocation, compromised authorities and changed ownership must be part of the threat model.
Address rotation and privacy
A resolver can issue a fresh address per request, improving on public static reuse. It can also learn who requested payment details, at what time and from which network location. Logs link aliases to transaction activity. A privacy claim should state what the resolver, network observer, merchant and blockchain analyst can each see.
Retention periods, analytics tags and third-party DNS infrastructure belong in that assessment rather than being treated as unrelated web operations.
Why closed status matters
BIP 15 did not become the deployed universal alias layer. Wallets should not interpret an arbitrary name according to this proposal or present it as native Bitcoin functionality. Modern naming and payment protocols have their own specifications and trust models. Historical compatibility should be isolated and clearly labelled rather than silently guessed.
Modern comparisons
BIP 21 standardises payment URIs but does not turn a human name into an authenticated destination. Lightning offers use-case-specific invoice and offer mechanisms, while external naming systems can map identities under separate rules. Operators should compare authentication, privacy, revocation, replay and fallback instead of assuming every readable payment identifier provides equivalent assurance.
How specialists test it
Developers test the proposal with made-up data on an isolated test network. They check normal cases and deliberately invalid cases. Different implementations should reach the same result before anyone relies on the proposal.
Frequently asked questions
What is BIP 15 Bitcoin Aliases?
BIP 15 Bitcoin aliases proposed resolving human-readable identities into payment destinations so users would not need to exchange long addresses directly. The document explored discovery and certificate-backed verification, but it is closed and not a current Bitcoin payment standard.
Is BIP 15 active or supported today?
The document explored discovery and certificate-backed verification, but it is closed and not a current Bitcoin payment standard.
Why does BIP 15 matter?
BIP 15 anticipated the demand for readable Bitcoin payment identities, but it did not become a deployed standard. Any modern alias system must be evaluated as a separate authenticated resolver with explicit privacy, expiry, substitution and fallback controls.
Do beginners need to use the technical details?
No. Most readers only need to understand the idea and its current status. Developers and node operators can use the primary sources when they need the exact technical rules.
Conclusion
BIP 15 anticipated the demand for readable Bitcoin payment identities, but it did not become a deployed standard. Any modern alias system must be evaluated as a separate authenticated resolver with explicit privacy, expiry, substitution and fallback controls.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
On this page
Search More Guides
BIP-110 Explained: Rules, Signalling and Why It Closed
BIP-110 Explained made simple. See the main facts, costs, risks and practical checks before you make a decision.
Read article
Bitcoin Core 29.4 Release: Chainstate Disk I/O Guide
Bitcoin Core 29.4 guide covering repeated chainstate rewrites, regular compaction, LevelDB seek compaction, transaction-data lifetime and wallet sizing fixes.
Read article
Need Advice for Your Mining Setup?
Use our guidance to build your shortlist, then speak to our team when you want help comparing hardware, power, hosting or repairs.