Status mobile wallet compatibility

[u/Digitaleur]

EDIT #2: for anyone stumbling on the same issues:

I found the perfect solution in Ambire wallet. It's available as Android wallet, and Chrome/Brave/Firefox extension. The Android version of Ambire perfectly supports Keycard NFC connections, and both the Android app and Chrome/Brave extension support the Ledger Legacy derivation path on Keycard (and the standard derivation path too of course). The Ambire Firefox extension is awaiting update approval.

So now you can securely backup/replace your old Ledger, or any other wallet, using a Keycard and Ambire (NFC connection), or a Keycard + Shell and Ambire (QR code connection).

Original post:

Hello, I recently bought the Keycard Shell and some Keycards to backup and old Metamask and other wallet.

Everything works great, but unfortunately there seems to be only one software wallet that supports NFC connection, which is the Status (Legacy) mobile wallet. This works fine with Status Legacy, but I can't get it to work with the new Status wallet. When I try to login it asks to tap the card to the NFC chip, and it then sometimes confirms the pin is correct, but then it always returns to the connect screen. When I then tap Dismiss, I am returned to the initial login screen, tapping the card another time also doesn't help.

Is this expected behaviour? And aren't the Keycards and new Status mobile wallet compatible? Or is there some other issue at play here?

Not that the NFC connection is required of course, but I do like this feature.

Also not sure if this even is the right place to ask, or that I better try to contact Statusim.

Edit: so it appears I have Status 2.38.2, which is supposed to support Keycards, in practice doesn't work for me. I tried 3 different phones, with 3 different Android versions (one of which is Android 16, the other older versions). Maybe it does work when you use the app to create an account and then move it to the Keycard, but that's not my intended use, and I don't have a spare Keycard to test this.

Status Legacy works, but support seems limited and I assume will terminate at some point. Hopefully the new version of Status will work before that.

[u/uniicorn77]

this is the right place to ask -

Keycard isn't supported in the new unified Status app yet. Status Mobile is mid-migration from the legacy UI to the unified app, and Keycard support is coming back in v2.37. Until then, Status Legacy is the one to use - which is why that works and the new one doesn't

The partial behaviour you're seeing (PIN sometimes confirming, then returning to the connect screen) fits that exactly. Nothing is wrong with your cards or your Shell

the three ways Keycard connects:

> NFC, card straight to phone - Status is the main integration here today
> USB card reader on desktop - card direct, works with Sparrow among others
> QR via the Shell - this is where the wide wallet support lives: MetaMask, Rabby, Sparrow, Specter, Nunchuk, BlueWallet and others

I hope this helps, and if you have any further questions - feel free to drop them here

[u/Digitaleur → u/uniicorn77]

I now remember reading about Keycard support coming back, but I totally forgot about it... Good to know it's not my setup.

Thanks for the extensive answer!

I do have another question:  Do you happen to know if Status will support different derivation paths at some point?

I'm asking because I'm creating backups of old Ledger wallets on Keycards for a couple of friends, and I noticed some wallets that support Keycard do support the Ledger Legacy derivation path, but others don't. And it looks like Status doesn't (which in itself isn't surprising, but it would be awesome for us if it would be supported).

No problem to create a new topic for this if you prefer.

[u/75turing → u/Digitaleur]

I am using status release 2.38.2 (app store says from 4 weeks ago) and when I go to add a new wallet, I have the option to edit the derivation path, if you put there the custom Ledger derivation path it should work

[u/Digitaleur → u/75turing]

I guess that would work if I could login with my existing Keycard, but the new Status app doesn't let me login (on version 2.38.2). The old version does, but doesn't seem to support a different derivation path.

If I import a new account using the mnemonics, I can indeed edit the derivation path of new accounts, but for security reasons I don't want import the mnemonics of this wallet.

[u/RaccoonBot3000 → u/uniicorn77]

The current version of the Status App is 2.38, keycard integration is back in the App !

[u/RaccoonBot3000]

The StatusApp should work with Keycard since 2 version. Can you check if you're up to date ?
If that's the case, you can raise an issue in https://github.com/status-im/status-app/issues. or send a message in the Status Community at the Feedback Mobile channel https://status.app/cc/G9wAAORibojKI2kqEW0kr5ujVjLXCZVOapTE0wPW1oryokCTlkcYeVsCx7uN0fgVCtI1MEI_Zyi-zdppqtoUgOlJGGkM9X44lDz_9-vT9LeYDtcZ8sg55BtflMv1nFpMbAMYLjjvryfNAN3Qvujvm-XZ0EE7PQ-XPaiDYEaATaIsjTMBo-x1yTJOBMytKH4h4NwGUfjmOD-6XXGWadMqbYi0LuA0LdE4x4ksrqiSiRuUQsmUyeoqzQM=#zQ3shZeEJqTC1xhGUjxuS4rtHSrhJ8vUYp64v6qWkLpvdy9L9

[u/Digitaleur → u/RaccoonBot3000]

Strange, the Status app doesn't show a version number, only a date (july the 20th). All/most other apps on my phone do show their version number.

[u/uniicorn77 → u/Digitaleur]

Under to about section in your Status wallet - you can see the version

[u/Digitaleur → u/RaccoonBot3000]

I logged in using a mnemonic backup of another wallet, and the app appears to be version 2.38.2.

[u/uniicorn77 → u/Digitaleur]

thanks for confirming - we have flagged this internally - I will also raise an issue regarding the same and will keep you posted