@BitBox
Swiss-made π¨π Bitcoin hardware wallet for beginners and pros
No relay list published yet.
Recent Notes
Our preliminary review of the phishing mail that was sent out to our newsletter subscribers about an hour ago found that it is very likely that our newsletter provider got compromised.
Multiple other Bitcoin companies got targeted as well, and it appears that we all share the same newsletter provider.
We sent out a phishing warning to all our newsletter subscribers, contacted the provider and reported the phishing domains. Most of the phishing links appear to have been taken down already.
We are still actively investigating this situation and will update you once we know more.
Multiple other Bitcoin companies got targeted as well, and it appears that we all share the same newsletter provider.
We sent out a phishing warning to all our newsletter subscribers, contacted the provider and reported the phishing domains. Most of the phishing links appear to have been taken down already.
We are still actively investigating this situation and will update you once we know more.
312β€οΈ9π2π€2π1π«1π« 1
There is currently a phishing email going around that's pretending to come from us.
Please do not follow the instructions in the email.
We are currently investigating.
Please do not follow the instructions in the email.
We are currently investigating.
2040β€οΈ27π3β€οΈ2π2π±2π§‘2
Can you still trust hardware wallets?
Our co-founder Douglas answered it properly: entropy sources, dice rolls, firmware updates, and the design decisions behind USB and Bluetooth.
Watch it here π
https://www.youtube.com/watch?v=m6XBiIVIB1g&t=44s
Our co-founder Douglas answered it properly: entropy sources, dice rolls, firmware updates, and the design decisions behind USB and Bluetooth.
Watch it here π
https://www.youtube.com/watch?v=m6XBiIVIB1g&t=44s
1β€οΈ3π1π1
Hi.
Every hardware wallet we sell can run the current firmware.
Bye.
Every hardware wallet we sell can run the current firmware.
Bye.
11β€οΈ10π€2π§‘2:corn:1β€1π1
Does that have anything to do with the entropy issue of Coldcard?
No, unrelated. That one was a random number generation problem in another vendor's device. These are issues in our own firmware, found during our internal audits: a bootloader exploit already fixed in July, a memory corruption bug on the Multi edition, and a silent payments implementation issue that could have locked funds at an unintended address. Different code, different companies. (You can read everything in the post)
β€οΈ1
Yes, user interaction was required.
The bootloader issue only works if the attacker first lands a successful phishing attack: the user has to be tricked into installing a fake BitBoxApp carrying manipulated firmware, then unlock the device to go through with it. High technical finesse on the attacker side, plus several deliberate steps on the user side.
It was already fixed in July with the Oeschinen release, firmware 9.26.2.
Nova is not affected, the bootloader versions involved are older than it.
The memory corruption issue we fixed now is a different one. It only applies to a Multi edition device with no wallet set up yet, plugged into a malicious host. Bitcoin-only is not affected, that code isn't in its firmware.
The bootloader issue only works if the attacker first lands a successful phishing attack: the user has to be tricked into installing a fake BitBoxApp carrying manipulated firmware, then unlock the device to go through with it. High technical finesse on the attacker side, plus several deliberate steps on the user side.
It was already fixed in July with the Oeschinen release, firmware 9.26.2.
Nova is not affected, the bootloader versions involved are older than it.
The memory corruption issue we fixed now is a different one. It only applies to a Multi edition device with no wallet set up yet, plugged into a malicious host. Bitcoin-only is not affected, that code isn't in its firmware.
β€οΈ1π«1
We just released the Dixence security update.
During our internal audits, we were able to discover and fix multiple security issues in the BitBox firmware.
We recommend our users to update their BitBoxApp and device firmware through the BitBoxApp settings.
https://blog.bitbox.swiss/en/bitbox-08-2026-dixence-update/
During our internal audits, we were able to discover and fix multiple security issues in the BitBox firmware.
We recommend our users to update their BitBoxApp and device firmware through the BitBoxApp settings.
https://blog.bitbox.swiss/en/bitbox-08-2026-dixence-update/
1232β€οΈ35π3π§‘3π2π2π€2
As a hardware wallet user, one of the best ways to stay secure is to keep your wallet firmware up to date.
With AI models only getting better at finding and fixing bugs, expect regular updates for your hardware wallets in the near future.
https://blog.bitbox.swiss/en/firmware-updates-in-the-age-of-ai-staying-up-to-date-matters-more-than-ever/
With AI models only getting better at finding and fixing bugs, expect regular updates for your hardware wallets in the near future.
https://blog.bitbox.swiss/en/firmware-updates-in-the-age-of-ai-staying-up-to-date-matters-more-than-ever/
53β€οΈ9:0470:1π€1π§‘1
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 askin...
HOW TO INDEPENDENTLY VERIFY THE BITBOX FIRMWARE:
https://blog.bitbox.swiss/en/how-to-independently-verify-the-bitbox02-firmware/
https://blog.bitbox.swiss/en/how-to-independently-verify-the-bitbox02-firmware/
β€οΈ1
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.
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.
611β€οΈ27π€3β€1π1π1π1
