SecurityKey Factor
Bitkey does not use a discrete secure element. Its signing core is a secure microcontroller from Silicon Labs (EFR32MG24), which generates the Hardware Key on the device and keeps it in the chip's Secure Engine; Block states that the key is never exported in any form. A separate STMicroelectronics STM32U585 drives the screen, and the two processors talk over a mutually authenticated secure channel. Block explains the choice in a blog post: a secure element 'would meet our security criteria' but would prevent it from publishing certain layers of firmware. This is Block's reasoning; we do not treat either approach as better by default.
The only data interface is NFC, which Block says has an effective range of less than an inch. The USB-C port has no data pins and is used only for charging, and there is no Bluetooth or Wi-Fi. Firmware updates arrive over NFC from the app. They are signed by Block, checked at boot and blocked from downgrading, and the app runs an attestation check to confirm the device is genuine. Block states that the screen shows transaction details taken from the transaction itself, so a compromised app cannot change what the device displays.
Unlocking is by fingerprint only; production builds have no PIN. Block publishes no retry limit or wipe policy. In the published firmware source, a failed match re-locks the device and pauses for one second, with no attempt counter and no wipe. Block says it does not collect fingerprint data. The signing code has no anti-exfil (anti-klepto) protocol. Block keeps a public log of fixed security bugs, among them an unreleased PIN feature that could be set over NFC before onboarding (BKS.2026.10.A) and non-cryptographic randomness in Recovery Contact enrollment (BKS.2026.08.D). Block reports no customer funds affected. No independent audit report has been published.



