Mycelium does not decode private key BIP38 anymore after scanning NFC wallet

[Juul]

I guess it started with the recent update. I have access to my btc in other ways like private key QR code, so that is not a problem.

I've tried everything but after typing in my passphrase Mycelium halts.

[1713428818]

1713428818

[BitMaxz]

Do you have a seed backup of your Mycelium wallet?
You can retrieve all of your private keys from Mycelium with your seed using this tool below.

- https://iancoleman.io/bip39/

Or if you have a PDF backup you can uninstall and reinstall the wallet to erase data and pin and import the backup PDF but if you don't have a backup don't do this because all of your data will be deleted.

Read the source from here: Can't decrypt my mycelium private key. #117

[LoyceMobile]

I've tried everything but after typing in my passphrase Mycelium halts.

Could it be processing the data? BIP38 takes a lot of cpu power to decrypt.

[Juul]

I've tried everything but after typing in my passphrase Mycelium halts.

Could it be processing the data? BIP38 takes a lot of cpu power to decrypt.

That could be the case but it decoded the private key just fine until now. Sure, I can access my btc in a different manner but I like my nfc chip wallet 

[HCP]

That could be the case but it decoded the private key just fine until now. Sure, I can access my btc in a different manner but I like my nfc chip wallet  

Just to clarify... you have your BIP38 (aka "encrypted" private key) stored on an NFC chip... and you used to be able to scan it using Mycelium, enter your passphrase and then Mycelium would decode it and then add the private key to your wallet?

I'd honestly never heard of that... I didn't realise Mycelium even had NFC reading functionality in it... I thought you could only import via QR Code or copy/paste WIF key.

Anyway, I just tried copy/pasting a BIP38 encrypted private key (created using bitaddress.org) into Mycelium using the "clipboard" method and it asked for the password... I entered the password and Mycelium says "Preparing decryption key..." and then just sits there doing sweet FA... so I'm guessing that's a bug in the newer version(s).

I have taken the liberty of creating an issue on the Mycelium Github: https://github.com/mycelium-com/wallet-android/issues/532
Feel free to add to it.

[Juul]

That could be the case but it decoded the private key just fine until now. Sure, I can access my btc in a different manner but I like my nfc chip wallet  

Just to clarify... you have your BIP38 (aka "encrypted" private key) stored on an NFC chip... and you used to be able to scan it using Mycelium, enter your passphrase and then Mycelium would decode it and then add the private key to your wallet?

I've stored the BIP38 encrypted key on a chip implant under my skin

So whenever I want to spent some funds I transfer some to Mycelium from the chip out of my hand.

But thank you very much for the double check.

[Juul]

https://www.youtube.com/watch?v=gSvq2q_ofA4

[BitMaxz]

https://www.youtube.com/watch?v=gSvq2q_ofA4

Omg... Is this your video? it's interesting if it's true but how the phone actually scan the small thing to open the mycelium directly and ask for a decrypt password?
I can't believe honestly, but it seems real? or he set the vol button up or down to open mycelium directly?

I mostly heard NFC in cards where you can load or topup it using phone with NFC supported.

[HCP]

... but how the phone actually scan the small thing to open the mycelium directly and ask for a decrypt password?

It would have been using a simple dataset on the tag that was a "bitcoin:" URL... as described here: https://www.reddit.com/r/Bitcoin/comments/2n0k3i/breaking_bitcoin_nfc_payments_now_secure_bip38/

Mycelium registers a listener in Android that advertises that it can handle "bitcoin:" URLs... so when you scan the NFC tag... it finds the "bitcoin:" URL and launches Mycelium automatically (if configured to use Mycelium as the default app for "bitcoin:" URLs, otherwise it'll prompt which app to use like it does on my device).

It's just like scanning a QR Code that has the same URL... like this one:


(NOTE: Password should be "password123", but the functionality in Mycelium is broken as per the OP)


When I scan it using "Barcode Scanner":



and tap the "Open Browser" link... it prompts to open it with Mycelium (or one of the other apps that is registered to handle "bitcoin:" URLs ):

[Juul]

https://www.youtube.com/watch?v=gSvq2q_ofA4

Omg... Is this your video? it's interesting if it's true but how the phone actually scan the small thing to open the mycelium directly and ask for a decrypt password?
I can't believe honestly, but it seems real? or he set the vol button up or down to open mycelium directly?

I mostly heard NFC in cards where you can load or topup it using phone with NFC supported.

It is a NFC chip the implant   The size is app. a rice grain.

Is there another BTC wallet which can do the same? I dont want to wait that long.

https://www.youtube.com/watch?v=pdauofdGFBM

https://dangerousthings.com/

[HCP]

Is there another BTC wallet which can do the same? I dont want to wait that long.

Not to my knowledge... direct BIP38 "importing" support was never widely implemented as far as I can tell. Seems most wallets required you to decrypt it first

[Juul]

Is there another BTC wallet which can do the same? I dont want to wait that long.

Not to my knowledge... direct BIP38 "importing" support was never widely implemented as far as I can tell. Seems most wallets required you to decrypt it first

That's too bad. Let's hope that Mycelium has not completely stopped supporting BIP38. Thanks in any case for thinking along.

[HCP]

That's too bad. Let's hope that Mycelium has not completely stopped supporting BIP38. Thanks in any case for thinking along.

The good news is that apparently they have not stopped supporting it

I got this notification from github regarding the issue that I created:

We had a bug that should be fixed in 3.2.0.17 which is rolling out as soon as Google approves the release or whatever they do that delays releases some 4 to 5 days after we upload them. Please open a new issue if the problem persists on 3.2.0.17

That was posted yesterday, so hopefully the new version will show up on the Google Play Store any day now... currently, I can still only see 3.2.0.11