We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
It would be good to add some UI mockups for user flows involving BIP21 QRs. Things like:
The text was updated successfully, but these errors were encountered:
Would Pay-to-endpoint ?pj= flow be welcome?
?pj=
Sorry, something went wrong.
What sorts of data would need to going to a payjoin param?
Here is a test with some valid payjoin bip21s: https://github.com/DanGould/rust-payjoin/blob/ecce332ab1ddb23f50d4cecfe7b583e94dca6e19/bip78/src/uri.rs#L224-L241
One example would be BITCOIN:TB1Q6D3A2W975YNY0ASUVD9A67NER4NKS58FF0Q8G4?amount=1&pj=https://example.com
BITCOIN:TB1Q6D3A2W975YNY0ASUVD9A67NER4NKS58FF0Q8G4?amount=1&pj=https://example.com
the pj param contains a valid secure endpoint, either https or .onion
pj
https
.onion
No branches or pull requests
It would be good to add some UI mockups for user flows involving BIP21 QRs. Things like:
The text was updated successfully, but these errors were encountered: