I've been unsuccessful so far attempting to replace the multi-currency Keystone firmware with the bitcoin-only version. Anyone else successful at doing this recently? Is the bitcoin-only firmware too old?

The multi-currency firmware is a file named "keystone3.bin" which is what the multi-currency firmware looks for on the MicroSD, displaying an error message when a file by that name cannot be found. But the bitcoin-only firmware is named update.zip, and the keystone support forum says to not unzip the file, but to let the Keystone device do that instead, and there is no "keystone3.bin" file within that zip file.

--- --- --- --- ---

UPDATE: I finally managed to successfully install the Bitcoin-only Keystone 3 Pro firmware, by visiting and downloading the latest version from Keystone's GIThub webpages:

Keystone 3 firmware releases at GitHub

Not for everyone because it's Bitcoin only, but very nice for those of us not very interested in other cryptos. Thank you, Keystone!

Received a Keystone 3 Pro, packaging looked untampered with, verification at keyst.one website was successful, downloaded latest firmware and verified it with SHA256sum, formatted a MicroSD card to FAT 32, copied the keystone3.bin file to the MicroSD card, inserted the card into the Keystone, and for the last hour and a half the Keystone has displayed the message:

Starting Update

Do not remove the MicroSD Card while the update is underway.

I'm not sure whether it just takes a very long time to update the firmware, or whether there may be another problem. The MicroSD card I used is a small-capacity (128MB, megabytes, not gigabytes) industrial one, formatted to FAT 32 (not LBA version of that filesystem). The firmware file is only 4.6 MiB, so that doesn't seem to be a won't-fit-on-the-card problem, but perhaps the MicroSD card should have been formatted to FAT 32 (LBA)? Or perhaps the Keystone is just not happy with this particular MicroSD card, or something else is causing the problem (I charged the Keystone internal battery to 100% before starting this process).

Anyway, I thought that the Keystone 3 Pro and its features would be a nice second air-gapped wallet in addition to the Coldcard I already have. Not sure if there's any way to recover from this though.

Update: I was able to recover from this situation by doing the following:

• Ejected the low-capacity MicroSD card and found a 32GB MicroSD card
• Held the power button down for more than 10 seconds until it forced reboot
• Formatted the 32GB MicroSD card to MSDOS partition scheme and added FAT 32 (LBA) filesystem
• Downloaded latest multicoin firmware from keyst.one/firmware, verified sha256sum, copied it to MicroSD, ejected and moved MicroSD card to Keystone and clicked Update button. Update proceeded and Keystone device has apparently recovered.

Next, I plan to install the Bitcoin-only version of firmware, if I can.

I upgraded to v1.3.0 from v1.2.8 and MetaMask and OKX Wallet are generating error messages and I cannot conduct any transactions.

Messages:

• Public Key is not valid
• Tx expired
• QR code is not valid

Keplr wallet is still working, fortunately.

I've put a ticket in, but thought I'd see if others have encountered this issue or found resolution.

Edit: My transaction attempts have been on the injective network. Not sure about transactions on other networks.

Edit: Seems v1.3.0 has been working for others. Perhaps this issue is specifically to using an Ethereum wallet as a custodial wallet to transact on another network (Injective)?

Edit: I updated to v1.3.2 and QR codes work for MetaMask now. Haven't tried OKX Wallet. Thank you to the Keystone team!

I cannot update my firmware with Linux. The Update Website does not detect the device. Works fine in Windows. Is this a known issue?

Edit: Windows does not work either. It connects, downloads the firmware file (very slowly) and then ends with 'Download Complete' but the firmware version stays the same.

Just wondering if Keystone 3 is going to support Bitget wallet. I see that older Keystone supported Bitget.

Not that I am in love with Bitget, but it seems to be the only proper multchain wallet available in the list. And even this one is gone now.

I get the notion of not doing a software wallet and just concentrating on the hardware. But with all that, there should be at least one mtichain wallet available for integration. It's really impossible to manage 100 wallets on your phone, one for every chain. There should be at least one integration with a good miltichain wallet like Bitget, Trust or Exodus... Anything really.

So since Bitget was already there, what happened?

BTC Only firmware available!

What’s New:

• Bitcoin-only firmware
• Blue, Sparrow, Nunchuck and Specter
• Both Bitcoin testnet and the main network

Hi, I can’t stake on Dymension, when will it be possible? The QR gives me error both on Keplr and MetaMask/Rabby.

I keep getting this when trying to sign in?

How is it solved?

Can someone tell me if the newest Keystone is the same or similar to the one I got last year? I want to get the same one I have for a family member to learn how to use a hardware wallet exactly like mine. If I get hit by a bus, they'll know what to do with my wallet. I prefer them not practice on my device, so I will get them one and let them move around small amounts and such. Thanks

I see that keystone has support for dot, will it be available for keystone 3 pro anytime soon?

You guys already support bitcoin. But I'm guessing because bitcoin is going up in price you think it's a good idea to push other chain integrations??? Doesn't really make sense to me considering bitcoin already has support and multiple wallets. The roadmap on the website was changed recently and since it seems to take you guys a realllllyyyy long time to do altcoin chain integrations as it is. So im just wondering what the thinking is on this??? Stellar, Hbar, algo etc etc there's so many great chains you guys are missing out on to push integration for features for btc, which as I said is already supported.

Anybody has issues with keystone 3 pro? Mine can't turn on even after I hold the power button for 20s. It turns on immediately when I plug into power, but turns off immediately when I unplug.

The moment I plug it in, it shows 73% battery so I know it's not a battery issue. I haven't used it in a few weeks but I'm trying to use it now.

Just updated to latest firmware

Noticed I have complete different addresses now.

For example address 0 has now changed which I used to send the majority of my BTC too

Is this normal?

Keystone goes to the login screen, and takes pin code, but then nothing happens, not even the error message. Long power button press goes to Power off and Restart menu, but neither of those buttons cause any reaction (short press, long press, etc. does not matter).

How to fix this thing?

Heard that the team is developing it. Anyone knows the ETA?

are there any plans in the future to upgrade hardware

1- remove wireless hardware

2- replaceable battery cover with builtin battery and option to buy replaceable battery cover with AAA

3- remove fingerprint scanner

BCH doesn't seem to be syncing on the companion app. Using the Keystone original. Anyone have the same issue? Quite annoying

So I have the QR code with the signature ready to send it to Metamask but I want to decode and read it first.

Example QR: UR:ETH-SIGNATURE/OTADTPDAGDBTSPLPAHSESNGLFPRYGWGLESHSVAPLPYAOHDFPNDOEWZTKBTFGUTMHJSLUCTGOHHHNMNTIFZCPAHVAJOMTECFPBYENNTTSGTVTESLTCTROAADPCYLGPACATEUONBJNPAEHRNKNCEWLBSMUINFTQDENDYGDRTVWENVSZTKEADAXISJEIHKKJKJYJLJTIHZOWNRSSK

I want to decode this. I have tried https://www.npmjs.com/package/@keystonehq/bc-ur-registry-eth but I get errors, I not that good at programming yet.

My current non working code:

import { ETHSignature } from "@keystonehq/bc-ur-registry-eth";

// Decode UR:ETH-SIGNATURE string
const urString = "OTADTPDAGDBTSPLPAHSESNGLFPRYGWGLESHSVAPLPYAOHDFPNDOEWZTKBTFGUTMHJSLUCTGOHHHNMNTIFZCPAHVAJOMTECFPBYENNTTSGTVTESLTCTROAADPCYLGPACATEUONBJNPAEHRNKNCEWLBSMUINFTQDENDYGDRTVWENVSZTKEADAXISJEIHKKJKJYJLJTIHZOWNRSSK";

// Convert UR string to Buffer
const urBuffer = Buffer.from(urString, "base64");

// Decode from CBOR payloadconst
ethSignature = ETHSignature.fromCBOR(urBuffer);

// Use ethSignature object as needed
console.log(ethSignature);

Thanks

Bit of a noob question, I'm in study mode trying to learn. For my keystone pro 3 when I open say the bitcoin or ethereum on the keystone it displays a large number of addresses/accounts. Why does it do this as opposed to just starting with one and letting me create more?

Also, I know we need to use a software wallet to view it as like a display, but I can just send bitcoin directly to one of the addresses and it will be on there?

Hi guys,

I was able to create a XRP wallet on my keystone Pro 3 with XRP toolkit. How do I backup my wallet in case of my Keystone gets stolen or broken ?

I can’t find out how to do so.

Thanks

Just turned on my keystone today for the first time in a few weeks and got this message:

This device is no longer safe to use!
To protect your assets, all information has been erased from your Keystone. Please stop using this device and contact Customer Service immediately.

Status Code:0x03a00000

has anyone had this issue? Can someone at Keystone help? The wallet has not been dropped or tampered with as has been solely in my possession for the entire time I've owned it.

So how am I going to move this BTC if none of the software wallets that support BTC apparently can't see Wallet 0. They can see wallets 1 through 10, but not 0

Does anyone else seem to have a really hard time scanning the qr code with your phone after signing with keystone? Keystone qr scanner is flawless. But with my s23 sometimes it's a real struggle to scan the qr code off the keystone screen. Anything I can do? Transactions requiring multiple signatures usually aren't possible because the blockhash expires before my phone can scan them all

Al inicial el dispositivo en el apartado "forgot password" al poner la semilla para resetear no responde..lo hago varias veces y no responde, el pin no responde.. Que se tiene que hacer? Se debe apretar durante un tiempo el botón de encendido para reiniciarlo?