I had issues with Sparrow Wallet when I was setting up my Blockstream Jade airgapped device. I mentioned it back then. My goal was to make Sparrow my go-to software wallet with my Jade but scanning the animated QR codes with my laptop was the worst experience ever. After several minutes of trying, I never managed to get the bar to 100%. I gave up and used Blue Wallet on mobile instead. It finally worked a bit later but again after many failed attempts.
I hope they finally fixed this. I initially thought it's the small screen of the Jade that is causing problems or perhaps a bad camera on my laptop. But I am not sure about that.
Out of curiousity, since I said I had the same problem, were you using multi-sig, single-sig or both? I am asking because the unsigned transactions from a multi-sig wallet are larger and, therefore, the QR code must be more dense and difficult to scan (?).
Multisig isn’t the only reason for larger QR data payloads. Transactions with many signed
by HW UTXOs also cause issues. In my experience, Sparrow struggles to read QR code from my Passport Core when multiple UTXOs are involved. Thus, I usually limit each transaction to spending just one UTXO. Besides, the lighting conditions also play meaningful role. Any reflections or glare on HW screen can interfere with QR code reading and cause the problem.
Are there options to opt out of the animated QR codes and to just use the static QR codes instead, and sure I can understand that there is added security with animated QR codes, but how much extra security is being added with animated versus static, and is such extra security necessary.
I have used the animated QR codes between the Passport and Sparrow, and it seems to take around 10 seconds on a faster scanning and more than 20 seconds on a slower scanning. The static QR codes, when they are an option,
** scan in a second or even less than a second.
** it seems that static QR codes are used for certain functions like merely validating an addresses without sending, and animated QR codes are used for other functions, such as initial set up and syncing of wallets, and the actual validating for sending of transactions.Perhaps if there were an option to choose between animated QR codes and static QR codes, then many folks would opt to use the static QR codes out of convenience, including myself... especially since I cannot understand how much added benefit is coming from animated QR code as compared with static QR code usage.
In theory it could be possible to use the static QR code for single, small transaction, provided the transaction size is small enough to fit within the QR code’s size limit
particularly when you disregard security concerns. However, most transactions exceed that limit, especially when QR using high levels of error correction
which is crucial for its reliability. Thus wallets have to chunk the relevant data in to smaller pieces and create the sequence of QR frames that represent animated QR. That said, there is
no such opt "to just use the static QR codes instead" on Sparrow or Passport Core.
P.S. I'm currently brainstorming the way to stabilize the Passport Core
while Sparrow reading QR codes to prevent potential issues caused by hand shaking. The idea is to create the clip or holder that will keep the device firmly in place in front of the camera ensuring reliable QR scanning without any wobble.
Multisig isn’t the only reason for larger QR data payloads. Transactions with many signed by HW UTXOs also cause issues. In my experience, Sparrow struggles to read QR code from my Passport Core when multiple UTXOs are involved. Thus, I usually limit each transaction to spending just one UTXO. Besides, the lighting conditions also play meaningful role. Any reflections or glare on HW screen can interfere with QR code reading and cause the problem.
Of course, any transaction which is larger in size, will create a denser QR code.
Larger in size transactions require more frames for animated QR.
