blixt-wallet icon indicating copy to clipboard operation
blixt-wallet copied to clipboard

Blixt will not scan BIP21 QR code with `lightning` invoice as first param

Open sbddesign opened this issue 3 years ago • 1 comments

It appears that Blixt will not successfully scan a BIP21 URI QR code when the lightning param is the first param -- only when it is the last param. My understanding of BIP21 is that the parameters do not need to be in a specific order. Phoenix, Muun, Breez, BlueWallet, and Wallet of Satoshi will all scan BIP21s with lightning as first or last param.

How to replicate

  1. Scan this QR code with Blixt: ln-last
  2. It will take you to the Pay Invoice screen
  3. Scan this QR code with Blixt: ln-first
  4. It will bring up an error message: "QR scan error: Code is not a valid Bitcoin Lightning invoice"
  5. Expected result: it should also take me to Pay Invoice screen

sbddesign avatar Jun 03 '22 22:06 sbddesign

Here's the raw URIs for the above QR codes.

lightning last (works)

bitcoin:bc1qylh3u67j673h6y6alv70m0pl2yz53tzhvxgg7u?amount=0.00001&label=sbddesign%3A%20For%20lunch%20Tuesday&message=For%20lunch%20Tuesday&lightning=lnbc10u1p3pj257pp5yztkwjcz5ftl5laxkav23zmzekaw37zk6kmv80pk4xaev5qhtz7qdpdwd3xger9wd5kwm36yprx7u3qd36kucmgyp282etnv3shjcqzpgxqyz5vqsp5usyc4lk9chsfp53kvcnvq456ganh60d89reykdngsmtj6yw3nhvq9qyyssqjcewm5cjwz4a6rfjx77c490yced6pemk0upkxhy89cmm7sct66k8gneanwykzgdrwrfje69h9u5u0w57rrcsysas7gadwmzxc8c6t0spjazup6

lightning first (does NOT work)

bitcoin:bc1qylh3u67j673h6y6alv70m0pl2yz53tzhvxgg7u?lightning=lnbc10u1p3pj257pp5yztkwjcz5ftl5laxkav23zmzekaw37zk6kmv80pk4xaev5qhtz7qdpdwd3xger9wd5kwm36yprx7u3qd36kucmgyp282etnv3shjcqzpgxqyz5vqsp5usyc4lk9chsfp53kvcnvq456ganh60d89reykdngsmtj6yw3nhvq9qyyssqjcewm5cjwz4a6rfjx77c490yced6pemk0upkxhy89cmm7sct66k8gneanwykzgdrwrfje69h9u5u0w57rrcsysas7gadwmzxc8c6t0spjazup6&amount=0.00001&label=sbddesign%3A%20For%20lunch%20Tuesday&message=For%20lunch%20Tuesday

sbddesign avatar Jun 03 '22 22:06 sbddesign

Thank you so much for the bug report @sbddesign. Bug fixed in b4ce664.

hsjoberg avatar Sep 19 '22 15:09 hsjoberg