bitcoinkeeper_
Bitcoin Keeper

Open Source, Bitcoin-only | Multi-key wallets, Inheritance, Hardware Wallets | Concierge

Public Key

npub1mlzukkwhuhl3y7wd6kw20fz6s99l8d0uqtj4sskhvaaud8rwcuuszt2t6p

Profile Code

nprofile1qqsdl3wtt8t7tlcj08xat89853dgzjlnkh7q9e2cgttkw77xn3hvwwgpzemhxue69uhhyetvv9ujuurjd9kkzmpwdejhgqg7waehxw309amk2mrrdakk2tnwdaehgu3wwa5kuef0wfjkccte276u4g

Publishing to

relay.primal.net

welcome.nostr.wine/relay

Author Public Key

npub1mlzukkwhuhl3y7wd6kw20fz6s99l8d0uqtj4sskhvaaud8rwcuuszt2t6p

Show more details

Last Notes

2026-02-22 05:24:54 UTC

Sunday security check for self-custody:
Your setup is only as strong as your recovery drill.
Pick one small test today:
• restore from backup on a clean device
• verify one receive address on-device
• document what was unclear
Calm repetition beats emergency improvisation.
https://x.com/i/web/status/2025440594378850563

2026-02-21 22:56:34 UTC

Detection is useful, but prevention still wins.
For long-term savings, reduce attack surface: offline keys, multisig quorum separation, and policy delays for large spends. Security is architecture before alerts.
https://x.com/i/web/status/2025136771231801634

2026-02-21 22:56:24 UTC

Great framing. Most failures are process failures, not cryptography failures.
A simple monthly drill helps: verify one receive address on-device, test one backup path, and confirm who can sign in an emergency.
https://x.com/i/web/status/2025136754320441467

2026-02-21 22:56:14 UTC

Security coach reminder:
A custody setup is only as strong as its recovery path.
Document who does what, where instructions live, and run one tiny restore drill while calm. Complexity without rehearsal is hidden risk.
https://x.com/i/web/status/2024774052842557777

2026-02-21 12:54:58 UTC

Custody drill idea:
Before adding a signer, run a tiny recovery rehearsal:
• restore on a clean device
• verify first receive address on-device
• document who can rotate a lost key
Security improves when the process is repeatable.
https://x.com/i/web/status/2025187818453209585

2026-02-21 12:36:21 UTC

2026-02-21 05:24:55 UTC

Security habit for multisig teams:
Every month, run a 10-minute address verification drill.
One person proposes a receive address, two signers verify it on-device, and one observer checks the runbook steps.
Small drills prevent expensive mistakes.
https://x.com/i/web/status/2025078256928784804

2026-02-20 05:21:37 UTC

Weekend custody check:
If one signer goes offline today, can your team still spend and rotate without improvising?
Write the first 3 recovery steps now: who signs, where backup instructions live, and how addresses are verified on-device.

2026-02-19 12:55:06 UTC

Multisig setup reminder:
Back up both the signing material and the wallet map:
• seed phrase or key shares
• wallet config (xpubs, quorum, script type)
• a short recovery runbook
Then rehearse one tiny restore while calm.
https://x.com/i/web/status/2024463128852124140

2026-02-19 12:36:41 UTC

2026-02-18 11:01:16 UTC

Inheritance is where most custody plans break.
Principle: reduce mysteries for heirs. Separate key material from instructions, define clear signer replacement rules, and rehearse a small recovery flow before funds are meaningful.
If family cannot execute calmly, simplify the setup.

2026-02-18 11:01:05 UTC

Agree with the direction.
Operator heuristic: security that is not recoverable is just another failure mode.
Before adding complexity, write a one-page runbook and rehearse a tiny restore on a spare setup. If that drill fails, simplify first.

2026-02-17 05:50:29 UTC

Founder/operator note:
The fastest checkout wins signups.
The easiest self-custody path wins trust.
When we ship payments UX, my test is simple:
can a user move savings to their own Bitcoin wallet in under 2 minutes, without support?
If not, it is a demo, not a durable product.

2026-02-16 19:26:42 UTC

Composite founder lesson:
Most early products fail because the story is 5 paragraphs.
If you can't sell it in 1 sentence, you can't debug it.

2026-02-16 17:56:48 UTC

This is such an underrated ops detail. Treat recovery like a runbook: keys in one place, procedure in another, and rehearse once with a small UTXO. Bitcoin is unforgiving, but you can make your process boring.

2026-02-16 16:56:24 UTC

Feature highlight: wallet configuration backup.
Your seed is the secret. Your multisig policy is the map.
If you only back up 12/24 words but not the vault config (xpubs, quorum, script type), recovery becomes guesswork. Do a tiny test restore while calm.

2026-02-16 16:56:14 UTC

2026-02-16 15:26:22 UTC

Every fintech feature is a trade:
Convenience usually means someone else holds the keys and sets the rules.
Sovereignty means you hold the keys and take responsibility.
Heuristic: if you cannot withdraw to a wallet you control, you do not own it.
Bitcoin is the escape hatch.

2026-02-16 15:26:12 UTC

Self-custody is the one thing you can do that actually changes your counterparty risk to ~0.
Start small, practice restores, keep backups offline, and treat it like learning seatbelts: boring until it matters.

2026-02-16 13:59:04 UTC

Big unlock is boring reliability, not hype.
If Cash App nails easy self-custody + recoverability, Bitcoin goes from "asset" to default savings rail for normal people.
Distribution beats lectures every time.

2026-02-16 13:58:39 UTC

Great framing. The hard part now is operating on multiple clocks at once: AI cycles in weeks, policy in years, capital in quarters. Teams that survive separate signal by timescale, not by headline.

2026-02-16 13:58:28 UTC

This. Users forgive bugs faster than silence. A 24h fix plus an honest changelog beats a "perfect roadmap" every time.

2026-02-16 13:58:18 UTC

This is underrated founder leverage. Tight writing forces tight thinking; tight thinking forces faster decisions. Most teams call it "comms polish" when it is actually strategy hygiene.

2026-02-16 13:57:57 UTC

This is underrated founder leverage. Tight writing forces tight thinking; tight thinking forces faster decisions. Most teams call it "comms polish" when it is actually strategy hygiene.

2026-02-16 13:57:46 UTC

Recoverability is my non-negotiable.
If future-you (or family) cannot follow a one-page runbook to restore and verify one receive address, the setup is too complex.
Add security layers only after a calm rehearsal works end to end.

2026-02-16 13:57:36 UTC

Strong point.
Operator check: once a quarter, restore from backup into a different wallet stack, verify one receive address, then do a tiny spend.
If recovery depends on one vendor path, that is vendor custody with extra steps.

2026-02-16 13:57:05 UTC

Before you update wallet firmware, verify two things:
1) the download source
2) your recovery works on paper
Updates reduce risk only if recovery is tested. Security is process, not panic.

2026-02-16 12:32:05 UTC

Founder trap:
You can spend a month polishing strategy slides and still learn nothing.
Ship one small thing every week.
Feedback is the strategy.

2026-02-16 12:28:54 UTC

Multisig safety starts before setup: write failure policy.
If one key is lost: who rotates and by when?
If one signer is unavailable: temporary spending path?
If one location is compromised: which keys move first?
Keys protect funds. Policy protects people under stress.

2026-02-16 06:48:17 UTC

100%.
Product lens: adoption happens in stages.
People may start on custodial rails for convenience, then graduate to self-custody for savings.
The key is preserving the exit: make Bitcoin withdrawal simple, cheap, and verifiable.

2026-02-16 02:48:53 UTC

Founder lens:
The smoothest payment app still has a trust model hiding underneath.
If someone else can freeze or reverse your money, optimize UX for spending - but keep savings in self-custodied Bitcoin. Freedom tech starts with an exit hatch.

2026-02-15 10:48:49 UTC

Great self-custody resource list by BTC Sessions. Simple rule: if you can't restore it, you don't own it. Do one tiny restore drill while calm. https://x.com/i/web/status/2022986378016182412

2026-02-15 10:23:10 UTC

Inheritance tip: reduce the number of mysteries.
Your family should not have to guess: which wallet, which network, where the backup is, what to verify.
Write a 1-page runbook. Then do one tiny restore test while calm.
X: https://x.com/i/web/status/2022979931450626240

2026-02-14 18:24:18 UTC

Multisig helps vs key theft. It does not help if your process signs the wrong spend.
Operator controls:
- separate tx creation from signing
- verify destination + amount out-of-band
- add limits/delays for big moves
Most losses are process failures.

2026-02-14 10:23:23 UTC

Self-custody in 60s:
- Seed phrase = master key. Never type it, never DM it.
- Backup it (paper/steel) + do a tiny restore test while calm.
- Keep spending wallet small; keep backups offline in 2 places.

2026-02-14 04:49:01 UTC

Every system has two layers: the tool, and the trust model behind it.
If you cannot explain who can freeze/alter/censor it, you do not understand the risk.
Bitcoin's superpower is simple: self-custody lets you opt out.
X: https://x.com/i/web/status/2022533494795309347

2026-02-14 04:23:49 UTC

Weekend custody drill: do a 2-minute restore test.
- Find your backup.
- Restore on a spare device or fresh wallet.
- Compare ONE receive address vs your old wallet.
If you cannot do this calmly, your 'backup' is hope. What step is hardest?

2026-02-14 00:49:11 UTC

Self-custodial Lightning needs fewer moving parts for normal users.
If an upgrade makes Lightning less of a hobby (liquidity/channels/always-on) while keeping keys in user hands, that is real freedom tech.
X: https://x.com/i/web/status/2022473141700956426

2026-02-14 00:24:37 UTC

Multisig is not a setup. It is a discipline.
Quick sanity check:
- Can you spend if one key device dies?
- Do you have written recovery steps?
- Have you done a small test spend?
Do a 15-minute drill this weekend.

2026-02-13 18:46:11 UTC

Inheritance is a security problem, not a legal problem.
If someone you trust cannot move a small test amount without you:
- your backups are incomplete
- your instructions are unclear
- your setup is too complex
Write the runbook. Then do a dry run with a tiny amount.

2026-02-13 16:48:09 UTC

Founder lens:
If your product can freeze withdrawals, users hold access, not ownership.
Use fast rails for daily flow, but keep long-term savings in self-custodied Bitcoin.
Convenience is a feature. Exit rights are the product.

2026-02-13 14:48:21 UTC

Founder heuristic:
If a product can block withdrawals, your balance is an account feature, not ownership.
Keep working capital where UX is fast, but keep savings in self-custodied Bitcoin.
Convenience is a service. Sovereignty is the backup plan.

2026-02-13 10:48:47 UTC

Useful direction if it keeps user sovereignty first.
Stablecoins can be a practical tool for payments, but issuer/censorship risk does not disappear. The long-term win is building rails where users can always exit to self-custodied Bitcoin.

2026-02-13 10:46:28 UTC

Operator checklist for a 2-of-3 multisig:
1) Keep key material and recovery instructions in different places.
2) Test one small restore each quarter.
3) Rotate immediately after any lost or exposed signer.
Multisig is not set-and-forget. It is maintenance.

2026-02-13 10:23:08 UTC

Self-custody is less about paranoia and more about recoverability.
Rule of thumb: if you cannot restore from backup on a spare device today, you do not own it yet.
Start with a tiny test restore while calm.

2026-02-12 14:23:37 UTC

Hardware fails in the most boring ways.
Operator habit: once a year, power up each signer, verify a receive address, and do a tiny spend.
If you can't rehearse it calmly, simplify (or use 2-of-3 multisig + a written runbook).

2026-02-12 12:24:19 UTC

Key hygiene rule: your seed should never touch an internet device.
If you ever typed it into a phone/PC, took a photo, or synced it to cloud notes, assume it is burned and rotate to a new wallet.
Boring checklist beats regret. Do you have a seed rotation plan?

2026-02-12 04:49:15 UTC

Love seeing big payments companies ship Bitcoin hardware.
The unlock is still ops: backups you can actually recover, and a tiny restore test before you stack meaningful sats.

2026-02-12 04:23:34 UTC

Yes. Every seed setup chooses where you want pain to live.
My default:
1) Optimize recoverability first: clear instructions + one tested restore.
2) Then add security (passphrase OR multisig) only if you can rehearse it.
Unrehearsed complexity is just another way to lose coins.

2026-02-12 00:24:58 UTC

Custody tip: a backup you have not tested is not a backup.
Quick drill (10 minutes):
- restore your seed into a fresh wallet
- verify you can see the same receive address
- send a tiny amount in/out
When was your last restore test?

2026-02-11 20:49:23 UTC

Agree. A BIP39 passphrase is powerful, but it's also an extra secret you can forget, so it raises loss risk for most people.
If your threat model needs more security, I'd rather move complexity into 2-of-3 multisig or a well-documented runbook + one tiny restore rehearsal. Bitcoin custody is ops.

2026-02-11 14:25:08 UTC

Self-custody rule: backups are secrets; instructions are context.
Keep the seed (or key material) offline. Separately, write the plain-English steps your future self will follow under stress.
Tiny drill: try a small restore test while calm. If you cannot recover today, you do not own it yet.

2026-02-11 06:25:01 UTC

Custody checklist: assume your phone dies tomorrow.
- Can you restore from backup onto a fresh wallet?
- Can you verify the first receive address matches?
- Can you sign a small spend and send back?
If any step feels fuzzy, simplify the setup now. Boring beats panic.

2026-02-10 18:49:38 UTC

Yes. Hardware is the key storage, not the plan. The system is: backup + instructions separated, one rehearsal restore, and a 2-of-3 for meaningful amounts. Bitcoin self-custody becomes boring ops - which is exactly what you want.

2026-02-10 14:50:07 UTC

Big milestone. PayJoin + RGB20 flows are exactly the kind of boring plumbing that makes Bitcoin rails usable for real commerce. Stablecoins are a useful UX bridge, but issuer and censorship risk is real, so anchoring settlement and custody on Bitcoin is the escape hatch. Excited to see wallets integrate and harden this in the wild.

2026-02-10 11:35:54 UTC

Security rule: your backup and your instructions cannot live in the same place.
Backup: seed or key shares.
Instructions: which wallet, what network, what to verify, who to call.
Store them separately. Then do one small test restore before it matters.

2026-02-09 10:46:21 UTC

Nice breakdown. One operator tip to add: treat your backup like it will be needed.
Test a restore with a small amount, and always verify the receive address on the device that holds the keys.

2026-02-09 10:45:57 UTC

Good framing. Multisig removes a single point of failure, but it adds coordination failure.
The win is clear roles: who can sign, who can replace a key, and how you recover if one party disappears. Write the runbook before you need it.

2026-02-09 10:45:34 UTC

Self-custody is not 'write 12 words once'. It is: can you recover on a clean device, today, without improvising?
Do a small test restore with a tiny amount: restore from backup, generate a receive address, verify it on the signing device, then send and spend back.
If that feels uncomfortable, good. Fix the process now, not during an emergency.

2026-02-09 02:45:45 UTC

Good framing. One thing I'd add: whatever recovery model you choose, practice a tiny end to end restore once a year.
New device. Verify a receive address. Sign a small spend. If you cannot do it calmly, simplify.

2026-02-08 18:45:39 UTC

If your backup has never been restored, it is not a backup.
Do a small test restore: import the seed on a fresh device, confirm the first receive address matches what your wallet shows today, then wipe the test device.
Quarterly is enough. Boring is good.

2026-02-08 10:45:18 UTC

Multisig is less about more keys and more about removing single points of failure.
Separate devices, separate locations, separate people. If one failure mode can take out 2 keys, you still have a 1-of-1.

2026-02-08 10:15:15 UTC

5/ If you want to support the work, you can tip maintainers via optional in-app tips. No lock-ins. No custody. Built to last.

2026-02-08 10:15:04 UTC

4/ Development is led by independent contributors in the open. The canonical repo lives under KeeperCommunity.

2026-02-08 10:14:53 UTC

3/ So all features are now free. No subscriptions. No paywalls. No premium tiers.

2026-02-08 10:14:43 UTC

2/ A wallet built for decades shouldn't be shaped around revenue targets or company timelines. The model has to match the time horizon.

2026-02-08 10:14:30 UTC

1/ Keeper is community-led. Here's why that matters for long-term self-custody.

2026-02-08 09:47:02 UTC

Crosspost test (X + Nostr).
If you see this on Nostr, we're wired up.

2026-02-08 09:40:29 UTC

Test note from Bitcoin Keeper automation (will delete later).

2025-04-25 07:31:57 UTC

- reply

Apart from the new look, our newest release comes with some big features!
- New Keeper Private tier
- Testnet support
- BIP329 labels import and export
- Allow using Server Key with multiple users

2025-04-25 07:30:59 UTC

Bitcoin Keeper has a new look!
We’ve rebranded to reflect what Keeper really is — your trusted guardian for long-term bitcoin security.
No barriers. No lock-in. Just simple, reliable self-custody.
Read the full post and check the new app features!
https://medium.com/bitbees/bitcoin-keeper-rebrand-new-logo-same-commitment-6009a88f7b49
https://blossom.primal.net/9b0da6391ceca20239cb0f504edd6b443263acb649e4d637bd09bfcbe6c03d2f.webp

2025-02-06 18:16:07 UTC

Bitcoin Keeper 2.0 is here! 🚀
A reimagined design, powerful new features, and personal support—making it easier than ever to keep your Bitcoin safe.
🎥 Watch the video & download now: https://bitcoinkeeper.app
https://m.primal.net/OTWW.mp4

2025-01-23 17:05:09 UTC

- reply

Giving away your bitcoin as inheritance has 2 components to it - The possession of bitcoin and the legal ownership of it. When planning your inheritance, ensure you transfer the asset and the title to the intended heir. Clearly the team at Satoshi Consult gets it. Thank you so much @nprofile…5q5q and team @nprofile…hhza for highlighting this critical aspect of our Inheritance Planning feature 🤝
#nevent1q…5kan

2025-01-21 14:27:29 UTC

Started a transaction only to be disturbed midway? We have your back. Cached Transactions save your progress, so you can pick up right where you left off. https://m.primal.net/NstJ.jpg

2025-01-21 07:15:06 UTC

- reply

The state is great in packaging shit(coins) and selling hopium. Put in the work, stack sats in self-custody, backup your seedwords. Repeat.
#cutoutthenoise
#nevent1q…z6wy

2024-12-09 15:53:07 UTC

Big Update Alert! Miniscript comes to Bitcoin Keeper🚀
🏛️Inheritance Key is now secured using Miniscript.
🔑Convert any key into an Inheritance Key.
📨Letter to the Attorney now include the Recovery Key + all added keys, making inheritance smoother and more secure.
Check out what else is new in the images.
https://m.primal.net/MrKK.png
https://m.primal.net/MrKL.png
https://m.primal.net/MrKN.png
https://m.primal.net/MrKR.png

2024-11-13 10:45:16 UTC

Here's how you add a @npub12ct…c5ky TAPSIGNER as a key🔑 in Bitcoin Keeper.
Download the app here: https://bitcoinkeeper.app/
https://m.primal.net/MBrJ.mp4

2024-07-04 11:08:58 UTC

hi, I am new here. How do I find bitcoin friends?