From daf64c4253fa920aa6086bba9a77ca81587b11f1 Mon Sep 17 00:00:00 2001 From: Jon Atack Date: Wed, 24 Sep 2025 10:45:24 -0600 Subject: [PATCH] BIP321: add reference implementation section --- bip-0321.mediawiki | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/bip-0321.mediawiki b/bip-0321.mediawiki index ea8810e2..025feddb 100644 --- a/bip-0321.mediawiki +++ b/bip-0321.mediawiki @@ -120,6 +120,12 @@ For payments completed on-chain, this is largely addressed by having the payment In order to avoid inadvertently revealing the sender's IP address or other information to the recipient, proof URIs must only be opened when they will simply switch to another locally-installed application (i.e. the application which initiated the payment). When clicking a URI from a website, the website should already have plenty of logic on its backend to process payment completion and a proof-of-payment callback is unnecessary. +== Reference Implementation == + +Documentation: https://docs.rs/bitcoin-payment-instructions + +Code repository: https://github.com/rust-bitcoin/bitcoin-payment-instructions + == Forward compatibility == Query parameter keys which are prefixed with a req- are considered required. If a client does not implement handling a query parameter which has a key prefixed with req-, it MUST consider the entire URI invalid. Any other query parameters which are not implemented, but which are not prefixed with a req-, can be safely ignored.