BitBox

Swiss-made 🇨🇭 Bitcoin hardware wallet for beginners and pros

Last Notes

2026-08-04 09:30:00 UTC

If you own a hardware wallet, you probably spent the last few days wondering what you're actually able to check for yourself.
Short answer: more than you'd think.
Here are the questions worth asking any manufacturer (us included):
- Where does the randomness come from?
Every wallet begins as one large random number. If that number is predictable, nothing built on top of it holds.
Ask how many independent sources of entropy the device combines and what happens if one of them turns out to be weak.
- Can I check that the firmware on my device matches the published code?
Reproducible builds let you verify the binary you're running was built from the source you can read.
Worth being precise: that proves the binary matches the source. It does not prove the source is correct.
- Who approves a change before it reaches my device?
Ask whether one person can ship firmware alone, or whether every change needs a second set of eyes.
This is unglamorous and it is where most of the real security lives.
- What happens when they find a bug?
Every manufacturer ships bugs. The question is what the process looks like afterwards.
Ask about the bug bounty. Ask how quickly users were told the last time something was found.
OUR ANSWERS
- The BitBox generates your wallet from five independent sources of entropy: Physical noise from the secure chip, physical noise from the MCU, randomness provided by the host device, a static random number set in the factory and your own device password.
The benefit of mixing entropy: Redundancy. All but one source can be compromised and your seed would still be secure.
- The BitBox firmware supports reproducible builds you can independently verify yourself (link in the comments)
That way you know the firmware you install matches the public source code.
However, it is generally very difficult to verify what code is actually executed on-device.
- All change requests to the BitBox firmware require an approved review by a maintainer to be merged.
- The BitBoxApp and BitBox firmware are fully open-source and part of our bug bounty program (link in the comments )
Bug reports are financially rewarded depending on their severity, encouraging security researchers to actually take a thorough look.
- We announce security updates publically on our channels, including detailed information on the vulnerability and how it might have affected users.

2026-02-24 11:12:55 UTC

- reply

https://bitbox.swiss/

2025-08-14 14:52:04 UTC

Why manage 5 backups when one seed gives you everything?
With BIP-85, your BitBox backup becomes the master key to your entire digital life. Smarter self-custody starts here:
https://blog.bitbox.swiss/en/using-bip-85-child-keys-with-the-bitbox/

2025-05-08 16:35:36 UTC

Storing data on the blockchain: How does OP_RETURN actually work?
A clear and balanced explainer on the recent debate around OP_RETURN limits, arbitrary data on Bitcoin, and what it means for node operators.
https://blog.bitbox.swiss/en/storing-data-on-the-blockchain-how-does-op-return-actually-work/