frame VS keepkey-firmware

Regarding your earlier comments on Frame, did you try the AppImage? At least on the x86 side of things, the AppImage just works, and I don't think I've ever seen an AppImage that didn't "just work". The arm64 version can be seen on their releases page here: https://github.com/floating/frame/releases/tag/v0.6.6

Using frame.sh instead of metamask helps. It isn't connected to a single chain at a time, but all of the chains you've added. For example you can use dapps on multiple chains at the same time but never go through the step of switching networks. Also sounds like what you're really complaining about is delay period for fraud proofs, that should not be abstracted away because bridging without waiting is likely costing you more than you're making in returns if you bridge too often.

MetaMask provides an extension to add a wallet feature to your browser so that you can interact with dapps. This was the first project to provide this feature back in the day, but it's now quite outdated; A much better alternative would be Frame. A wallet needs an RPC node to talk to, and a new user doesn't want to have to worry about this, so MetaMask uses Infura as their default. But you can go into settings and change it, either to your own node or to a node hosted by someone else.

As your next step, I'd suggest trying alternative apps for accessing and managing your account(s). I'd personally suggest Frame (https://frame.sh/), but most use MetaMask (which is available as a browser extension).

gotcha, maybe check out frame (https://frame.sh) — you can import any wallets, hardware, seeds, private keys, etc. If you want to use it with any defi, there’s a companion browser extension.

I work on Frame (frame.sh) and used MEW to get a keystore file for testing our import keystore flow. The file I got was a different version (v4) and format from the expected v3, and our import flow does not support it at all. Digging deeper, we use `ethereumjs-wallet` to parse the keystore files - this library does not have a fromV4 method, and the existing fromV3 does not work at all with the MEW file.

Just wanted to install frame.sh as a new web3 wallet. It tells me to add "frame companion" to Edge, it warns me about:

So try MetaMask, or my personal favourite for stuff like this is: http://frame.sh and play around with derivation paths.

Frame Wallet does a few things Rabby doesn't and also supports hardware wallets but lacks the contact security check.

open source firmware, hardware

KeepKey's the cheapest out of the three and it's the one I use. It looks like there's development again on it at least looking at the github activity here: https://github.com/keepkey/keepkey-firmware

Thanks again for your replies! I've created an issue in the keepkey-firmware github but I don't expect that that's going to happen any time soon. There are a lot of open PR's and there does not seem to be a lot of presence from keepkey staff. I hope I'm wrong, but in the mean time I'll be looking out for other wallets that actually do support BSC.

Actually KeepKey does support BSV at the firmware level. See https://github.com/keepkey/keepkey-firmware/blob/master/include/keepkey/firmware/coins.def#L23

Where's the release log that details the changes for firmware 7.1.0? It's not tagged in github repo and it's also missing from the release section as well: https://github.com/keepkey/keepkey-firmware/releases

If you do get one here are couple things you'll probably have to do before it's functional: - On Mac/Linux you'll probably have to add appropriate udev rules so apps can communicate with KeepKey without sudo. See this - On Windows you may need to install usb driver https://zadig.akeo.ie if it's not picking KeepKey up. Just check device manager after plugging in KeepKey to tell. - You'll have to update the bootloader and firmware. I recently got a second KeepKey and it came loaded with bootloader 1.0.3 and firmware 4.0.0, both of which are quite old. After updating to 1.1.0 and 6.7.0 respectively, haven't had any issues using it. - For Windows on any chrome-based browser you may need to enable chrome://flags/#new-usb-backend. I found the behavior to be less quirky with it on. For example, on shapeshift platform some functions like address display on device and device reset wipe doesn't work unless this is on. The usb user prompt will also show unknown for me instead of keepkey when pairing unless this flag is on.

Note that firmware support is still required for this to work. If Shapeshift official support is important to you I suggest pestering them to merge this PR into their upstream repo.