Sparrow wallet question...
How do I get Sparrow wallet to show me both my native segwit and segit accounts ? they both show up on L*dger live but only the native segwit shows up on sparrow
#asknostr
Sparrow wallet question...
How do I get Sparrow wallet to show me both my native segwit and segit accounts ? they both show up on L*dger live but only the native segwit shows up on sparrow
#asknostr
I hope this question makes sense lol 🤔
need to change the derivation path.
Last time I used sparrow for a similar use case I imported the seed a second time, this time selecting the other derivation path I want track (segwit I think you mean nested segwit m/49'/0'/0'/n and for native segwit is m/84'/0'/0'/n) and I considered them like 2 different wallets.
Ooof I'm so lost lol
Not a completely understandable explanation but maybe anotther pice of your puzzle: create a secon wallet (file - new wallet) and import your hardware signing device with an explicit derivation path.
Another account in the same wallet file will NOT work for your purpose ( as described here https://sparrowwallet.com/docs/coldcard-wallet.html#bonus-adding-an-account )
sparrow has also an explixit selector when creating wallet that makes you select what wallet you want, and change automatically the derivation path (it is native segwit by default).
Also, to be sure you want the nested segwit wallet: the address you miss here are the ones that starts with "3"?
Yeah I have some that start with 3. Was hoping to consolidate into the native segwit account. But proving to be too complicated for me lol.
Think I can just use ledger to send from segwit to native segwit, which is a sort of consolidation? In a way?
Yeah its a solution. I dont know if ledger has a utxo selector in the UI. To consolidate you basically send to yourself a transaction with your little utxos (the coins you received from previous transactions). But they need to be selected with a good ui, or risk that the software can compose a tx that dont spend the right utxos
nostr:nprofile1qqstu7jjjx6n969erredexq539y2x0f7pks80zxhg9hh8dx8298s3esppemhxue69uhkummn9ekx7mp0rt8eme: I've had the same question from users as well. Why didn't you implement the function to create a new account within the same wallet file with an absolute derivation path as "advanced settings" when creating a new account?
You can do this if you create the new account with a watch only keystore, but I haven’t seen a compelling reason to add this as a general feature.