Need help with wallet access restoring

[Aleksey_575]

I've got the following situation:

I worked with BTC transaction in OWNR wallet for 4 last years - last successful one was made on July 14
Next day OWNR has stopped broadcast BTC transactions and the problem is still active (no adequate response from wallet support)
It correctly shows transaction history with all required details according with any blockchain explorer

Surely I've tried to open my wallet in Sparrow by seed phrase with BIP39 passphrase
Sparrow correctly restore all Legacy transactions and addresses so I've transferred the balances to the new wallet

but when I've tried to do the same procedure in Sparrow with SegWit addresses it shows no addresses at all - even for fresh transaction from July 14
Of course I've checked every word in seed and made import procedure several times, tried all SegWit protocols in Sparrow - results are the same

could you provide helpful comments for the situation ?

[hosemary]

I just installed OWNR wallet on my mobile phone to see how it works.
I created a new wallet on OWNR and I was able to import both nested segwit and native segwit wallets to Sparrow successfully. You probably did something wrong when importing your segwit wallet into Sparrow.

[Aleksey_575]

I just installed OWNR wallet on my mobile phone to see how it works.
I created a new wallet on OWNR and I was able to import both nested segwit and native segwit wallets to Sparrow successfully. You probably did something wrong when importing your segwit wallet into Sparrow.

Thank's for the reply - but there are no "segwit wallets" just segwit transactions (may be it just a question of terminology) - could you make input BTC transaction to this fresh OWNR wallet and then output it ?

.... You probably did something wrong when importing your segwit wallet into Sparrow.

I do hope for this

one idea - I input wrong derivation path - is it possible to understand the correct one by looking at transactions protocol in blockchain explorer ? - in Jason format may be ?

[hosemary]

but there are no "segwit wallets" just segwit transactions (may be it just a question of terminology)

When you go to "Receive coins" in OWNR wallets, there are three options.
"Default" gives you legacy addresses, "Compatible" gives you nested segwit addresses and "New" gives you native segwit addresses.

In sparrow, you should select the "Script type" depending on which type of addresses you used in your OWNR wallet.

could you make input BTC transaction to this fresh OWNR wallet and then output it ?

If you generate the correct addresses in Sparrow, you will surely see your transactions.

[Cricktor]

I don't know this OWNR wallet but as hosemary confirmed to be able to restore Segwit address types from OWNR in Sparrow, I would assume that OP did something wrong with script type or derivation path for Segwit address types during restore in Sparrow.

If he managed to restore legacy addresses correctly then apparently the mnemonic recovery words were correct.

[hosemary]

I don't know this OWNR wallet but as hosemary confirmed to be able to restore Segwit address types from OWNR in Sparrow, I would assume that OP did something wrong with script type or derivation path for Segwit address types during restore in Sparrow.

Unless OP changed the derivation path manually in Sparrow, there shouldn't be any problem with the derviation path.
I could generate the same addresses as OWNR wallet in Sparrow using standard derivation paths.

m/44'/0'/0' for legacy wallet, m/49'/0'/0' for nested segwit wallet and m/84'/0'/0' for native segwit wallet.

[Aleksey_575]

Great thanks to everyone for the comments !

Sparrow automatically shows all accounts for the seed in case of Legacy type
but for SegWit one has to add accounts manually one by one

[nc50lc]

Sparrow automatically shows all accounts for the seed in case of Legacy type
but for SegWit one has to add accounts manually one by one

I tried this in Sparrow v2.2.3 and it doesn't seem to be the case.

My test BIP39 seed phrase with funded account_index 0' and 1' of standard BIP44 derivation path only restored the first account even thought the second one has transactions.
The next account has to be manually restored using the "Add Account..." button.

Same happened to its Native SegWit counterpart.
Additionally, the main wallet is also loaded with number of addresses based from the wallet's gap limit, not like the "no addresses" as described in the OP.

Perhaps, you're using an older version of Sparrow?