Free, open-source Bitcoin self-custody. Multisig, inheritance & recovery. Community-run, supported by grants and tips.

Cyberspace
Joined April 2022
📢Help shape what Keeper builds next. Users, partners and contributors already help improve Keeper. We’re bringing more of that work onto X: requests, progress and the decisions behind them. What’s one thing you’d change? Reply below. 1/3
3
2
1
9
1,567
A BIP39 passphrase isn't a device PIN. With the same seed, changing even one character derives a different wallet. Back up the exact passphrase securely, separately from the seed, and test access before funding. trezor.io/guides/backups-rec…
195
Bitcoin Keeper is free, open source and community-run. Independent contributors maintain it; voluntary tips and grants fund development, maintenance and security work. If Keeper helps you, consider supporting it: Settings → Support the Developers. bitcoinkeeper.app/
1
4
497
Bitcoin Keeper retweeted
Replying to @bitcoinKeeper_
Fault tolerance beats vendor loyalty.
1
1
102
It always was the most tolerant solution.
Multi-vendor Multisig is not optional. It is MANDATORY for self custody.
1
1
1
4
707
good comparison table by @bluewalletio 👏 may be add additional entropy (dice or coin) to one of your multis keys and use an app that offers a decoy wallet and you get all ✅
What no one is telling you. Save it for later. - Is BlueWallet safe? What each setup protects you from bluewallet.io/is-bluewallet-…
1
1
17
1,863
Bitcoin Keeper retweeted
You should. Community-run, fully open source, full of features, easy to use. Bitcoin only.
1
2
182
A PSBT (partially signed bitcoin transaction) lets separate signers approve the same spend without bringing their private keys together. Keeper collects the required signatures before broadcasting. Check the destination and amount before signing.
1
2
5
490
Yes! When miniscript in Trezor @tsusanka, @Dantoshi, @Lahannin, @JanBed00, @matej_zak and @slush? We would love if @Trezor supported miniscript and worked with @lianabitcoin, @nunchuk_io, @bitcoinKeeper_ and @AnchorWatch. copy @KLoaec, @hugomofn, @anant_tap, @Rob1Ham
1
1
6
547
Bitcoin Keeper retweeted
Ledger is investigating reports of loss of funds from users in South East Asia who purchased products from a reseller named CryptoBillis. As a precaution, and pending the results of our investigation, we have asked CryptoBilis to pause all sales and shipments of Ledger devices. We recommend Ledger users who purchased from this reseller in the last 90 days to not initiate set up if you have not done so yet. If you have set up your Ledger device, consider moving assets to a new Ledger signer (with new seed). We will continue to inform customers of updates as the investigation progresses. Reach out to Ledger customer support through official channels with any questions: support.ledger.com/
1,159
1,745
1,850
7,263
4,685,484
Bitcoin Keeper retweeted
Multi-vendor multisig.
25
26
18
402
29,141
“It is NOT an upgrade for a casual investor to go from an ETF to a single-sig. It's a downgrade.” @anant_tap tears apart conventional self-custody advice and builds it back from first principles. In this completely UNFILTERED episode, we discuss: • The Coldcard hack • Entropy generation • Single-sig vs multi-sig • (and a lot more you’re not ready for) 🕑 TIMESTAMPS 0:00 - Trailer 2:05 - Intro 4:02 - What happened to Coldcard? 6:08 - Can you trust any wallet to generate your seed? 9:30 - How Bitcoin multisig works 18:06 - Dice rolls & coin tosses 22:52 - Can you reuse an old Coldcard? 25:11 - Is cold storage overrated? 26:01 - The trade-offs of self-custody 27:39 - Persona 1: The Investor 34:33 - When is self-custody a downgrade? 36:54 - Persona 2: The HODLer 39:49 - Bitcoin inheritance: access vs ownership 47:36 - Persona 3: The Whale 49:43 - Collaborative custody 53:53 - Lightning round 55:22 - Closing remarks Links 🎧👇
3
1
2
13
1,361
1/2 At Bitcoin Keeper, we already follow good bitcoin wallet practices. Fresh receiving addresses are generated automatically, and change from transactions goes to new addresses. This is standard bitcoin wallet behaviour, not something that requires an emergency migration.
Today I call upon the blockchain industry to calmly begin planning for "bunker mode". My personal recommendation is to set in motion a controlled mass migration of assets to fresh addresses, i.e. addresses whose pubkeys remain hidden behind a hash. Holders, starting with large and sophisticated ones, should consider moving the bulk of their funds to addresses that have never signed a transaction. And when they do sign one, they should also move remaining funds to a new address (possibly generated from the same seed phrase). Don't rush. While I believe there is cause for action a rushed migration would do more harm than good. Don't panic either. Moving assets to protected addresses is a simple, preventative step which does not require new cryptography or new wallets. IMO it is now reasonable to brace for the possibility that ECDSA breaks before qday, in the worst case in months not years. By "break" I mean fast private key recovery (e.g. in one week) on available hardware (e.g. a large GPU cluster). Recent days have been humbling for human mathematical intuition. Long-held, unquestioned hypotheses have fallen. This includes the n log(n) bound for integer multiplication and the 3SUM conjecture. In hindsight, May's unexpected disproof of the Erdős unit distance conjecture was our warning shot. Yesterday's OpenAI drop made it clear that mathematical superintelligence is upon us. They say there are weeks where decades happen. We are about to live through weeks where centuries of mathematical progress happen. Could our magic 64-byte ECDSA signatures be too good to be true? Was it just security through obscurity all this time? Elliptic curves feel especially vulnerable to superintelligence. Curves carry rich structure, with room for fancy tricks like Schoof, Frobenius, pairings. (By contrast, hashes are designed to minimise algebraic structure.) Separately, as Ewin Tang can attest, an efficient quantum algorithm sometimes foreshadows an efficient classical one. We should be open to the possibility of a classical counterpart to Shor that breaks elliptic curves and RSA at once. Also noteworthy is the striking under-representation of cryptographic breakthroughs among the 722 mathematical results OpenAI published. I've witnessed first-hand the US government censoring academic quantum cryptanalysis results. Backroom interventionism is my base case. I urge large, sophisticated actors to lead by example. Project11's "risq list" (bitcoin-risq-list.projecteleven[.]com) is a great tracker of exposed BTC pubkeys. Binance, Bitbank, Robinhood, Bitfinex, and Tether have an opportunity to harden their cold storage. Next month I'll address institutions in London in a live Q&A (forum.ethereuminstitutional[.]org/london-2026). Again, please do not rush. Wallets holding under 50 BTC enjoy partial cover from "Satoshi's shield", i.e. his 20K exposed addresses that hold 50 BTC each. Load-bearing signers like oracles and L2 security councils should consider rotating ECDSA pubkeys with every signed message and/or multi-signing with a hash-based schemes like SPHINCS. Exiting bunker mode safely will require post-AI cryptography. My inclination is to go all-in on hash-based cryptography and avoid structured mathematical assumptions entirely, whether from curves, lattices, or isogenies. A single battle-tested hash (e.g. from the SHA or BLAKE families) yields plausible post-AI security. The Ethereum roadmap on strawmap[.]org fully embraces hash-based cryptography with end-to-end formal verification as a response to the quantum threat. Those timelines must now be revisited and accelerated in light of mathematical superintelligence. I'll be pushing for maximum defensive acceleration.
2
1
4
645
2/2 Keeping public keys unexposed until spending is a useful precaution, but it isn’t a new discovery or a complete defence. There is no demonstrated classical attack that can recover bitcoin private keys in days or weeks. We take emerging threats seriously. But security decisions should be based on evidence, not speculative timelines.
3
206
Stored keys need periodic access checks. Put one on your calendar: can you still access each signer? Keeper includes a Key Health Check for this. Don’t wait until a spend is urgent. bitcoinkeeper.app/features/
1
1
284
Bitcoin Keeper retweeted
Replying to @vicariousdrama
👻
1
8
225
Your bitcoin security shouldn’t be an upsell. Multisig. Inheritance. Recovery. Privacy. All free. No subscriptions. Bitcoin Keeper is open-source and community-run. Use it. Improve it. Help keep it going. bitcoinkeeper.app
🤖 Made with AI
2
1
10
786
Do you know where your Keeper Recovery Key is? Those 12 words help you restore Keeper if you lose your phone. Keep them somewhere safe. Never share your Recovery Key. Keeper will never ask for it.
4
407
Bitcoin Keeper📱 2.6.2 is live. This update gets you into the app faster 💨 after unlocking and improves reliability when changing wallet keys 🔑 Update on the App Store, Google Play, or download the signed Android APK.
1
5
368