Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£861.54
EST. MONTHLY
205
DAYS
EST. ROI
This guide explains BIP 121 Proof of Payment URI scheme 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 121 proposed a btcpop URI for requesting the BIP 120 proof that a wallet controlled the credentials used in a prior payment. It adapted BIP 21-style query handling but required a proof destination and nonce, with an optional transaction identifier hint.
- Why it matters: BIP 121 defined a compact request wrapper for a proof protocol that closed without broad deployment. Any archival support should be isolated, consent-driven and explicit about destination, replay and privacy.
- Current position: Where the proposal is closed, isolate historical parsers and consensus code from production.
BIP 121 Proof of Payment URI scheme in simple English
BIP 121 Proof of Payment URI scheme: The scheme name was btcpop rather than bitcoin, and the normal address path remained empty. Query parameters carried all request data.
Simple example
A node operator is checking BIP 121 Proof of Payment URI scheme. Keeping proof requests distinct from payment links reduced accidental interpretation, but operating-system handlers and QR scanners still needed explicit scheme registration and confirmation.
Key terms in plain English
- BIP:
- Bitcoin Improvement Proposal: a document describing a proposed rule, standard or process. Its status must be checked separately.
- Consensus:
- The shared rules full nodes use to decide whether blocks and transactions are valid.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Scheme and empty path
The scheme name was btcpop rather than bitcoin, and the normal address path remained empty. Query parameters carried all request data. Keeping proof requests distinct from payment links reduced accidental interpretation, but operating-system handlers and QR scanners still needed explicit scheme registration and confirmation.
Mandatory destination
Parameter p identified where the completed proof should be sent, such as an HTTPS URL or mailto destination. It was an outbound data target supplied by the requester. Wallets had to show and restrict that destination so a scanned code could not silently transmit wallet-linked evidence to an unexpected service.
Nonce and replay resistance
Mandatory n carried a Base58-encoded nonce generated for the request. The proof bound this challenge so a captured response would not normally satisfy a later request. Randomness, one-time server storage, expiry and atomic consumption were application responsibilities; encoding alone did not prevent replay.
Optional transaction hint
The optional txid helped the wallet find the payment being proved. It was only a hint and had to match the transaction selected through request information. Transaction malleability and differing local history could make a remembered outgoing identifier unreliable, so wallet discovery could not trust the hint blindly.
Short-URI guidance
The BIP encouraged concise destinations and parameters because dense QR codes are harder to scan. URL shorteners introduce another redirect and ownership boundary. A compact code must not hide the final proof destination, nonce scope or service identity from the user’s trusted confirmation screen.
Transport and privacy
A proof can link wallet inputs and a prior payment to a new login or physical access event. HTTPS protects transport to an authenticated web endpoint but does not minimise server retention. Mail delivery leaks different metadata. Services need stated purpose, expiry, access control and deletion rules for proof records.
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 121 Proof of Payment URI scheme?
BIP 121 Proof of Payment URI scheme: The scheme name was btcpop rather than bitcoin, and the normal address path remained empty.
For BIP 121 Proof of Payment URI scheme, what should a beginner know about scheme and empty path?
The scheme name was btcpop rather than bitcoin, and the normal address path remained empty.
For BIP 121 Proof of Payment URI scheme, what should a beginner know about mandatory destination?
Parameter p identified where the completed proof should be sent, such as an HTTPS URL or mailto destination.
For BIP 121 Proof of Payment URI scheme, what should a beginner know about nonce and replay resistance?
Mandatory n carried a Base58-encoded nonce generated for the request. The proof bound this challenge so a captured response would not normally satisfy a later request.
Conclusion
BIP 121 defined a compact request wrapper for a proof protocol that closed without broad deployment. Any archival support should be isolated, consent-driven and explicit about destination, replay and privacy.
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.
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.