# KeyOS version 1.4.0-beta1, now available for testing! **URL:** \ **Category:** Beta Testing\ **Created:** [August 16, 2026, 7:25pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200 "2026-08-16T19:25:09Z")\ **Posts on this page:** 20\ **Page:** 1
**Author:** ![Amy](https://community.foundation.xyz/letter_avatar_proxy/v4/letter/a/4da419/32.png) [@Amy](https://community.foundation.xyz/u/Amy)\ **Post date:** [August 16, 2026, 7:25pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/1 "2026-08-16T19:25:09Z")
![636261054-b7f99488-f1d9-4746-99b9-b0a920138ced](https://community.foundation.xyz/uploads/default/original/1X/366a8dae4d03261b6b7f15363c136eb3d4095d81.jpeg) ## ⚠ THIS IS A BETA RELEASE. **KeyOS v1.4.0-beta1 is a pre-release build for testing.** It is intended for users who are comfortable flashing firmware through recovery mode and are happy to help us test. If you’d rather wait for the stable release, no action is needed, the official KeyOS v1.4.0 release will follow. **Before you begin:** as with any firmware update, and especially a beta, please make sure your backup is current before installing. **Important:** in order to upgrade from this beta to the official KeyOS v1.4.0 release, you will have to follow the same recovery steps again with the v1.4.0 recovery file. ### WHAT’S CHANGED KeyOS 1.4.0-beta1 is a major release for Passport Prime, headlined by a fully redesigned launcher. It also introduces multisig exports for Unchained and Casa, connections for Bitcoin Safe and Coconut Wallet, imports from Aegis and Proton Authenticator, and extensive security improvements across Bitcoin signing, multisig validation, apps and storage. ### NEW FEATURES - The launcher has been fully redesigned, with brand-new app icons, an overhauled light-pattern background and icon dock, customizable app icon placements, and a smoother unlocking animation - You can now sideload third-party apps directly from Settings \> Apps with a new install button. This feature is available in the new Apps menu and is backed by an “Allowed Publishers” model that puts trust decisions in your hands. In addition, you can pick and choose the permissions for sensitive operations for these apps. - You can now export multisig wallet configurations for Unchained and Casa from the Bitcoin app, using both file and UR/QR formats - Bitcoin Safe and Coconut Wallet connections added to the Bitcoin app - You can now import existing TOTP accounts from Aegis or Proton Authenticator by QR code or file, including password-protected encrypted exports - You now have to enter your PIN before Passport Prime shows your seed words, adding an extra safety step to the seed reveal flow There’s a lot more in this one, every improvement and bug fix is listed in the full release notes on [GitHub](https://github.com/Foundation-Devices/KeyOS-Releases/releases/tag/1.4.0-beta1). ## **📥 HOW TO UPDATE, read carefully, this beta installs through recovery mode** > **You will need:** the beta file and an external drive, a microSD card or USB flash drive. If your drive is microSD or USB-A, you will also need a USB-C adapter. 1. **Download `KeyOS-v1.4.0-beta1-Recovery.bin`** to an external drive (microSD card or flash drive) — This can be found on the release notes linked above. 2. **Turn on your Passport Prime** 3. **While the Foundation logo is being displayed during boot, tap the power button repeatedly** — this should bring you to the Boot Menu 4. **Select “Recovery”** — this will bring you to the Firmware Recovery menu 5. **Tap Firmware Recovery** 6. **Connect the external drive to the USB-C port on Passport Prime** (you will need a USB-C adapter if you saved to a microSD card or USB-A drive in step 1) 7. **Select `KeyOS-v1.4.0-beta1-Recovery.bin`** saved during step 1 > **⚠ Note: in order to upgrade to the official KeyOS 1.4.0 release, you will have to follow the same steps again with the 1.4.0 recovery file.** Found a bug, or something that doesn’t feel right? Please reply in this thread, that’s exactly what this beta period is for. Thank you for testing! 🖤 ---
**Author:** ![zherbert](https://community.foundation.xyz/user_avatar/community.foundation.xyz/zherbert/32/76_2.png) [@zherbert](https://community.foundation.xyz/u/zherbert)\ **Post date:** [August 16, 2026, 8:24pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/2 "2026-08-16T20:24:46Z")
This is our most important release yet. Let us know what you think! ---
**Author:** ![Ke\_James](https://community.foundation.xyz/user_avatar/community.foundation.xyz/ke_james/32/624_2.png) [@Ke\_James](https://community.foundation.xyz/u/Ke_James)\ **Post date:** [August 16, 2026, 9:39pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/3 "2026-08-16T21:39:12Z")
Does KeyOS 1.4.0 allow Passport Prime to fully back up and restore the device without using Envoy, for example using only Prime + Keycards + microSD? ---
**Author:** ![salvador](https://community.foundation.xyz/letter_avatar_proxy/v4/letter/s/4da419/32.png) [@salvador](https://community.foundation.xyz/u/salvador)\ **Post date:** [August 16, 2026, 11:34pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/4 "2026-08-16T23:34:03Z")
+1 when restore from backup files is out it’s going to be huge for Prime users 💯 ---
**Author:** ![Ke\_James](https://community.foundation.xyz/user_avatar/community.foundation.xyz/ke_james/32/624_2.png) [@Ke\_James](https://community.foundation.xyz/u/Ke_James)\ **Post date:** [August 17, 2026, 1:59am UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/5 "2026-08-17T01:59:35Z")
Passport Prime feels like an increasingly large and complex platform, and in my view it has lost some of the focus and predictability that made Passport Core so appealing. Core is purpose-built, focused, and mature. Prime, by comparison, is trying to do many things at once — Bitcoin signing, authentication, apps, keycards, backups, third-party apps, and more. That ambition is interesting, but complexity inevitably increases the attack surface and makes long-term reliability harder to achieve. My biggest concern, however, is the current dependence on Envoy for important backup and recovery workflows. I think that is a fundamental design mistake. A self-custody device should remain fully sovereign on its own: I should be able to set it up, back it up, wipe it, recover it, and use it indefinitely without depending on a companion phone app or another piece of Foundation software. Envoy can be a useful optional convenience layer, but it should never be a requirement for the device’s core security and recovery functions. For a product built around self-custody and sovereignty, the Prime itself should ultimately be self-sufficient. ---
**Author:** ![qna](https://community.foundation.xyz/user_avatar/community.foundation.xyz/qna/32/284_2.png) [@qna](https://community.foundation.xyz/u/qna)\ **Post date:** [August 17, 2026, 6:32am UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/6 "2026-08-17T06:32:34Z")
Passport Prime hasn’t lost its focus. Passport Prime is a platform. That is the entire point of the product. Passport Core was designed as a focused Bitcoin signing device. Passport Prime was designed to protect far more of a person’s digital life: Bitcoin keys, security credentials, 2FA accounts, encrypted files and, now, applications running with user-controlled permissions. These are not unrelated features being bolted onto a hardware wallet. They are different applications of the same principle: sensitive data and approvals should remain under the user’s control on trusted hardware. More capability does require more engineering and a stronger security architecture. We do not pretend otherwise. That is why KeyOS uses application isolation, explicit permissions, publisher controls and an opt-in Developer Mode. The answer is to build the platform securely, not to turn Passport Prime into another Passport Core. The point about independent backup and recovery is fair. A user can already restore their Bitcoin master key without Foundation holding it, and manual Keycard backups do not require an Envoy-held recovery share. Fully restoring all device settings and application data without Envoy is not yet complete. That is a capability we intend to deliver, not a change in Passport Prime’s direction. It is completely reasonable to prefer a narrow, single-purpose Bitcoin signer. Passport Prime is deliberately not that product. It is a personal security platform that includes an excellent Bitcoin hardware wallet, and KeyOS 1.4 is an important step toward the product Passport Prime was always intended to become. Specific bugs, security concerns and beta feedback are welcome. But the expansion into apps and broader digital security is not scope creep. It is the roadmap. ---
**Author:** ![btcpleb](https://community.foundation.xyz/user_avatar/community.foundation.xyz/btcpleb/32/952_2.png) [@btcpleb](https://community.foundation.xyz/u/btcpleb)\ **Post date:** [August 17, 2026, 12:38pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/7 "2026-08-17T12:38:50Z")
Having an issue with signing transactions. Error message reads “No transaction found. QR code does not contain a valid Bitcoin transaction.” Did not have this issue on previous build. ---
**Author:** ![qna](https://community.foundation.xyz/user_avatar/community.foundation.xyz/qna/32/284_2.png) [@qna](https://community.foundation.xyz/u/qna)\ **Post date:** [August 17, 2026, 1:16pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/8 "2026-08-17T13:16:32Z")
Which wallet software are you trying to sign with? ---
**Author:** ![btcpleb](https://community.foundation.xyz/user_avatar/community.foundation.xyz/btcpleb/32/952_2.png) [@btcpleb](https://community.foundation.xyz/u/btcpleb)\ **Post date:** [August 17, 2026, 1:26pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/9 "2026-08-17T13:26:55Z")
I am using sparrow wallet ---
**Author:** ![qna](https://community.foundation.xyz/user_avatar/community.foundation.xyz/qna/32/284_2.png) [@qna](https://community.foundation.xyz/u/qna)\ **Post date:** [August 17, 2026, 1:34pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/10 "2026-08-17T13:34:09Z")
My guess is the Sparrow QR display is set to BBQr instead of UR. Please set to UR and confirm it fixed your issue. ---
**Author:** ![btcpleb](https://community.foundation.xyz/user_avatar/community.foundation.xyz/btcpleb/32/952_2.png) [@btcpleb](https://community.foundation.xyz/u/btcpleb)\ **Post date:** [August 17, 2026, 1:43pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/11 "2026-08-17T13:43:39Z")
![IMG_1395](https://community.foundation.xyz/uploads/default/original/1X/e9b13c88ac6ae4a1469815d587e667de0f1804e3.jpeg) still giving issue. device has never been backed up to envoy. its also displaying an error with bitcoin price chart. ---
**Author:** ![btcpleb](https://community.foundation.xyz/user_avatar/community.foundation.xyz/btcpleb/32/952_2.png) [@btcpleb](https://community.foundation.xyz/u/btcpleb)\ **Post date:** [August 17, 2026, 1:49pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/12 "2026-08-17T13:49:11Z")
![IMG_1396](https://community.foundation.xyz/uploads/default/original/1X/ecff04a08008d12404ca044fed75594b29cb51e2.jpeg) gives this issue when connected using bluetooth as well. ---
**Author:** ![btcpleb](https://community.foundation.xyz/user_avatar/community.foundation.xyz/btcpleb/32/952_2.png) [@btcpleb](https://community.foundation.xyz/u/btcpleb)\ **Post date:** [August 17, 2026, 1:50pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/13 "2026-08-17T13:50:04Z")
would you suggest reverting back to previous build? ---
**Author:** ![qna](https://community.foundation.xyz/user_avatar/community.foundation.xyz/qna/32/284_2.png) [@qna](https://community.foundation.xyz/u/qna)\ **Post date:** [August 17, 2026, 2:18pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/14 "2026-08-17T14:18:17Z")
Thanks, we are investigating the issue. For now you will not be able to downgrade to an older firmware version. ---
**Author:** ![Scriptshaman\_Ji](https://community.foundation.xyz/user_avatar/community.foundation.xyz/scriptshaman_ji/32/958_2.png) [@Scriptshaman\_Ji](https://community.foundation.xyz/u/Scriptshaman_Ji)\ **Post date:** [August 18, 2026, 12:14am UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/15 "2026-08-18T00:14:39Z")
> [@Amy](#): > > KeyOS-v1.4.0-beta1-Recovery.bin Where do you download this from? ---
**Author:** ![qna](https://community.foundation.xyz/user_avatar/community.foundation.xyz/qna/32/284_2.png) [@qna](https://community.foundation.xyz/u/qna)\ **Post date:** [August 18, 2026, 5:41am UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/16 "2026-08-18T05:41:50Z")
It is linked in the first post [Release 1.4.0-beta1 · Foundation-Devices/KeyOS-Releases · GitHub](https://github.com/Foundation-Devices/KeyOS-Releases/releases/tag/1.4.0-beta1) ---
**Author:** ![exitus1](https://community.foundation.xyz/user_avatar/community.foundation.xyz/exitus1/32/876_2.png) [@exitus1](https://community.foundation.xyz/u/exitus1)\ **Post date:** [August 21, 2026, 7:39pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/17 "2026-08-21T19:39:30Z")
Hi, Quick question about sideloaded app permissions on 1.4.0-beta1 / SDK 1.0.0. I’ve got an open-source Decred signing app installed and running on a dev unit — the sideload flow (cert gen, Allowed Publishers, build/pack, Install App) all worked smoothly. The blocker: the app needs GetSeed to derive keys. I declare “os/security” = [“GetSeed”, …] in app-config.toml, and it’s present in the signed manifest, but the kernel returns xous(AccessDenied) at runtime. There’s no seed/security entry under Settings \> Apps \> Permissions to grant, and permission\_templates.toml ships only fs-generic, gui-app, and navigable — none covering os/security. Is seed access intended to be available to sideloaded apps in this release, or is it gated to built-in apps for now? And if it’s planned, is there an interim path for dev units? Since offline signing is a headline use case in the docs, I suspect I’m not the only one who’ll run into this. Happy to share the repo or test anything on the unit. Thanks. ---
**Author:** ![qna](https://community.foundation.xyz/user_avatar/community.foundation.xyz/qna/32/284_2.png) [@qna](https://community.foundation.xyz/u/qna)\ **Post date:** [August 22, 2026, 5:27am UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/18 "2026-08-22T05:27:01Z")
Hi, Thanks for testing this. The behaviour is intentional, although we need to make it clearer in the SDK documentation. `GetSeed` returns Passport Prime’s master seed and is restricted to Foundation-signed system apps. It cannot be granted to a sideloaded app, including on a dev unit, so the `AccessDenied` response is expected. For a third-party signing app, use: ```auto "os/security" = ["GetAppSeed"] ``` and call `Security::app_seed()`. This returns a deterministic 32-byte seed derived specifically for your app and bound to its `appId`. It lets the app derive and use its own signing keys while preventing it from reading Passport Prime’s master seed or the keys belonging to another app. Access is user-approved on first use. The entries in `permission_templates.toml` are convenience bundles rather than the complete set of available permissions, so `GetAppSeed` can be declared directly. There is no supported route for a sideloaded app to obtain `GetSeed`. If `GetAppSeed` still returns `AccessDenied` or does not produce the approval prompt, please let us know, as that would be a separate beta issue. Thanks for building and testing this. ---
**Author:** ![Mason.99999](https://community.foundation.xyz/user_avatar/community.foundation.xyz/mason.99999/32/730_2.png) [@Mason.99999](https://community.foundation.xyz/u/Mason.99999)\ **Post date:** [August 22, 2026, 3:20pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/19 "2026-08-22T15:20:44Z")
This makes sense and glad to hear it’s deterministic. Is the process of derivation from prime seed and app ID published? Want to make sure it can be recreated without prime if needed. ---
**Author:** ![qna](https://community.foundation.xyz/user_avatar/community.foundation.xyz/qna/32/284_2.png) [@qna](https://community.foundation.xyz/u/qna)\ **Post date:** [August 22, 2026, 3:52pm UTC](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200/20 "2026-08-22T15:52:45Z")
Yes. The current derivation is published in the open-source KeyOS code: `app seed = HMAC-SHA256(key: appId, data: Master Key entropy)` The `appId` is the 16-byte value in the app’s manifest. The Master Key entropy is the raw 16 or 32 bytes represented by the user’s 12 or 24 BIP39 words, not the separate 64-byte BIP39 seed produced using PBKDF2. This produces the same deterministic 32-byte app seed every time. Therefore, a developer can build an offline recovery tool that recreates it from the user’s seed words and the original `appId`, without needing Passport Prime. The `appId` must remain stable across app versions. Changing it intentionally produces a different app seed. The implementation is already public in [KeyOS](https://github.com/Foundation-Devices/KeyOS/blob/v1.3.1/os/security/src/atsama5d2.rs#L1001), but this recovery formula should also be documented explicitly in the SDK so developers do not have to infer it from the OS source. [Next page](https://community.foundation.xyz/t/keyos-version-1-4-0-beta1-now-available-for-testing/1200.md?page=2)