Sealminer A4 Ultra Hydro
Bitcoin & Bitcoin Cash ASIC Miner
886TH
HASHRATE
9.45W/TH
EFFICIENCY
8373W
POWER
£856.08
EST. MONTHLY
NO PAYBACK
EST. ROI
This guide explains BIP 321 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 321 is a Complete specification replacing BIP 21 with modern guidance for Bitcoin payment links and QR codes. A bitcoin URI may contain an on-chain address plus query parameters for amount, label, message, proof of payment and alternative payment instructions such as Lightning, BOLT12, private payments or silent payments.
- Why it matters: BIP 321 modernises Bitcoin payment links without making links trustworthy. Wallet safety comes from strict parsing, exact amounts, required-key handling, visible method selection and explicit approval before any transfer.
- Current position: BIP 321 is a Complete specification replacing BIP 21 with modern guidance for Bitcoin payment links and QR codes.
BIP 321 URI Scheme in simple English
BIP 321 URI Scheme: The bitcoin scheme is case-insensitive. The path may be a base58, bech32 or bech32m address or empty when a query parameter supplies a payment instruction.
Simple example
A node operator is checking BIP 321 URI Scheme. A wallet should show which method it selected and preserve an on-chain fallback only when provided.
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.
Status and replacement
BIP 321 is Complete, Specification, at the Applications layer and replaces BIP 21. It standardises payment instructions rather than recipient identity.
General form
The bitcoin scheme is case-insensitive. The path may be a base58, bech32 or bech32m address or empty when a query parameter supplies a payment instruction.
Encoding
Query data outside the permitted character set is encoded as UTF-8 bytes and then percent-encoded. Decode exactly once and reject malformed escape sequences.
Parameters
label, message and pop cannot be duplicated. Unknown ordinary keys must be tolerated, while an unsupported req- key makes the URI unusable.
Payment methods
Defined instruction keys include lightning, lno, pay and sp. A wallet should show which method it selected and preserve an on-chain fallback only when provided.
Amount
The amount is decimal BTC using a period and no commas. Parse as exact decimal or satoshis, enforce range and never use binary floating-point for transfer value.
Authorization and proof
Every payment requires user authorization. Pop or req-pop supplies a callback URI for proof after completion; treat it as untrusted external navigation and disclose privacy effects. Build a revision-pinned evidence pack on an isolated node, wallet or protocol harness. Record source commit, binary hash, network, chain identity, configuration and dependencies.
Frequently asked questions
What is the main point of BIP 321 URI Scheme?
BIP 321 URI Scheme: The bitcoin scheme is case-insensitive. The path may be a base58, bech32 or bech32m address or empty when a query parameter supplies a payment instruction.
For BIP 321 URI Scheme, what should a beginner know about status and replacement?
BIP 321 is Complete, Specification, at the Applications layer and replaces BIP 21.
For BIP 321 URI Scheme, what should a beginner know about general form?
The bitcoin scheme is case-insensitive. The path may be a base58, bech32 or bech32m address or empty when a query parameter supplies a payment instruction.
For BIP 321 URI Scheme, what should a beginner know about encoding?
Query data outside the permitted character set is encoded as UTF-8 bytes and then percent-encoded.
Conclusion
BIP 321 modernises Bitcoin payment links without making links trustworthy. Wallet safety comes from strict parsing, exact amounts, required-key handling, visible method selection and explicit approval before any transfer.
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.