Sparrow Bitcoin Wallet

[apogio]

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. And yes, the reflections is the worst thing.

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.

I think it's impossible to avoid animated QR codes, because when there is a big transaction the data won't fit in a single image. Please note that my answer is somewhat arbitrary, because I am definitely not sure about it.

[satscraper]

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.

[Pmalek]

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 (?).

No multisig. I was trying to set up a standard single-sig wallet and use my Jade as a stateless signer. As I mentioned, it worked eventually but it's not an experience I want to repeat. I can't even imagine how much more difficult it would be to scan a QR code from a multisig wallet due to its density when my singlesig configuration was already a nightmare.

[cygan]

version 2.2.3 was released today with some small improvements and bugfixes
you can find out exactly what these are in the following github link: https://github.com/sparrowwallet/sparrow/releases/tag/2.2.3
and you can also download the new version for your os there as well as on the official website: https://sparrowwallet.com/download/

[satscraper]

I'm really impressed with the recent improvements ^{from the latest updates} in Sparrow's ability to read QR codes. Animated QRs related to signed transactions on Passport Core now are scaned reliably within 10–15 seconds. Because of this improvement, I've put my idea of creating the custom clip or holder for the Passport on hold ^{as for now, my hand is good enough for this task}.

[btc-freedom-money]

What's the difference between a wallet and an account?
Can a seed phrase create multiple master private keys? Is that what accounts are? Are they master keys? So it would be same thing as creating a sparrow wallet on a different computer?
And a wallet is an xpub?
When you go to send tab, you can send from addresses that are in that xpub aka wallet? Or can you combine from multiple xpubs aka wallets in the send tab?

[Pmalek]

What's the difference between a wallet and an account?

An account is what you get on custodial services like centralized exchanges. Binance, for example. They hold all the keys and control the money. You own only the account. If you want to withdraw from that account, they will decide if that is ok or not. A wallet can be custodial or non-custodial. If it's non-custodial then you hold your own keys and can decide what to do with your bitcoin.

Can a seed phrase create multiple master private keys?

Your seed can derive one master private key. That master private key can then derive child private keys and eventually all your addresses.

So it would be same thing as creating a sparrow wallet on a different computer?

If you generated a new wallet using Sparrow on a different computer, you would get a totally different master private key. Obviously, all other derived keys and addresses from that master key would also be different. You would also get a different master key from a wallet that you extended with a passphrase.

And a wallet is an xpub?

An xpub is an extended public key. From it you can generate all the addresses at that particular derivation path. Or from that particular account if you want. Software like Ledger Live calls each unique derivation path a new account. But the xpub isn't enough to allow you to use all the features of a wallet. It's missing the signing keys - the private keys.

When you go to send tab, you can send from addresses that are in that xpub aka wallet?

You would be sending from addresses derived at a specific derivation path under the condition that you have the private keys that correspond to the addresses you are trying to send from. Like I said, the xpub alone won't give you that. The seed or extended private key will. Alternatively, you will need individual child private keys for each address.

Or can you combine from multiple xpubs aka wallets in the send tab?

Not by default because the xpub corresponds to addresses generated on a specific derivation path. The thing you call an account. The account contains the xpub for that derivation path but not for other accounts. What you could do is create a wallet with imported private keys from multiple other wallets (be it from Sparrow or other software). You could then fund and make transactions from the addresses derived from those private keys. 

[nc50lc]

What's the difference between a wallet and an account?

Since we're in Sparrow thread, you must be pertaining to "Add Account" option, no?
If so, those are just another set of keys that are derived from the same seed phrase but with separate derivation path.

Technically, each is derived with incremented "account_index", starting from 0' of the wallet's first "account", and 1' in your first 'Add Account' button usage.
For example: If your main wallet's main account has the derivation path of (in the settings): m/84'/0'/0' (Master prvKey/Purpose'/Coin'/Account'), your Account#1 would be m/84'/0'/1'.

So basically, your entire wallet includes all of the keys and extended keys that can be derived from your seed phrase,
While your accounts are just keys from different derivation paths within the same wallet.

[satscraper]

What's the difference between a wallet and an account?

Your put your questions into the thread dedicated to Sparrow thus I guess they are relevant to it.

Sparrow is the client which has the ability to manage multiple wallets and accounts.

Entities that define the given wallet are: policy which may be either Single Signature or Multy Signature, Script Type, Keystore determined in fact by SEED and added by the way you opt.

Each of those wallets may have ^{in Sparrow} up to 10 accounts which differ by 'account' index in its derivation path m / purpose' / coin_type' / account' /.

When you create the wallet first Sparrow creates account with index=0

Then you can add to this wallet other accounts.

Can a seed phrase create multiple master private keys?

Nope

 Is that what accounts are?

nope, see above

And a wallet is an xpub?

xpub is the major component of the given wallet but they are not the same

When you go to send tab, you can send from addresses that are in that xpub aka wallet?

Those addresses are defined by the particular account  of the given wallet

Or can you combine from multiple xpubs aka wallets in the send tab?

Nope, no way to do it.

[btc-freedom-money]

I think what makes it more difficult to understand and learn about this like what an account and wallet is because every project has their own definition of what it is. In some cases the wallet is the app. And in other cases wallet is something inside the app, not the app itself. The problem is all projects try to explain how it works in abstract ways that simplify too much. Ideally there should be explanations for all experience levels, like beginner, intermediate, expert. When they explain in beginner terminology it makes it harder for intermediate users to understand because the intermediate doesn't know what a wallet is but knows what a master private key is and child key and how a HD wallet works so if those kind of universal terminology was used it would be easier to switch between wallet software. But now I know what an account is in Sparrow.

[nc50lc]

Ideally there should be explanations for all experience levels, like beginner, intermediate, expert. When they explain in beginner terminology it makes it harder for intermediate users to understand because the intermediate doesn't know what a wallet is but knows what a master private key is and child key and how a HD wallet works so if those kind of universal terminology was used it would be easier to switch between wallet software.

Yeah, it's kind of messed-up when they named the account derivation path "account".
Maybe an established term ever since when Bitcoin Core used "accounts" feature (before 0.17.0),
now, it just confuses some users like those who see Sparrow's account feature.

I'm not entirely sure on the history of naming the derivation path levels of standard derivation paths including BIP32's term though.
But to be fair, IMO there's no better term for its use-case.

[Forsyth Jones]

I think what makes it more difficult to understand and learn about this like what an account and wallet is because every project has their own definition of what it is. In some cases the wallet is the app. And in other cases wallet is something inside the app, not the app itself. The problem is all projects try to explain how it works in abstract ways that simplify too much. Ideally there should be explanations for all experience levels, like beginner, intermediate, expert. When they explain in beginner terminology it makes it harder for intermediate users to understand because the intermediate doesn't know what a wallet is but knows what a master private key is and child key and how a HD wallet works so if those kind of universal terminology was used it would be easier to switch between wallet software. But now I know what an account is in Sparrow.

You are putting the cart before the horse ... Before leaving for technical terms, you should try to know more common to beginners such as: Wallets, Exchanges, Transactions, Addresses, etc. Therefore, go to this guide to improve your knowledge: https://learnmeabitcoin.com/beginners/ , below is a brief explanation:

Many people confuse accounts with wallets, but technically, each term represents a function within a HD wallet structure:

Account = an account derived from the extended private key (also known as a wallet to facilitate the understanding of beginners).

HD (Hierarchical Deterministic) = When an "infinite" addresses derive, that is, even if you use 994 receiving addresses, your backup can restore funds from address 994 and all the others you use after this, so you don't have to  make backup the same seed more than once, because they are all covered by the master seed).

Wallet Application = application responsible for storing the key pair derived from your master seed, which derives the master key, typically, in a reputable wallet app, you can protect it with a password or PIN (numeric password).

STRUCTURE:
M / PURPOSE ' / COIN TYPE' / ACCOUNT ' / RECEIVING OR CHANGE / INDEX (IDX)

In practice, the account derivation structure is like this (without the spaces from the example above):

Code:

m/84'/0'/0'/0/i

m/84'/0'/0'/0/i - "i" represents the index that always starts with 0 that represents its initial receiving address (in computer science, we always start from 0, not 1).

You are here: "Account".
Normally, a wallet always derives the private keys from a standard address in the derivation paths (if you don't know this or other technical terms, go to this link and look) on account 0, i.e., m/84 '/0'/0 '/0/i, if you ask the wallet (app) to add a new account, technically you are accessing a new "account" (account 1) derived from your extended private key Derivation Path: M/84'/0'/1'/0/i, if you request a new account, then the next account is accessed in m/84'/0 '/2'/0/i and so on.

*Derivation Path in the applied example represents a native segwit account that is the most common (considered the standard): m/84 '/0'/0 '/0/i or BIP84.

Explore the iancoleman tool. To understand all the operation of an HD wallet structure in practice (do not enter your real online Seed or you will risk being stolen).