Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£861.31
EST. MONTHLY
205
DAYS
EST. ROI
This guide explains BIP 79 Bustapay protocol 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 79 described Bustapay, an optional sender-receiver coinjoin payment protocol intended to weaken common-input and change heuristics while helping a merchant manage UTXOs. The BIP is Informational and Closed, not a current network rule.
- Why it matters: Bustapay is a thoughtful historical privacy protocol, but it remains closed and operationally intricate. Its lasting lesson is that collaborative payment mutation demands exact validation and a safe unilateral fallback.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
BIP 79 Bustapay protocol in simple English
BIP 79 Bustapay protocol: Closed means the proposal did not become an active standard. Treat this as historical protocol analysis, not a recommendation that modern wallets or merchants support it.
Simple example
A node operator is checking BIP 79 Bustapay protocol. The receiver can later broadcast this fallback if collaboration stalls. Blindly signing every wallet-owned input could let a malicious receiver trick the sender into authorising contributed inputs.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- UTXO:
- An unspent transaction output: a piece of bitcoin that can be used as an input to a later transaction.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Status and scope
Closed means the proposal did not become an active standard. Treat this as historical protocol analysis, not a recommendation that modern wallets or merchants support it.
Template payment
The sender first makes a fully signed, relay-eligible transaction using SegWit inputs but does not broadcast it. The receiver can later broadcast this fallback if collaboration stalls.
Exchange flow
A BIP 21 bpu parameter identifies an HTTPS endpoint. The receiver validates the template, adds at least one signed input, may increase its own output and returns a partial transaction.
Sender validation
The sender must retain every original input with sequence unchanged, find at least one new signed SegWit input and retain every original output without any amount decreasing.
Signing boundary
The sender signs only inputs present in the original template. Blindly signing every wallet-owned input could let a malicious receiver trick the sender into authorising contributed inputs.
Privacy and denial of service
Stable contributed-input selection is needed to resist UTXO enumeration. A valid fallback makes abandoned attempts costly, yet endpoint, timing and reuse can still leak relationships.
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 the main point of BIP 79 Bustapay protocol?
BIP 79 Bustapay protocol: Closed means the proposal did not become an active standard. Treat this as historical protocol analysis, not a recommendation that modern wallets or merchants support it.
For BIP 79 Bustapay protocol, what should a beginner know about status and scope?
Closed means the proposal did not become an active standard. Treat this as historical protocol analysis, not a recommendation that modern wallets or merchants support it.
For BIP 79 Bustapay protocol, what should a beginner know about template payment?
The sender first makes a fully signed, relay-eligible transaction using SegWit inputs but does not broadcast it.
For BIP 79 Bustapay protocol, what should a beginner know about exchange flow?
A BIP 21 bpu parameter identifies an HTTPS endpoint. The receiver validates the template, adds at least one signed input, may increase its own output and returns a partial transaction.
Conclusion
Bustapay is a thoughtful historical privacy protocol, but it remains closed and operationally intricate. Its lasting lesson is that collaborative payment mutation demands exact validation and a safe unilateral fallback.
Primary sources
- BIP 79 Bustapay primary specification
- BIP 21 URI Scheme
- BIP 125 Opt-in Full Replace-by-Fee Signalling
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.