Replies: 2 comments
-
great feedback. we should indeed select the lightning invoice. a more complex logic would be to suggest a payment on chain if the lightning payment were to fail. |
Beta Was this translation helpful? Give feedback.
-
Agree with the OP, the default should be the LNpayment, but the best would be the choice between paying on LN and onchain if both are offered (LN still as default). BTCPay v1.7.0 introduced BIP21 payment codes eg on signet from: https://signet.demo.btcpayserver.org/apps/2SCdQhwFm464BcHxXn44kRVg3iCr/pos
Also the new Zeus v0.7.0 release candidate offers to show BIP21/unifiedQRcode links: https://github.com/ZeusLN/zeus/releases A good table of wallet compatibility here https://bitcoinqr.dev/ from @agbegin. Jan 2023 update: Muun Wallet adds Unified QR codes - not by default, can chosse to use in Settings - Advanced settings - Lightning Network - Receiving protocol |
Beta Was this translation helpful? Give feedback.
-
Background
An issue more broadly in the Bitcoin ecosystem is situations where the user must choose whether to generate an on-chain Bitcoin address or a lightning invoice. Bitcoin Beach wallet falls into this category since it supports both on-chain and lightning.
While Bitcoin Beach will scan a QR code of a BIP 21 payment URI, it will only recognize the on-chain address and not a
lightning
parameter containing a BOLT 11 invoice. I would love it if Bitcoin Beach wallet could support scanning a BIP-21 QR with alightning
param.Steps to Replicate
To
field with the on-chain address.To
field with the BOLT 11 invoice from thelightning
param in the QR code (or, it could prompt the user to choose which to use, but I think it would be easier on the user if it defaulted to lightning).See this website for more background information.
Screenshots
Beta Was this translation helpful? Give feedback.
All reactions