works @BitBoxSwiss / BitBox02, #bitcoin

Joined July 2018
benma retweeted
Today, we're publishing BIP SHRINCS, the first concrete proposal for a post-quantum signature scheme designed specifically for Bitcoin. The BIP draft turns what began as a rough idea into exact algorithms with an executable reference implementation. This is an important milestone: the discussion can now focus on analyzing, criticizing, and improving a concrete proposal. The BIP makes choices ranging from major design questions, such as whether to support flexible XMSS and how to balance signature size against verification time, to the many smaller decisions involved in saving a byte here or there. All of these choices are up for debate. Big thanks to Mike Casey, @conduition, @Ethan_Heilman, @kudinov_mikhail, @olkurbatov, Boris Nagaev, and @remix7531 for their contributions to the BIP. A lot more work lies ahead: - The draft BIP specifies only the cryptography. Using SHRINCS in Bitcoin Script will require a separate BIP. - We are working on a security proof for the exact construction and parameters. - Wallet integration and user experience, for example around backups and recovery after state loss, are still at an early stage. The design space remains wide open. SHRINCS is not intended to be Bitcoin's "final" signature scheme, and it is not optimal along every axis. I do think it is a very good trade-off among the options we have now. bitcoin-dev post: groups.google.com/g/bitcoind… Draft BIP: github.com/SHRINCS/shrincs-b…
40
146
34
554
129,557
benma retweeted
Reflections upon the past year of the BIP-110 movement, similarities I noted to the 2017 scaling debates, and numerous receipts to hold folks accountable for their mistakes. blog.lopp.net/bip-110-post-m…
37
44
13
268
69,736
benma retweeted
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. blog.bitbox.swiss/en/bitbox-…
88
239
123
820
469,106
Replying to @peterktodd
We also are interested in such a spec and and have some early drafts. Should we cooperate to write a BIP? @lianabitcoin @nunchuk_io @umbrel @ElectrumWallet
446
benma retweeted
This round of Bitcoin Whitepaper booklet sales proceeds go to the Bitcoin Red Team! This cypherpunk group uses frontier AI to responsibly disclose vulnerabilities across Bitcoin projects, their tireless work hardens the ecosystem and makes Bitcoin more secure.
12
36
1
440
19,546
This is important.
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. blog.bitbox.swiss/en/firmwar…
1
8
762
.@CasaHODL when will you add support for BitBox? Please reach out.
1
3
11
1,690
.@AnchorWatch when will you add BitBox to the list of supported HWWs? Are your services available in Switzerland?
2
6
661
Hey @kloaec, you’ve done a great job helping people over the past few days, but can you put on your CEO hat for ONE SINGLE post? You spent 4 years of your life on Liana, which is literally designed to mitigate risks like this, and many people don’t even realize that. So please, please do one shill post before going back to helping people in the short term. My equity thanks you, and so do future Liana users who can rest easy the next time around.
Next time around the bug may be at a different place. The one mixing up the entropy from dice for instance: "but dice" is not the right takeaway from this. Trusting a single point of failure with all your money is just extremely risky.
9
24
4
181
60,233
Don't forget to move the funds in your wallets which are backed by BIP-85 seeds derived from Coldcard.
3
14
1,104
Correction, any such multisig account is affected. Address reuse not necessary. xitter.cf/KLoaec/status/20830071…
Multisig accounts where affected coldcards make up the signing threshold (e.g. 2-of-3 are affected coldcards) are also potentially vulnerable for addresses that were reused (or where the descriptor is known). I recommend moving these funds too in abundance of caution.
1
1
1
7
1,724
Multisig accounts where affected coldcards make up the signing threshold (e.g. 2-of-3 are affected coldcards) are also potentially vulnerable for addresses that were reused (or where the descriptor is known). I recommend moving these funds too in abundance of caution.
2
2
20
3,714
It sounds like Mk4, Q, and Mk5 are also vulnerable in a different way than Mk3. Slightly less problematic than Mk3 but still not great to keep using. If you're using single sig Coldcard at the moment you should move your assets to a different wallet (multisig, exchange, other HWW) to be safe.
16
33
3
169
21,597
Confirmed. Mk2/3 vuln, I don't think mk4 is but can't be certain
39
86
57
533
349,651
If you have bitcoin residing under a single key that was generated on a Coldcard Mk3 between 2021-2023, and you - did not incorporate dice rolls - do not use a passphrase - do not use multi-sig I would advise moving funds as soon as possible.
124
396
94
1,662
507,815
Potential very high risk for funds theft for some ColdCard wallets out there. Might be prudent to move remaining funds ASAP.
My current hypothesis for the Coldcard theft. 1- The issue: - Low entropy RNG, either in a library or secure element/chip itself. Could be a limited batch or a specific firmware. - Probably affecting the mnemonic, even if the theft is weird/confusing. - Thief knows about the RNG bug, but not about Bitcoin. 2- The attack - Attacker asked an AI to craft a script to bruteforce and prepare a sweep. - AI ONLY TRIED bip84 derivation paths - AI ONLY TRIED A LIMITED NUMBER OF DEPTH This is why we only see Segwit being stolen, and sometimes partial wallets instead of full wallets. If i am correct: - The funds of partially affected wallets ARE AT RISK or further drain - The funds of other type of addresses ARE AT RISK when the scan looks for them too. If I am wrong: - WHY only bip 84? - WHY partial sweeps? Could be some very rare bug happening in very specific cases, but looking at the chain it's hard to guess what it could be. Some weird derivation bug happening only in CC, at bip 84 paths?
8
11
1
109
15,402
BULL Wallet now supports @BitBoxSwiss on both Android and iOS! Connect your BitBox via USB on Android, or pair your BitBox02 Nova over encrypted Bluetooth on iOS. Verify receiving addresses on your BitBox and securely sign Bitcoin transactions. Open-source firmware. 100% self-custody. No compromises. Download BULL ↓
9
25
4
84
29,747
Replying to @Arvolear
Agreed In particular it's great as a backup for the spending scripts for other outputs of the same transaction
7
1
9
673
benma retweeted
The Oeschinen update is live. Hardened firmware and a stronger app, because good security is never finished. 💪 You can download and install the update now. Full details on our blog: blog.bitbox.swiss/en/bitbox-…
2
7
33
3,427