URI Scheme

The five-minute read

One action, walked through

1. Open BIP 321 and read the status line before the examples.
2. Write down the rule in one sentence. A fair version of that sentence is: A URI scheme for describing Bitcoin payment instructions.
3. Name the object that changes: URI.
4. Ask what an old client, an old contract, or an offline counterparty does. If the document is silent, the silence is part of the design.

The argument, unpacked

What has to be true

• You are implementing BIP 321 at the status the text itself states: Complete.
• The object that has to change is URI. A neighbouring document with a similar name is not this one.
• Status in the header is not adoption.

What happened after the paper

The source marks this complete. That is a statement about the text, not a promise that every wallet or node has shipped it. Later documents can narrow, replace, or ignore this one. Cite the number you mean.

What to check before you use the idea

• What must an implementation of URI Scheme accept, and what may it ignore?
• Is this consensus, peer policy, or an application interface?
• Which names does the text pin down: URI?

Terms

BIP 321

The public text titled URI Scheme.

Complete

The document's own label for how finished the text is. It is not a market fact.

The problem the paper names

An interface that is only a name in a repository will be re-implemented differently by every team, which is how shared contracts break.

What the design proposes

• A URI scheme for describing Bitcoin payment instructions.
• The purpose of this URI scheme is to enable users to easily make payments by simply clicking links on webpages or scanning QR Codes.
• This BIP is a modification and intended replacement of [[bip-0021.mediawiki|BIP 0021]] to add information about the modern usage of bitcoin: URIs (including standard query parameters and modern address types) as well as provide forward-looking guidance on how to incorporate new payment instructions.

How the mechanism is specified

• Taken from the specification, the next constraint is: The purpose of this URI scheme is to enable users to easily make payments by simply clicking links on webpages or scanning QR Codes.
• Locate URI in BIP 321 and apply it to one transaction or call.
• Then check the failure the class of rule always has: a node that did not upgrade, a reverted call, a replayed signature, or a peer that does not speak the message.

What this page does not treat as proven

• This document does not set a fee, a valuation, or a security proof.
• Status in the header is not adoption.
• The source marks this complete. That is a statement about the text, not a promise that every wallet or node has shipped it.

Why a venture studio still reads it

Use BIP 321 when a pitch says 'URI Scheme' without saying whether the rule is consensus, policy, or an interface. The number is the citation. The pitch is not.