🟠🛡️ Bitcoin-Safe.org Desktop Wallet - Questions & Support

[bitcoin-safe]

🧩 Compact Block Filters — optional lightweight mode for faster, more private syncing. Awesome work from @rustaceanrob on the CBF client.

Awesome upgrade, thanks for caring about privacy. Shout out to @rustaceanrob!

Thanks!

Version 1.7.0  is released:  https://github.com/andreasgriffin/bitcoin-safe/releases
New ✨
📝 Message signing & verification
↩️ Back button
⚙️ Faster network switching with 1-click restart

Tool Suite 🛠️
📸 Bitcoin QR
📝 Message signing & verification
🔌 USB hardware wallet tools
🛡️ Updater

[satscraper]

Version 1.7.0  is released:  https://github.com/andreasgriffin/bitcoin-safe/releases

In my view, to burst onto the highly tight wallet market  a new wallet needs to offer something extraordinary and highly anticipated by regular users, full i^{ncluding address generation and sending} support for BIP352 for example. Yes, we have the Silentium wallet, which fully supports BIP352, but it’s a short tailed project that exists only as a web app rather than the fully featured wallet. For this reason every time you announce the new release I expect to see Silent Payment implemented, but there has been no such feature so far.

Is support for Silent Payment on your roadmap?

[bitcoin-safe]

Is support for Silent Payment on your roadmap?

Yes SP will be integrated in Bitcoin Safe if possible. It's being worked on here https://github.com/bitcoindevkit/bdk-sp to integrate it in BDK.  When that is done we need Hardware signer support, which will be critical.  SP   has the downside that you cannot verify the destination address is correct. You have to trust the hardware signer.  Also, SP gets complicated in the multisig case.
Tldr: Sp is awesome, but there needs a lot of work to be done until it becomes a smooth experience with hardware signers.



Version 1.7.1 was released Check out https://github.com/andreasgriffin/bitcoin-safe/releases

New Features
    Choice between BTC and ₿ in the UI
    UTXO based coin selection is supplemented by address based coin selection directly from the address list
    Fully configurable P2P listening connections for instant transaction notifications

Improvements
    Better explanations for RBF/CPFP transactions
    Better notifications for sync errors
    Bug fixes, Translation fixes

[satscraper]

Is support for Silent Payment on your roadmap?

Yes SP will be integrated in Bitcoin Safe if possible. It's being worked on here https://github.com/bitcoindevkit/bdk-sp to integrate it in BDK.  When that is done we need Hardware signer support, which will be critical.  SP   has the downside that you cannot verify the destination address is correct. You have to trust the hardware signer.  Also, SP gets complicated in the multisig case.
Tldr: Sp is awesome, but there needs a lot of work to be done until it becomes a smooth experience with hardware signers.

Good, thanks.

Another hot topic in the field is support for MiniScript.

AFAIK, this language is currently supported by only two wallets, namely,  Liana and Nunchuk.

What about Bitcoin Safe? I’m aware that it doesn’t support MiniScript at the moment, but is there any hope that it might be added in one of future releases?

[cygan]

the new version 1.8.0 has now been released. it includes the following new features and improvements:

• zooming for the balance chart
• custom nLocktime support
• simple secure updates on windows, machst and linux

and some more...

https://github.com/andreasgriffin/bitcoin-safe/releases/tag/1.8.0

[bitcoin-safe]

What about Bitcoin Safe? I’m aware that it doesn’t support MiniScript at the moment, but is there any hope that it might be added in one of future releases?

Thank you for asking, someone else asked late last year and yes, we are discussing the options to implement miniscrip internally, but still really early days. However, we are working to open up the option to install external plugins that could speed up the process and allow other python developers to easily contribute to enhance Bitcoin-Safe with such functionalities for more advanced users without affecting the core code.

[bitcoin-safe]

A really great question has been shared by @Hispo in the Spanish topic, I tought it would be good to translated it and share it here.

By the way, I have a question regarding the development and maintenance of this wallet.

What is the business model for this project? In the case of cold wallets, they offer their software services thanks to their hardware sales.

Does Bitcoin-Safe have any advertising contracts or something similar to guarantee an influx of money for the development of its wallet?

Because I doubt that these kinds of projects can be sustained over time with major updates without a significant source of income.

Thanks in advance for the answer.

Thank you very much for your question; it's a very important point and, as you say, fundamental for the future development and maintenance of the wallet.

In the case of Bitcoin-Safe, the code is FOSS (Free & Open Source Software); anyone who knows Python can verify its authenticity and the fact that there is no telemetry or tracking of any user information. Therefore, we do not collect, let alone sell, any type of data to other entities, and for the same reason, we do not offer advertising or other ways of monetization through the app or our website.

The only thing you will find on the website are a couple of links to buy hardware wallets at a discount to encourage users to prioritize and evaluate privacy and security by using them.

Regarding monetization options, after two years of self-funded development, we have received a grant from OpenSats. That covers marginal costs and, obviously, that model is not sustainable in the long term. It helps us a lot and, more importantly, motivates us to keep going with this project that we personally need for ourselves and our communities.

In recent months, we have developed the Plugins section; you already have some free ones available, like the Wallet Graph and encrypted Chat&Sync via Nostr. In the upcoming version 2.0, we are going to provide our users with more unique features that no other wallet achieves with privacy. So, expect Scheduled Payouts and Notifications (via Nostr DM, Email, Telegram, CalDAV (calendar events), and Webhooks) soon.

This plugin setup will not only allow us to monetize some unique features but also open the doors to other developers and companies to deliver Bitcoin-related services through these plugins.

This will be our first attempt at monetization to sustain the project for the future, both near and far. We are also open to suggestions, so if you have any ideas to help us sustain the project, don't hesitate to share.

₈₆₇

[satscraper]

This will be our first attempt at monetization to sustain the project for the future, both near and far. We are also open to suggestions, so if you have any ideas to help us sustain the project, don't hesitate to share.

₈₆₇

Probably, if you manage to attract some crypto card issuer and integrate their card into the wallet’s loop, you will be able to monetize your project further. Besides, it could add value to the wallet itself and, in turn, expand its client base. I personally would love to use it  ^{even though I already have several wallets with integrated cards like Pavy, Ready, Trusty Plus, etc}.

[bitcoin-safe]

Probably, if you manage to attract some crypto card issuer and integrate their card into the wallet’s loop, you will be able to monetize your project further. Besides, it could add value to the wallet itself and, in turn, expand its client base. I personally would love to use it  ^{even though I already have several wallets with integrated cards like Pavy, Ready, Trusty Plus, etc}.

Thank you for your suggestions, that's definitely possible. However we don't want to be intermediary or resell third parties services. We aim pioneer and deliver unique functionalities that will ideally bring new user toward Bitcoin-Safe. As I mention the new plugin functionality will be open for anyone to build extra scripts that ca interact with the codebase of the Bitcoin-Safe wallet.

The plugin will be highly scrutiny and approved before be listed in our official source code.


I invite everyone to test the latest RC verso from the post below and test out the greatest UX/UI improvements Bitcoin-Safe ever faced since inception.

👇👇👇👇👇👇

NEW UX in Bitcoin-Safe 2.0.0rc0, now out for testing 🧪

• Compact Block Filters are now default
• Redesigned Wallet Setup Wizard with
• Redesigned hardware signer UX with added support for MK5 + Trezor Safe 7

🧪 Please test and give lots of feedback! 🙏⚡

Download and verify from : https://github.com/andreasgriffin/bitcoin-safe/releases/tag/2.0.0rc0

932

[satscraper]

• Compact Block Filters are now default

Making  CBF as default for private syncing eliminating the need to connect to any server is a great option for those who have no possibility ^{or wish} to run their own node, while at the same time wish to preserve their privacy. But may I ask how many nodes actually serve CBF? My node doesn't do it because it requires extra disk space to build the relevant filter index, and besides, some nodes run in pruning mode. So it may be quite a hard task for safe-wallet to find the active CBF nodes, which could result in prolonged sync times.

[bitcoin-safe]

... may I ask how many nodes actually serve CBF? My node doesn't do it because it requires extra disk space to build the relevant filter index, and besides, some nodes run in pruning mode. So it may be quite a hard task for safe-wallet to find the active CBF nodes, which could result in prolonged sync times.

Thanks for asking. The good news is that the user decide. From our side we suggest a default of two nodes but the user can change it to as any as wished/needed. In the reverse case, the functionality could also be used to connect to only one node, for those us that already run a node and want to maintain the setup.

The functionality is accessible from Network Settings panel (ctrl + .) > Manual peers under the Network Monitor section at the bottom.
It also enable Instant transaction notifications

More info at https://bitcoin-safe.org/en/knowledge/compact-block-filters/

[satscraper]

From our side we suggest a default of two nodes

I guess those are yours nodes. Am I right?

, the functionality could also be used to connect to only one node, for those us that already run a node and want to maintain the setup

As I understand it, I can use it to connect bitcoin‑safe to my Bitcoin Core, provided I configure the latter to serve as CBF node. But as I already mentioned this requires additional space on my SSD and extra time to sync from scratch to build the filter index.

So are there any advantages to changing my current setup (Sparrow + fully synced Bitcoin Core) to  new one like safe‑wallet + Bitcoin Core with CBF enabled?

In my view, I wouldn’t gain any privacy benefits from such a change. What else could matter?

[bitcoin-safe]

From our side we suggest a default of two nodes

I guess those are yours nodes. Am I right?

No, the node are pick randomly form the network

, the functionality could also be used to connect to only one node, for those us that already run a node and want to maintain the setup

As I understand it, I can use it to connect bitcoin‑safe to my Bitcoin Core, provided I configure the latter to serve as CBF node. But as I already mentioned this requires additional space on my SSD and extra time to sync from scratch to build the filter index.

So are there any advantages to changing my current setup (Sparrow + fully synced Bitcoin Core) to  new one like safe‑wallet + Bitcoin Core with CBF enabled?

In my view, I wouldn’t gain any privacy benefits from such a change. What else could matter?

The advantages are speed. CBF allow much faster connection that traditional RBF. The only requirement is that the node must have blockfilterindex=1 and peerblockfilters=1 in your bitcoin.conf file. CBF setup also enable near-instant notifications when tx are broadcasted.

When comparing with the setup you mentioned, the benefits are not in the privacy side but in the set of extra functionalities Bitcoin-Safe offers when compared to other desktop wallets. When transacting in mainnet, Bitcon-Safe is more secure just because it don't store any keys or seed locally. The hardware wallet is always needed to transact (send) on mainnet. On any testnet seeds signing is ok as coin are worthless.

[satscraper]

Bitcoin-Safe just shipped thebig release, v2.0.0, featuring easier setup, a clearer signing screen, broader device support, quicker QR scans, and privacy-by-default networking via CBF. Improvements to QR scanning and new entities in hardware wallet support will likely be the most important factors in increasing user adoption of this software wallet. ^{Personally I like that CBF is now default feature}.

[bitcoin-safe]

Thank you @satscraper for the share, appreciated. This release is a big milestone for us, here are some more details and links (better for indexing and search):

Bitcoin-Safe 2.0 is now available. It's a free/open-source desktop wallet for Bitcoin cold storage where seed phrases never touch the computer (hardware-signer-only).

What's new in 2.0:

1. Private chain sync (Compact Block Filters) — new wallets download compact block filters directly from random Bitcoin Core peers. No Electrum server needed. No address leakage to third parties.

2. Guided setup wizard — rebuilt first-run experience with device-specific instructions for each supported hardware signer. Clearer recovery PDFs.

3. Device-focused signing — signing actions centered on the actual hardware device. Multisig shows exactly which signers are done.

4. New hardware support — Trezor Safe 7, Blockstream Jade / Jade Plus (Bluetooth), Foundation Passport Prime, COLDCARD Mk5. 30% faster animated QR codes.

5. Plugin architecture — GPG-signed plugins distributed via external sources repository. Independent versioning for each plugin.

The project is GPL v3, with reproducible builds verified by WalletScrutiny and code signing via SignPath Foundation.

More details about this release at: https://Bitcoin-Safe.org/en/news/bitcoin-safe-2-0-0/
Full changelog: https://github.com/andreasgriffin/bitcoin-safe/compare/1.8.1...2.0.0


1078

[satscraper]

Bitcoin-Safe v.2.1.0 release seen the light of day featuring  light/dark theme switching and MetroVaul support, alongside upgrade to BDK 3.0 under the hood. It also brings a visualization of connected compact-block-filter nodes on the map view and re-enables custom account xpub fetching for USB signers. The release also marks a rebrand to "Bitcoin-Safe," plus the round of bug fixes.

UPD. Just in one new Bitcoin-Safe was elevated to 2.1.1 with UI bug fixes.


UPD.UPD. The latest release is 2.1.3

[Forsyth Jones]

Where can I find the pgp public key to verify the binaries?

I couldn't find it on github or in this ANN thread.

In the past, when I tested it on Windows, I found the setup process quite complicated (too many steps), has that improved?

[cygan]

Where can I find the pgp public key to verify the binaries?

I couldn't find it on github or in this ANN thread.

In the past, when I tested it on Windows, I found the setup process quite complicated (too many steps), has that improved?

i hope i can help you. check out the link below and you'll definitely find what you're looking for at the very bottom
https://bitcoin-safe.org/en/download/

Verify signature

All software is signed with my private key. Verify the download is authentic by following these steps:

Import my public key and verify the signature with:

[satscraper]

Where can I find the pgp public key to verify the binaries?

Here you are:

BTW, Bitcoin Safe is finding more and more market acceptance. For example, such reputable hardware developers as Foundation recently added to their leading product, namely Passport Prime, support for pairing it with Bitcoin Safe.Besides, this wallet is listed on the official bitcoin.org page. That speaks for itself.