In the last few months I've had two newcoiner friends who had issues with nostr:nprofile1qqsfy229w70e8lgtxavlz9t78k06yrel6fxyhreteafqet8kfxhhwmgpr9mhxue69uhhqun9d45h2mfwwpexjmtpdshxuet59uq3vamnwvaz7tmjv4kxz7fwwpexjmtpdshxuet5uzhxm7 Green wallet and Cobovault. On both occasions their BIP39 seed phrase did not work when restoring on an alternative wallet. One tried nostr:nprofile1qqsvxq03xdev3uxehjqcdkr5lfzl5vawmcf7vm6ps73m6ghwg8y4k2spz4mhxue69uhk2er9dchxummnw3ezumrpdejqz9nhwden5te0dehhxarj9eekcmm5dpujuamfdcq9v6rc which showed a zero balance, the other nostr:nprofile1qqsqxqmml7j56x4lrylqm4h2ce9etmrmeunyqfheu8kjewdsuwn7mkqpzfmhxue69uhkzum5wfskctnwd9hx5cgpramhxue69uhky6t5vdhkjmndv9uxjmtpd35hxarn9ehkumrfdejsmd83ak which did the same.

Strangely the first was able to get nostr:nprofile1qqsqxqmml7j56x4lrylqm4h2ce9etmrmeunyqfheu8kjewdsuwn7mkqpzfmhxue69uhkzum5wfskctnwd9hx5cgpramhxue69uhky6t5vdhkjmndv9uxjmtpd35hxarn9ehkumrfdejsmd83ak to work. The Green guy was able to fix his issue but withdrew all his funds because of this.

Anyone have any idea what's going on bearing in mind I'm 99% sure the words were correct and they weren't using a passphrase.

#Bitcoin

#asknostr

nostr:nprofile1qqstnem9g6aqv3tw6vqaneftcj06frns56lj9q470gdww228vysz8hqpzdmhxue69uhkzmr8duh82arcduhx7mn9qy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxg8mv947

nostr:nprofile1qqspnzgrfett3asxcuj0gksje6z2zxzpvgd27uvz58m9vsuqh8zzw6cpr9mhxw309a382emdv9hzumt8w4ujumn9wsargwp58qq3vamnwvaz7tmzv46xztnwdaehgunfdshxxctd9a4sn7

nostr:nprofile1qqst0mtgkp3du662ztj3l4fgts0purksu5fgek5n4vgmg9gt2hkn9lqppemhxue69uhkummn9ekx7mp0qys8wumn8ghj7mn0wd68ytn9d9h82mny0fmkzmn6d9njuumsv93k2tct43vxq

Reply to this note

Please Login to reply.

Discussion

Derivation path.

Derivation Paths | Locating Keys and Addresses in HD Wallets https://learnmeabitcoin.com/technical/keys/hd-wallets/derivation-paths/

Seriously that’s weird. Sounds like a derivation path problem though. I would tell them there are ways to create different wallets from the same seed, but as long as they have their seed they can recover funds.

I imagine the reason it’s different in green is because Blockstream does a special setup so it might not be standard. Sorry I wish I had specifics to investigate. If I might be able to help I can try, just a factor of available time right now unfortunately

So I get this right:

They were using Blockstream green WITH cobovault as the key? Because in that case I would try a fresh Green wallet restore on a different device first with the cobovault. Basically same setup as they did the first time to see if it comes back.

Or are you meaning one had a problem with Green and the other had a problem with Cobovault? Also how did they lose their setup or disconnect the wallet? Any details on what happened exactly? Might help figure out the process to bring it back.

Firstly Guy, both issues have been resolved so no need to spend any more time on it.

I prob wasnt clear. 1st person tried his Green seed in Blue and got zero balance. His original issue was a 2FA thing that he never set up denying him access to Green, so I suggested restoring in Blue. He eventually fixed the 2FA.

2nd person tried his Cobo seed in Nunchuck and got a zero balance. He then tried it in Blue and this worked. His issue was it was the Cobo setup simply no longer worked.

I now understand its a derivation path thing but it surprised me because I thought most of these well known wallets use compatible paths. I have a pretty rudimentary understanding of derivation paths and thought they were only important to record with mu-sig setups.

Bottom line is its pretty horrible UX when a new user, or any user for that matter types their seed phrase in during recovery and is hit with zero balance. And were also never prompted to note anything other than the seed.

On the positive side when it happens again I'll be able to advise them better.

What’s funny about that too is that there aren’t but a handful of common derivation paths. You could write a script to load and check all the possible ones in the background to verify any balance, and then prompt the user if one is found while the user selected a different one.

Something like “you chose a P2SH derivation, but there is a Bech32 derivation with 0.2157 bitcoin in it. Would you like to load that as well?”

Apparently Blue Wallet does something like this, although it still didn't work with the Blockstream Green seed.

This happened to a friend of mine. He thought he lost a ton of Bitcoin and almost threw his “empty” seed words out.

Friend of mine had an issue with this, idk if you can help but I gifted him btc by sending to a bluewallet from muun, then writing him the seed phrase. He tried setting up via phoenix wallet but it shows this:

Any tips on how to recover?

If anyone has had a similar issue and has some direct advice… #asknostr #bitcoin

nostr:nevent1qqsz9sd5qcvtt4vvep4al63n7fvvfpmczpw54apelya559t7wy880vcyc8zzj

Must be an issue with the derivation path.

It’s prolly some weird derivation used by Blockstream.

I stopped using my own Green wallet and deleted it because of how poor their customer support was for a completely different issue I had.

The main issue I can imagine is that the derivation path did not match where it was sent. Check and make sure the wallet is either: Legacy, Taproot, Segwit, or Wrapped segwit.

m44/...

m49/...

m84/...

m86/...

Check all of those derivation paths. And if it is not found within one of those, then it was initially set up with a non-standard derivation path.

I know that blue wallet will search common derivation paths when restoring a seed. They'll do legacy and even aezeed (LND on chain). So it makes sense they could find the funds.

Blue didn't work with Blockstream Green seed.

Well that sounds scary