Watch only wallet help CC

[nagasaki23]

A few months ago I setup a CC for stacking sats off swan. I generated a watch only wallet from the CC xpub QR code, and began sending my sats to the addresses generated from that watch only wallet. Yesterday I decided to switch to blue wallet. I exported the skeleton from that same CC to my blue wallet and it shows zero balance so I scanned the CC xpub QR code with the blue wallet and it popped up my balance. I can not sign transactions generated from the watch only wallet. The CC says something like "can not sign with out the leys. Need 'XXXXXX' keys". I'm sure I'm missing something here so any help but much appreciated.

[LoyceMobile]

I setup a CC for stacking sats off swan.

.
Can you explain what CC and swan mean in this context?

[BlackHatCoiner]

Do you have the seed phrase or the private key(s)? If you don't you can't spend your coins. A watch-only wallet is what it says, a wallet that's supposed to only be watched. Explain what's CC, swan and how did you generate a watch only wallet since you didn't have a master public key to begin with.

[DireWolfM14]

I setup a CC for stacking sats off swan.

.
Can you explain what CC and swan mean in this context?

I think the OP is using CC as an abbreviation for ColdCard, maybe.  Swan is an exchange that makes scheduled purchases of bitcoin by drafting a small ACH transfer from your bank account.  I assume they only operate in the US, but not sure about that.

@nagasaki23, If I'm correct in my assumptions that your coins are in a ColdCard wallet, you can use Electrum to connect to the hardware wallet.  You'll need to create a new wallet, and for type of wallet pick "standard," then select "Use a hardware wallet."  Also, when you set up your hardware wallet you were instructed to write down a 12-word or 24-word seed phrase.  That seed phrase can be used to restore the wallet in Electrum, but that would defeat the purpose of having a hardware wallet in the first place.

[BitMaxz]

I think you did wrong in trying to sign a transaction can you tell us what did you choose to sign the transaction from this image below


Have you scanned the transaction through QR code to sign the transaction?

You need to export the transaction you made into a file and transfer it into coldcard SD card then put the SD card back to ColdCard and sign it there it should generate a signed hex file that is ready to broadcast and open it in your Blue wallet.

I suggest you follow the guide on blue wallet youtube video on how to use coldcard with blue wallet here https://www.youtube.com/watch?v=hF2MyDB0nno

[nagasaki23]

Yes CC is cold card. Swan is the exchange. I did export the psbt to the sd card and insert it into the CC and hit "Ready to sign to which i get this msg on the "none of these keys belong to this coldcard. Need "XXXXX" i verified the wallet number is the one that was created in blue with the exported CC skeleton wallet as well. The skeleton and the watch only wallet came from the same cold card. I have the leys the addresses with the btc just dont show up in the skeleton wallet.


So I was able to fix it using this

https://bitcoin.stackexchange.com/questions/112667/sent-funds-to-coldcard-bip-32-address-how-can-i-transfer-them-out-to-a-differen

Worked perfectly. Would someone explain possibly what that even did. I know it's derivation realted but I'm so new to this level of tech stuff

[moderator's note: consecutive posts merged]

[BitMaxz]

So I was able to fix it using this

https://bitcoin.stackexchange.com/questions/112667/sent-funds-to-coldcard-bip-32-address-how-can-i-transfer-them-out-to-a-differen

Worked perfectly. Would someone explain possibly what that even did. I know it's derivation realted but I'm so new to this level of tech stuff

So your problem is related to the derivation path or other accounts you might be generated a skeleton wallet with a different derivation path?
It is the same problem as this old thread below

- https://bitcointalk.org/index.php?topic=5364268.0

And solved the case by following this https://bitcointalk.org/index.php?topic=5364268.msg58116216#msg58116216

So you recover your funds by exporting the wallet.json file and editing some text then import to bluewallet?

[o_e_l_e_o]

Worked perfectly. Would someone explain possibly what that even did. I know it's derivation realted but I'm so new to this level of tech stuff

The majority of wallets create a master private key, either from scratch or by deriving it from a seed phrase, and then use that master private key to create a branching tree of further private keys using hash functions. Some wallets follow what is known as BIP 44, 49, and 84 with the tree they create. The standard derivation path for a BIP 44 wallet (which creates legacy addresses) is m/44'/0'/0'. This means you take m, your master private key, and derive the next key using the hardened index (denoted by the ' symbol) number 44. You then take that key, and use it to derive the next key using the hardened index number 0. You then take that key, and use it to derive the next key using the hardened index number 0. This key is then the extended key for the wallet account, and again goes through a number of derivations to generate your individual private keys. This will be /0/0 (non hardened index 0) for your first address, /0/1 for your second address, /0/2 for your third address, and so on. Your first change address will be at /1/0, your second change address will be at /1/1, and so on.

Other wallets follow different derivation paths, the most common alternative just being m, meaning you wallet just takes your master private key and appends the /0/0 for your first address directly. So instead of m/44'/0'/0'/0/0 as you would end up with above, you now end up with m/0/0.

Accounts, keys, and addresses at different derivation paths are completely separate, and for the sake of signing transaction might as well be considered as entirely different wallets. A key at any given derivation path cannot sign for a key at any other derivation path. And because they are derived with hash functions, it is a one way process and you can't work backwards up the tree (except in some rare cases which are irrelevant here) - meaning you can't take a key at m/0/0 and work out the key at m which produced it. The process is deterministic though, which means that if you start with the same master private key then you will always derive the exact same child private key at the same path.

Essentially, all you did was tell your wallet to derive at the path m instead of the path m/44'/0'/0', which was the same path your initial wallet used, and so they matched up again.

[nagasaki23]

Awesome. Thanks for the explanation that was very simple and clear. Always find what I'm looking for on this forum so I appreciate the time you all take to help out the newbies!