This article explains the current open source status of the firmware that runs on OneKey Pro 2 and OneKey Neo, and what you can expect next.
Current status
The OneKey Pro 2 and OneKey Neo run safeOS 2, our own firmware system for these devices. safeOS 2 is not open source yet.
We are still working through the remaining steps on our side: finalizing the licensing terms for the code we publish, and preparing the codebase and its documentation for release. These steps are in progress, and we will open source the safeOS 2 code once they are complete.
We are not announcing a release date in this article. When the release is ready, we will announce it through our official channels and update this article.
What is already open source
Openness has been part of how we build OneKey for a long time, and a large part of our code is already public:
For earlier generations of OneKey devices, the firmware source code and release builds are published on our GitHub organization (github.com/OneKeyHQ).
OneKey App packages can be verified with GPG signatures, so you can confirm that an installer is the one we published.
For devices whose firmware is already public, you can compare the firmware running on your device with the source code and checksum published on GitHub.
See the related articles at the end of this page for the step-by-step verification guides.
What "not open source yet" means for your security
Not having the source code published yet does not mean the device is unverified or unprotected:
Every OneKey device ships with a secure element that is provisioned at the factory, and firmware must carry a valid OneKey signature before the device will run it. A device flashed with unofficial firmware shows a warning at startup.
Firmware updates are signature-checked during the upgrade process. OneKey App verifies the new firmware before it is installed, and warns you if anything does not match.
Your private keys are generated and stored inside the device, in an offline environment, and are never exposed to the computer or phone it is connected to.
You can still confirm that your device is genuine with the Genuine Check in OneKey App, and confirm the firmware version and checksum on the device itself under System Settings → About Device.
In short: the security model of OneKey Pro 2 and OneKey Neo does not depend on the source code being public. Publishing the code adds independent review on top of that, and that is exactly why we are doing it.
Why the release takes time
Opening up a firmware codebase is not only a matter of pushing a repository public. Before release we need to:
Settle the licensing terms that will apply to the published code, so that what we publish is clear and usable.
Review the code and its third-party components, and remove anything we are not able to publish.
Prepare build instructions and documentation, so that what we publish can actually be reproduced and reviewed.
We would rather publish once, properly, than publish something incomplete.
Questions
If you have a question about the open source status of safeOS 2, or about firmware verification for your device, contact OneKey Customer Support. We will keep this article updated as the release progresses.
Related articles
