Bitcoin-Safe (@BitcoinSafeOrg) header
Bitcoin-Safe (@BitcoinSafeOrg) profile picture

Community: https://nitter.cf/t.co/8lqO05EJVl Youtube: https://nitter.cf/t.co/nmctt7Ibjm Github: https://nitter.cf/t.co/Lp5SblwTgp

Bitcoin-Safe.org
Joined November 2024
Photo by Bitcoin-Safe (@BitcoinSafeOrg)Photo by Bitcoin-Safe (@BitcoinSafeOrg)Photo by Bitcoin-Safe (@BitcoinSafeOrg)Photo by Bitcoin-Safe (@BitcoinSafeOrg)Photo by Bitcoin-Safe (@BitcoinSafeOrg)Photo by Bitcoin-Safe (@BitcoinSafeOrg)Photo by Bitcoin-Safe (@BitcoinSafeOrg)Photo by Bitcoin-Safe (@BitcoinSafeOrg)Photo by Bitcoin-Safe (@BitcoinSafeOrg)Photo by Bitcoin-Safe (@BitcoinSafeOrg)
Bitcoin Safe 2.3.0 (Linux AppImage) is reproducible ✅ We built tag 2.3.0 from source with the project's own Docker build. Our file is byte-for-byte identical to the official release. Script, hashes and a recording of the run: walletscrutiny.com/verifier/…
1
1
73
🚀 Successfully reproduced and verified Bitcoin-Safe Desktop v2.3.0 (windows) from source! ✅ The binary tested matches the one built from source. 🔍 See the full verification here: walletscrutiny.com/verifier/…
2
6
179
Absolute full house for @bitschmidty 🔥 He walked through the actual steps Bitcoin Core developers are taking to make Bitcoin better money, and cleared up the myth that Core is busy with things plebs don't care about. Great to see a packed room getting it straight from someone who actually knows what he's talking about.
5
21
164
10,850
Bitcoin-Safe retweeted
感谢Keystone的用户:九神二号 带来了一期完整的 Keystone + @BitcoinSafeOrg 中文实操教程 👍 从钱包创建、QR 连接到离线签名都走了一遍。 想尝试 Bitcoin Safe 的朋友,推荐跟着视频一步步操作。
比特币自托管,其实不一定很复杂。 @BitcoinSafeOrg 的两个特点让我印象很深: 🧙 Wizard 引导式流程,一步一步带你完成自托管 🔒 Compact Block Filters(BIP158),让区块链扫描更加注重隐私。 本期教程演示 Keystone + Bitcoin Safe 的完整使用过程: @BitcoinSafe_CN youtu.be/LkhBhSm2lOU
3
1
4
1,670
Bitcoin Safe Demo - Open source desktop software for managing your cold storage wallets 👀 Via @BitcoinSafeOrg
3
9
1,181
Two features I really like: @BitcoinSafeOrg 🧙 The Wizard guides you step by step through Bitcoin self-custody. 🔒 Compact Block Filters (BIP158) for more private blockchain scanning. Here’s my full tutorial using Bitcoin Safe with Keystone: youtu.be/LkhBhSm2lOU
1
539
比特币自托管,其实不一定很复杂。 @BitcoinSafeOrg 的两个特点让我印象很深: 🧙 Wizard 引导式流程,一步一步带你完成自托管 🔒 Compact Block Filters(BIP158),让区块链扫描更加注重隐私。 本期教程演示 Keystone + Bitcoin Safe 的完整使用过程: @BitcoinSafe_CN youtu.be/LkhBhSm2lOU
1
1
1
5
2,228
Bitcoin-Safe retweeted
Bitcoin interoperability gets a major boost: - Multisig exports for @CasaHODL and @unchained via file or UR/QR - New @BitcoinSafeOrg and @CoconutWallet connections
1
3
1
7
632
Bitcoin-Safe retweeted
Replying to @River
@River missing @BitcoinSafeOrg in the non-custodial wallets section. MultiSig compatible with most of the hardware wallets mentioned above. Fixed
1
4
119
Join us tonight to learn about three of the most important open source Bitcoin tools; 💊 @SeedSigner 💊 #Sparrow @craigraw 💊 @BitcoinSafeOrg Get a full walkthrough on the ultimate sovereign set up with ₽sy𝑓er from 6:30pm. 🎟️ Tickets tinyurl.com/cmhevents ☀️😎🚀
5
2
8
455
Bitcoin-Safe retweeted
Like many, I've barely slept since the Coldcard incident. My mind has been racing on how to stop this from ever happening again. I believe I've come up with a novel wallet design that solves Bitcoin's self-custody trilemma. Live on mainnet. Writeup: lu.ke/self-custody-trilemma
197
252
88
1,559
422,459
Bitcoin-Safe retweeted
Hey @nvk Now that everything has ended, could you please return the @WalletScrutiny domains you hijacked? Like for example WalletScrutiny . org that points to a website of yours, you know.
10
11
2
133
19,740
Bitcoin-Safe retweeted
Ready to try a Multi-Vendor MultiSig? Try Bitcoin-Safe.org setup wizard to guide you through step-by-step. - Multi-Vendor (Hardware signers from different companies) - Includes Receive and Spend test to ensure each signer works #Bitcoin #SelfCustody #Multisig
1
7
1
15
1,417
Bitcoin-Safe retweeted
Hi, @BitcoinSafeOrg! Welcome to btc.rottenwheel.com/wallets/! Pleasure to have you. 🫡
2
5
109
Bitcoin-Safe retweeted
I’m tired of seeing people post misinformation: this code is part of micropython, NOT coldcard. Some microcontrollers don’t have dedicated RNG hardware, so it’s natural to fallback to a PRNG. It’s not a bug, it’s the way it is. The bug in CC’s setup is accidentally using this
who knew about this vunerability looks like @nvk did and pushed the code anyway
25
30
7
137
25,801
NVK is currently deleting old posts from 2020 to try to clean up the history. Screenshot them while you can. They will all be gone soon.
Replying to @zherbert
Wow, he deleted it. Yikes.
64
184
80
1,183
294,317
Regarding the Coldcard entropy bug – many folks are explaining what happened but I wanted to take a minute to explain why it may have happened. It's a disastrous situation and our heart goes out to all the Bitcoiners affected. Here's a timeline of events: On July 28 2020: @FoundationHQ announced our first Passport hardware wallet and noted that we were building on Coldcard firmware which at the time was GPLv3 licensed (FOSS license). On July 30 2020: NVK publicly said he regretted choosing GPL because Coldcard now had a “clone” and that they would change things in future updates. nitter.cf/nvk/status/12888603458… On November 18 2020: Coldcard added its MIT + Commons Clause license, prohibiting commercial products substantially derived from the software. github.com/Coldcard/firmware… On January 8, 2021: Coldcard firmware 3.2.1 formally announced, “License changed from GPL to MIT+CC on files for which the GPL doesn’t apply.” CC is the "Commons Clause" license addendum which is "source available" instead of FOSS. On March 1, 2021: The “First pass w/ libNgU” commit removed the GPL @Trezor-derived crypto libraries and replaced them with libNgU. That same 120-file commit changed seed generation code. libNgU was licensed with a novel “Licensed for Bitcoin Only” license. On March 17, 2021: Version 4.0.0 announced that all crypto and BIP39 code had been replaced and that the “last remaining GPL code” was removed. blog.coinkite.com/version-4.… github.com/Coldcard/firmware… Our best understanding right now is that the entropy bug was collateral damage from this major overhaul of the codebase. To be clear, this overhaul was not solely about licensing. Coldcard also cited technical goals including adopting Bitcoin Core’s libsecp256k1, faster AES and SHA implementations, and reproducible builds. But the timeline establishes two things: (1) Foundation’s launch was the obvious impetus for Coldcard’s licensing change, and (2) removing the remaining GPL code was an explicit goal of the subsequent v4 rewrite. We don't know by how much the licensing pressure affected the scope or timeline of the rewrite. All we can determine is that the entropy bug was introduced inside the same 120-file commit that removed the old GPL code dependencies.
This quoted post is unavailable.
92
168
91
923
238,100
Bitcoiners: @FoundationHQ is auditing our codebase for potential entropy issues but so far everything looks good. Passport uses multiple entropy sources including our custom “avalanche noise source” and we have confirmed that all sources are properly combined to give strong entropy. We also have access to GPT Cyber program and are using it for our analysis. Please reply with any questions.
12
13
6
141
13,615
Bitcoin-Safe retweeted
Foundation has confirmed that all Passport models have always correctly generated seeds with 128 bits of entropy (or 256 bits for 24 word seeds). All Passports are safe and secure. If you have questions or if you need help, please do not hesitate to reach out.
39
60
19
520
77,290
Bitcoin-Safe retweeted
Trezor users: your funds are safe. The recent Coldcard issue is limited to their own custom firmware and how some of their devices generated randomness. Trezor does not share that code. We have always mixed multiple independent sources of randomness together (device hardware + host + secure elements on newer models). We are truly sorry for everyone who has lost bitcoin. Stay safe. Read more on how Trezor generates entropy here: trezor.io/guides/trezor-devi…
214
425
74
3,063
484,654