how to recover segwit bitcoin in taproot?

[q7naistar]

i exported these public keys from my exodus wallet: xpub6DA, zpub6ruWS, zpub6rhPfS.

from what i understand, xpub is for older addresses, and zpub is an extended public key for segwit (bc1q-starting) and taproot (bc1p-starting) addresses.

exodus gave no warnings, so i messed up and used a taproot address to receive bitcoin. now it's not showing up in my wallet.

i found a transaction on trezor at m/84'/0'/1'/0/1. i tried importing my seed phrase and setting the path to m/84'/0'/1' like online guides suggest, but still no transaction.

my wallet says it's wallet #1 for my zpub6ruWS address. so basically, my bitcoin is complicatedly stuck in a taproot address.

how can i get my money back?

[Satofan44]

exodus gave no warnings, so i messed up and used a taproot address to receive bitcoin. now it's not showing up in my wallet.

If you are sure it went to a taproot address then the issue is with the path.

BIP 44: m/44'/0'/0' (1addresses)
BIP 49: m/49'/0'/0' (3addresses)
BIP 84: m/84'/0'/0' (bc1qaddresses)
BIP 86: m/86'/0'/0' (bc1paddresses) - This is Taproot.

https://learnmeabitcoin.com/technical/keys/hd-wallets/derivation-paths/

i found a transaction on trezor at m/84'/0'/1'/0/1. i tried importing my seed phrase and setting the path to m/84'/0'/1' like online guides suggest, but still no transaction.

my wallet says it's wallet #1 for my zpub6ruWS address. so basically, my bitcoin is complicatedly stuck in a taproot address.

how can i get my money back?

How can you be sure it is Taproot if you say it is in this public key? According to https://slips.readthedocs.io/en/latest/slip-0132/:

BIP-0084 proposes a native-SegWit derivation scheme, encoding P2WPKH addresses in Bech32. However, the extended serialization format is presented with a zpub prefix but no version bytes. This is an issue since multiple values of the version bytes may encode to the same prefix.

In any case you can try out the other derivation paths, there is no harm in trying.

[nc50lc]

i exported these public keys from my exodus wallet: xpub6DA, zpub6ruWS, zpub6rhPfS.

from what i understand, xpub is for older addresses, and zpub is an extended public key for segwit (bc1q-starting) and taproot (bc1p-starting) addresses.

exodus gave no warnings, so i messed up and used a taproot address to receive bitcoin. now it's not showing up in my wallet.

I can't see the connection, you exported those xpubs from Exodus and then use one of those on which wallet?
You imported back to Exodus or something?

i found a transaction on trezor at m/84'/0'/1'/0/1. i tried importing my seed phrase and setting the path to m/84'/0'/1' like online guides suggest, but still no transaction.

my wallet says it's wallet #1 for my zpub6ruWS address. so basically, my bitcoin is complicatedly stuck in a taproot address.

Then Trezor is mentioned without explaining how it's involved.

Please explain the situation more clearly in detail.
You may use this sticky thread as a guide: [READ BEFORE POSTING] Tech Support Help Request Format

For now,
If I understand the situation correctly, your TapRoot address is derived at the derivation path m/84'/0'/1'/0/1... with the extended public key: zpub6ruWS...

If that's the actual scenario, the derivation path is still within the standards, so you may import it to Sparrow Wallet by disabling "Validate Derivations" in its settings since you'll be swapping script types and derivation path.
Then, to restore:

• Create a new wallet
• Select "Taproot" as script type (very important, do not skip)
• Click "New or imported Software Wallet"
• Select the number of words and type them in, and click "Create Keystore".
• Edit m/86'/0'/0' into m/84'/0'/1' before clicking "Import Custom Derivation Store".
  In this step, it wont be clickable if "Validate Derivations" is still enabled in the settings.
• After that, finish creating the wallet using "Apply".

If this doesn't derive the correct address, there something in those unclear explanations that's caused a discrepancy.

[q7naistar]

Let me describe my experience:
1. I created a new profile in Exodus. It didn't ask for a password, and the exported mnemonic phrases were all the same.
2. I exported the public keys from the second profile:
xpub6DALZDVFmbnxm2Uf...
zpub6ruWSbTpt1w2pRnZ...
zpub6rhPfSfwxbMuqC3...

3. I then set the third zpub as my receiving account on sell.app. When I had completed 3 orders but my wallet didn't show anything, I immediately stopped receiving payments and started looking for information.
4. According to some sources, the third address is for Taproot addresses.
5. As instructed, I checked the path using Trezor's tool. Here is the link:
https://btc1.trezor.io/xpub/zpub6rhPfSfwxbMuqC3MSp49aH7uFYz5gfouN4Yo2oKKxcFNgGvbDae6TwMWtLyAhEa6Z2suDLjFZD5eGAqqaxRNLtW7yPCMXatq6qTAYQZWsqL

6. I tried to create a wallet using the derivation path m/84'/0'/1', but the wallet showed addresses corresponding to the second public key (the one starting with WSb), and I couldn't find the correct third public key.

I tried adding my profile name "1" as a passphrase, but it led to a new set of addresses, which were clearly not the right ones.

Right now, my theory is that either the new profile has a hidden mnemonic phrase, or the money was mistakenly sent to a SegWit address, even though my public key is from Trezor.

[q7naistar]

i exported these public keys from my exodus wallet: xpub6DA, zpub6ruWS, zpub6rhPfS.

from what i understand, xpub is for older addresses, and zpub is an extended public key for segwit (bc1q-starting) and taproot (bc1p-starting) addresses.

exodus gave no warnings, so i messed up and used a taproot address to receive bitcoin. now it's not showing up in my wallet.

I can't see the connection, you exported those xpubs from Exodus and then use one of those on which wallet?
You imported back to Exodus or something?

i found a transaction on trezor at m/84'/0'/1'/0/1. i tried importing my seed phrase and setting the path to m/84'/0'/1' like online guides suggest, but still no transaction.

my wallet says it's wallet #1 for my zpub6ruWS address. so basically, my bitcoin is complicatedly stuck in a taproot address.

Then Trezor is mentioned without explaining how it's involved.

Please explain the situation more clearly in detail.
You may use this sticky thread as a guide: [READ BEFORE POSTING] Tech Support Help Request Format

For now,
If I understand the situation correctly, your TapRoot address is derived at the derivation path m/84'/0'/1'/0/1... with the extended public key: zpub6ruWS...

If that's the actual scenario, the derivation path is still within the standards, so you may import it to Sparrow Wallet by disabling "Validate Derivations" in its settings since you'll be swapping script types and derivation path.
Then, to restore:

• Create a new wallet
• Select "Taproot" as script type (very important, do not skip)
• Click "New or imported Software Wallet"
• Select the number of words and type them in, and click "Create Keystore".
• Edit m/86'/0'/0' into m/84'/0'/1' before clicking "Import Custom Derivation Store".
  In this step, it wont be clickable if "Validate Derivations" is still enabled in the settings.
• After that, finish creating the wallet using "Apply".

If this doesn't derive the correct address, there something in those unclear explanations that's caused a discrepancy.

thank you very much for your suggestions. However, I followed your tutorial, and unfortunately, the method didn't work.


Here is a screenshot:
https://imgur.com/a/huMHXJ0