ElectrumSVP 0.2.0 reaches stable status, with security fixes and scaling questions ahead
ElectrumSVP’s [first release designated stable](https://coingeek.com/?p=624896) fixes a wallet-seed storage issue, expands local transaction-proof handling and improves coin control. Its developer says the project is ready for everyday use, though server resilience and a fuller SPV design still need work.
- Version 0.2.0 closes a beta phase that began in October 2025, according to developer Truth Machine.
- Wallets affected by the issue remove legacy plaintext mnemonic data when migrated; potentially exposed seeds should be replaced.
- Proof caching can cut repeat requests to Electrum servers, but it does not make the wallet server-independent.
- Air-gapped signing and privacy tools are planned, not included in this release.
ElectrumSVP is a maintained revival of the ElectrumSV wallet for BSV. Truth Machine calls version 0.2.0 the project’s first stable release. By “stable, ” he means he is comfortable recommending it for normal use. It has not passed an independent security audit.
“It means that ElectrumSVP has reached a point where I’m comfortable recommending it as a normal wallet release rather than an experimental beta.”
The available release information does not provide a reliable publication date. A project FAQ gives September 17, 2026, while another reference says the release arrived “this week.” Without a verified date to reconcile those accounts, the release timing remains unspecified here.
A seed-storage issue, and what affected users should do
ElectrumSVP’s [release notes](https://electrumsv.io/articles/2026/electrumsvp-0_2_0.html) say legacy BIP39 mnemonic data could remain in plaintext in a wallet database under certain circumstances. BIP39 is a format for the recovery words used to restore a wallet. The project’s available details do not say exactly which versions or conditions were affected, or how many wallets may be involved.
Version 0.2.0 removes the legacy data and automatically migrates affected wallets when they are loaded. Deleting data during migration cannot undo an earlier copy or exposure, though. ElectrumSVP advises treating any mnemonic that may have been exposed in plaintext as compromised: create a new wallet with a new seed, then move funds to it. This advice applies to potentially exposed wallets. It does not mean every user’s seed or funds were compromised.
Truth Machine says there is no evidence the issue was exploited in the wild. That is the developer’s assessment, not an independently verified incident finding. The project’s release notes document the fix, but the available information does not mention an independent audit.
“There is no evidence that this was exploited in the wild, so I don’t want to exaggerate the practical impact. But from a wallet-security perspective, storing a recovery seed in plaintext where it isn’t necessary is something I consider unacceptable.”
The project provides downloads for Linux, macOS and Windows, along with SHA-256 checksums and cryptographic signatures. It also lists the signing-key fingerprint E9BAFA19B15E6C2C158CDD400DB16C74A9CA7CF6. Users should follow the project’s signature-verification instructions and confirm the fingerprint through a trusted channel. A checksum alone does not establish who produced a file.
More transaction-proof data stays local
Version 0.2.0 expands ElectrumSVP’s BREAD proof handling. The release notes say the wallet can retrieve previously stored Merkle-proof data from its local SQLite database instead of requesting the same information repeatedly from [Electrum servers](https://www.reddit.com/r/Bitcoin/comments/hzr2b8/how_can_i_know_that_the_spv_server_that_my/). A Merkle proof is data that shows a transaction is included in a block.
The update can also connect an unconfirmed transaction to the latest confirmed transaction for which proof data is available. The reported “hop” count shows how many transaction links separate the unconfirmed transaction from that confirmed anchor. It does not prove the unconfirmed transaction will be confirmed or included in a block.
Users can export BREAD proof data for inspection or use with other tools. ElectrumSVP says BREAD is compatible with BEEF, but the available release details do not explain exactly how they work together. The project’s claims about BREAD should not be confused with [BUMP](https://docs.bsvblockchain.org/important-concepts/details/spv/data-models), a format for representing Merkle paths, or taken to mean the wallet no longer relies on servers.
Truth Machine’s longer-term goal is “true SPV, ” a design in which the wallet does more verification itself, including ideas explored in [SPV notarization](https://bsv.brc.dev/apps/0220). This release advances local proof handling, but more work remains, according to the developer. The available details do not explain how the wallet verifies cached proofs or provide performance benchmarks.
“There is still work to do before I would say the project has reached the final form of the ‘true SPV’ architecture I have in mind.”
Scaling concerns and a proposed fallback
Truth Machine says criticism of Electrum-style wallets’ ability to handle very large blocks led him to consider how the wallet might work if running [server infrastructure](https://milan2016.scalingbitcoin.org/files/presentations/D2%20-%203%20-%20Jonas.pdf) became uneconomical. His proposed fallback, which he calls an “estranged state, ” would let users see and spend their coins without immediate confirmation proofs. The wallet would request proof data when needed.
This is a theoretical design proposal, not a response to a reported current outage or a feature available in version 0.2.0. The project has not provided implementation details or activation conditions, or shown that the server network can handle a particular scale.
Truth Machine points to several infrastructure efforts: satoshi.io has a Rust-based ElectrumX server; bitails.io has a JavaScript implementation; Indelible.one is developing an SPV relay model being tested with ElectrumSVP; and gorillapool.io is running servers. He says the broader ecosystem is more active than it has been in years. These projects may add infrastructure, but their existence alone does not prove it is reliable or capable of meeting future demand.
“Bitcoin is economic, and the idea is to allow the wallet to survive a theoretical rapid scaling event, and give market participants time to offer solutions to users.”
Fee, coin-control and platform changes
The release overhauls fee displays and minimum-fee safeguards, and improves UTXO splitting and [coin control](https://adbytes.media/blog/stas-3-0-bitcoin-svs-first-layer-1-dex-redefines-secure-token-trading). A UTXO, or unspent transaction output, is a unit of bitcoin value available to spend. Coin control lets users choose which UTXOs to use.
One useful fix changes the “Max” button. It now respects coins selected under “Spend From” instead of reverting to all available funds. The release also adds Banana Blocks and Whatsonchain as exchange-rate providers for fiat conversions.
Other fixes address Windows QR scanning, macOS wallet data paths and Linux segmentation faults. The release notes also describe stronger checks for inconsistent local [blockchain headers](https://adbytes.media/blog/dna-storage-and-blockchain-bitcoin-sv-powers-enterprise-data-for-millennia), a “Refresh Headers” option, improvements to account and [key handling](https://github.com/electrumsv/electrumsv/issues/1041), and a fix for a nonce-handling issue that affected sweep-transaction signing. These are changes documented by the project, not claims of independent security testing.
The interface offers four themes: Light, Dark, Pink and Orange. Dark is the default.
Hardware wallets, cold signing and privacy plans
ElectrumSVP’s FAQ says its Ledger and Trezor integrations have been deprecated because the vendors no longer support BSV. Truth Machine recommends multisig setups, which require multiple signatures to authorize a spend, but the FAQ does not name a specific configuration.
An air-gapped signing workflow could offer an alternative. In this setup, an internet-connected device prepares a transaction and a separate offline device signs it. Truth Machine has discussed using animated QR codes to transfer the signing data, with possible support for PiWalletSV or similar setups. This remains a roadmap item, and no release date has been given.
Privacy tools are also being considered. The proposed approach would use UTXO splitting to help users avoid merging coins and potentially make timing analysis harder. These tools are not part of version 0.2.0, and splitting coins alone does not guarantee privacy.
ElectrumSVP’s release shows ongoing work on an established wallet architecture, including a concrete fix for an unacceptable seed-storage practice. Its broader ambitions will depend on implementation, independent scrutiny and dependable infrastructure, not confidence alone. Those questions are part of the wider discussion around [Bitcoin SV’s 2026 protocol upgrade](https://adbytes.media/blog/bitcoin-sv-chronicle-upgrade-2026-restoring-satoshis-vision-after-16-years).
“ElectrumSV is not a dead end as long as people are willing to do the work instead of abandoning it, and in fact, Electrum is an extremely strong and proven foundation to build on.”
Key questions and answers
-
What should users do if their wallet database may have exposed a seed?
ElectrumSVP advises treating the mnemonic as compromised, creating a new wallet with a new seed, and moving funds to it. Version 0.2.0’s automatic cleanup cannot undo an earlier exposure.
-
Does proof caching make ElectrumSVP independent of servers?
No. It can reduce repeat server requests when proof data is already stored locally, but the project’s fuller SPV design is still unfinished.
-
Are air-gapped signing and privacy tools available now?
No. They are proposed or under consideration, and no release dates have been provided.
-
Does ElectrumSVP still integrate with Ledger and Trezor?
No. ElectrumSVP’s FAQ says those integrations have been deprecated because the vendors no longer support BSV.
