Bitcoin Keeper

Bitcoin Keeper is now fully community-led. All features are free. • No subscriptions, no paywalls. no lock-ins • Open-source, MIT licensed, as always • Development led by independent contributors • Optional in-app tips to support developers directly Built to last decades, not company lifecycles. Keeper stays independent, open, and in the hands of the community. Read more: medium.com/bitbees/bitcoi…

Wanna try @bitcoinKeeper_ with your Satochip hardware wallet? Check this 5-steps guide that will cover the creation of your next #Bitcoin wallet. satochip.io/setup-use-sato…

Bitcoin Keeper (android,ios) v2.5.9 released by @bitcoinKeeper_ Release notes: github.com/bithyve/bitcoi… Discover and compare the Best Bitcoin Software Wallets. thebitcoinhole.com/software-walle…

🚨 LIVE ANNONCE: Découverte exclusive de TAP2SIGN sur @satochip ! Signer tes tx Bitcoin en UN SIMPLE TAP NFC sur ton phone → ultra fluide, max sécurité (secure element EAL6+), zéro QR galère ! 📅Jeudi 12 Mars: démo live avec @bitcoinKeeper_ -Setup en 5 min -Tx réelle signée en tapant la carte -Tips sécurité NFC 🔗Liens en commentaire 👇 (Et comme d'habitude, 𝐮𝐧𝐞 𝐜𝐚𝐫𝐭𝐞 𝐚̀ 𝐠𝐚𝐠𝐧𝐞𝐫, c'est @satochip qui régale, encore une fois !) #Bitcoin #SelfCustody #Satochip #Tap2Sign #TapToSign #NFC #HardwareWallet #BitcoinFrance #LAB312

Satochip will be at the Brussels #Bitcoin Meetup! 📆 Tomorrow evening 📍 Brussels, of course. At the Dolle Mol café. Telegram: t.me/BrusselsBitcoi… NOSTR: tinyurl.com/BRUSSELS-BITCO…

A NFC hardware wallet - open-source - with a secure element for 25€. Supported by the major #Bitcoin software such as @SparrowWallet or @bitcoinKeeper_ Yes it's possible! satochip.io/product/satoch…

This is more than tech! Mobile NFC signing + hardware secure elements is a big step toward the cypherpunk dream: money you can carry, control, and verify without trust. The future of #Bitcoin self-custody is here with @bitcoinKeeper_ and @satochip

Custody lasts when operators--not vendors--own the policy. Build a signer guild: rotate drill leads, cross-review runbooks, log changes so anyone can rehearse on demand. Community-led custody feels slower day one, but when a portal locks or a signer exits, your circle moves.

@bitcoineaqui Valid concern. We treat the runbook like a key: seed words live in one sealed vault, instructions live elsewhere, both logged and tamper-evident. Heirs practice the process without touching funds. Criminals can’t use what they can’t locate; your family still has clarity.

@bitcoinKeeper_ The problem with writing it down is that it becomes a manual for criminals. If this is going to be done, it needs to be very carefully thought out and kept hidden.

Inheritance planning fails at one hidden point: key context. Your heirs don’t just need seeds—they need wallet policy, signer locations, and the first safe move. Leave a sealed day-one recovery brief. Bitcoin rewards preparation, not assumptions.

Travel custody checklist: 72 hours before a long trip, lock your high-value spending policies, move a small spend key to a travel-only device, and record who holds it. Mobility-friendly Bitcoin custody still keeps the cold quorum cold.

Still true. Single-sig teaches responsibility. Multisig teaches resilience. Before size, run one tiny recovery drill with clear signer roles. That is the difference between confidence and false comfort.

🔐 Create your Bitcoin wallet directly inside your Satochip secure element! Your private keys never leave the smartcard. Full guide using BitcoinKeeper. 👉 Self-custody made simple. youtu.be/Bz8yh0uQn2A?si…

@satochip Exactly this. Secure element + transparent signing UX is the practical bridge between convenience and sovereignty. For real self-custody, the key test is simple: can users verify critical details before they approve?

Thanks for flagging this. Fastest way to isolate it: share device/OS, app version, and the exact first step that fails. Most startup bugs are migration or signer-compat edge cases; reproducible steps get fixes shipped faster. Security-first: avoid large moves until a tiny test send works end-to-end.

@bitcoinKeeper_ Keeper is currently full of bugs. From the startup.

Most wallet mistakes are not technical—they are process mistakes. Today: run a 3-step recovery drill with a tiny amount. Setup, restore, verify. Security is a routine, not a setting.

Great threat model callout. If the coordinator app is compromised, blind signing can still approve bad intent unless policy and verification boundaries are strict. Use independent policy checks, trusted-screen output verification, and signer diversity. Blind signing alone is convenience, not security.

@bitcoinKeeper_ @Lab312_ @satochip humm, the OP link to a video where the smartcard is used as single sig, then from my POV, with the OP scheme, if your threat model assume the app is compromised, dont bother use a blind signer, as it will blindly sign a malicious tx emptying your wallet. Or I miss something?

La Bonne Nouvelle du Lundi. La feature "Tap2Sign" est dispo avec @satochip & @bitcoinKeeper_ Qui veut une démo LIVE 🔴 pendant un live le jeudi? A titre perso, je trouve ça vraiment GAME-CHANGER🔥

Custody is not just key count, it is response time. Create a one-page incident card now: - which signer can move first - who can authorize delay bypass - where verified backups live In a crisis, clarity is your strongest security control.

@pythcoiner @Lab312_ @satochip Great question. Our base threat model: assume phone/app can be compromised, but keys stay on secure element/card and critical actions are verified on trusted hardware. For meaningful funds: separate signer roles + tested recovery flow.

@Lab312_ @satochip @bitcoinKeeper_ c'est quoi le threat model?

Custody upgrade most teams skip: signer provenance log. For each key, record device model, firmware version, setup date, and who verified fingerprints. When something feels off later, you can investigate facts instead of guessing under stress.

Security coach reminder: A custody setup is only real when recovery is rehearsed. Do one monthly drill: - verify one receive address on-device - test one backup restore path - confirm who can act in an emergency

Custody coaching for this week: 1) Run one tiny restore test while calm 2) Verify one receive address independently 3) Keep a plain-English recovery runbook for family Most losses come from process gaps, not market moves.