We suggest the latest ways to pay with Bitcoin

On September 23, client Bitcoin Core collaborator Matt Corallo presented a technical proposal aimed at simplifying how Bitcoin (BTC) payments are made.

The approach published as a draft in the proposal name for improvements to Bitcoin 321 (BIP-321) must be discussed by the developer and Bitcoiner Before implementing it in the protocol.

According to the proposed repository, the purpose is to define a new scheme Bitcoin’s “uri” address (uniform resource identifier), i.e. the address of the link (uniform resource identifier), which includes payment procedures and can be opened in a web browser or QR code.

These links already exist in the current standard included in BIP-21, but new documentation promises updates It reflects «Latest Bitcoin Uses Prepare the terrain for future expansion».

Simply put, a URI is followed by a link beginning with «Bitcoin:» followed by an additional address or parameter describing the payment.

By clicking on that link or scanning, you can get a compatible wallet Interprets instructions and guides users to make payments.

It is true that applications such as Aqua already offer a more friendly payment experience with short addresses or payment links that simplify user interaction.

The difference is that you do it at the application level. Each wallet implements its own solution.

Matt Coraro raises that type of thing. Bitcoin Protocol level facilities. This means that a wallet or service that follows the standards can adopt the same payment method, without relying on a particular app.

In other words, it is not a replacement for something already present in Aqua or other wallets; Integrate and standardize these functions Be native to Bitcoin and not dependent on external development.

The most notable aspects of Bitcoin’s new proposal

According to the BIP-321 text, the most relevant changes are:

• Enhanced compatibility: Includes latest orientations such as BeCh32 and BeCh32M, as well as base inheritance base 58. Other payment methods are also planned to be integrated, such as Lightning and Silent Payments invoices.

• Additional parameters: The scheme allows you to add data as an exact amount of BTC, the recipient’s name, a descriptive message, or a unique transaction identifier.

• Payment Test (proof of payment, POP): Adds the possibility of receiving confirmation when the application that started payment is completed. For payment On-chainthe test is a complete transaction in hexadecimal format. In the case of lightning, payment is prepaid.

• Security Rules: Bitcoin customers must not make payments without user approval. Each instruction You need to review and check manuallyin some cases, it may be automated under user decisions.

• Integration with the Operating System: Graphic Fac should be recorded as the default application for handling “Bitcoin:” links. So when you open a link, the system calls the wallet directly.

Evolving Bitcoin Standard

The documents presented by Corallo ensure that previously valid BIP-21 comes from previous versions (BIP-20) and is outdated against new practices such as lightning bolt use and high privacy addresses.

In this sense, the new draft is trying to unify the criteria and generate a framework for future development.

The logic behind this scheme is that the payment link does not represent a person; Unique transfer instructions.

Bitcoin recommends not reuse your address. Therefore, each “URI” must be considered a temporary payment identifier, not a fixed identifier for the receiver.

Furthermore, the author of BIP-321 highlights that incorporating payment testing can be important in scenarios where there is no public registry for transactions such as Lightning. Unlike the main Bitcoin chain, there is no global accounting book to monitor.

Currently, discussion is open between Bitcoin developers and engineers. You should assess the relevance of the changes And how to integrate them into future versions of the protocol.