10-06-2026 
|
Getting your Trinity Audio player ready...
|
TL;DR: ElectrumSVP, the revived classic Bitcoin wallet for BSV, has reached its first stable release with version 0.2.0, closing out the beta phase that began in late 2025. The release fixes a security issue that could have left BIP39 seed phrases stored in plaintext within wallet metadata and significantly upgrades the wallet’s BREAD verification system. Developer Truth Machine says criticism that Electrum “can’t scale” motivated him to prove the opposite, and the wider Electrum ecosystem on BSV is healthier than it has been in years. Next on the roadmap: an air-gapped cold wallet workflow designed to pair with PiWallet-style setups, and new privacy tools.
Key Takeaways:
- First stable release: ElectrumSVP v0.2.0 ends the beta phase; the developer now recommends it as a normal wallet release rather than an experiment.
- Seed storage security fix: BIP39 mnemonic words could previously be retained in plaintext in wallet metadata. v0.2.0 removes that storage and automatically migrates affected wallets.
- BREAD verification upgrades: proofs are cached locally, unconfirmed transactions are anchored to confirmed ancestors, and users can export their full proof cache.
- Not a dead end: Truth Machine rejects claims Electrum can’t scale, pointing to “estranged state” survival design and a reviving server ecosystem.
- Ecosystem revival: new ElectrumX server implementations in Rust and JavaScript, an SPV relay project, and miners running servers.
- Roadmap: air-gapped cold wallet workflow with animated QR codes aimed at PiWallet-style setups, plus privacy features built on UTXO control.
Table of Contents:
- A key upgrade secures wallet seed storage
- Wallet takes on more transaction verification
- Developer pushes back on ElectrumSV doubts
- New release brings fee and interface upgrades
- Cold storage and privacy tools lead the roadmap
- FAQs
ElectrumSVP, the maintained revival of the classic ElectrumSV wallet for BSV, released version 0.2.0 this week, its first stable release and the official end of a beta phase that began in October 2025.
For developer “Truth Machine,” the word “stable” has a deeper meaning than how well the code runs. “It means that ElectrumSVP has reached a point where I’m comfortable recommending it as a normal wallet release rather than an experimental beta,” he told CoinGeek.
“From here, I expect development to become more incremental.”
The seed storage fix
The most important change in v0.2.0 is a security fix for BIP39 wallets. Under certain circumstances, a wallet’s mnemonic seed words could be retained in plaintext in wallet metadata, meaning someone who obtained a copy of an affected wallet database could potentially find the seed without breaking the wallet’s password encryption.
Truth Machine said it’s important to keep the issue in proportion. “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.”
Version 0.2.0 no longer stores the mnemonic that way, and affected wallets are migrated automatically on first launch, with the plaintext data checked for and removed. Users whose wallet database may have been exposed to third parties are still advised to move funds to a new seed, as a precaution.
Verification moves into the wallet
The release also deepens BREAD (Blockchain Referenced Evidence and Data), the wallet’s BEEF-compatible proof format. Merkle proofs are now cached locally in the wallet’s own database instead of being repeatedly queried from Electrum servers, unconfirmed transactions can be anchored back to a confirmed ancestor rather than treated as isolated objects, and users can export their entire proof cache, including proofs for all active UTXOs.
This all serves a longer-term goal: a wallet that verifies itself rather than trusting a server. “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,” Truth Machine said. “But v0.2.0 moves substantially further in that direction because verification is increasingly being performed by the wallet itself rather than delegated entirely to a server.”
‘ElectrumSV is not a dead end’
Not everyone in the BSV world thought this project was worth the effort. Some respected community members argued that ElectrumSV was the wrong architectural direction, Truth Machine noted, and that it could never scale with very large blocks.
“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,” he said. The disagreement, he added, motivated him to investigate the scaling question more deeply, and some critics have since become more receptive.
His answer to the scaling doubt is what he called the “estranged state.” If enormous blocks ever made Electrum servers uneconomical to run, the wallet would degrade gracefully rather than fail. Users would still see and transact with their coins, just without immediate confirmation proofs, querying for proofs only when needed. Chain scanning becomes a backstop rather than a constant, and a market for proof and monitoring services can form around it. “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.”
He pointed out that the server side is reviving on its own: satoshi.io has a new Rust-based ElectrumX server; bitails.io has a JavaScript implementation; Indelible.one is developing an SPV relay model being tested with ElectrumSVP; and the miner gorillapool.io is running servers. “Overall, the ElectrumSVP ecosystem looks healthier and more active than it has been in years,” he said.
The community gets the credit for any of this happening at all. “If it were not for the community’s encouragement, I probably wouldn’t have put in the efforts I have in order to keep ElectrumSV going.”
Fees, coins, and colors
Elsewhere in v0.2.0, the fee system has been overhauled for clearer display and stronger minimum-fee safeguards, UTXO splitting and coin control are improved (pressing “max” now respects coins selected through Spend From), and long-standing platform bugs are fixed, including Windows QR scanning, macOS data paths, and Linux segfaults. USD conversion now uses the Banana Blocks API, showing fiat values for amounts, fees, and balances. Testing with what felt like significant sums turned out to be around two-tenths of a penny, Truth Machine noted: “It really shows you how micro the payments can get when using BSV.”
There are now four interface themes, with dark as the default. “The pink theme started as a bit of a joke, when I polled the community on which color they wanted to see in the wallet,” he said. Orange is a deliberate nod to the legacy Bitcoin color. Several people have independently suggested Winamp-style skins, possibly even tokenized and tradeable ones.
What’s next for ElectrumSVP
At the top of Truth Machine’s roadmap is a proper cold wallet workflow: possibly air-gapped signing with animated QR codes, designed to work well with hardware devices like PiWalletSV or similar setups—a natural substitute after Ledger and Trezor’s lack of BSV support forced ElectrumSVP to deprecate hardware wallet integration. Privacy tools are also under consideration, building on the wallet’s UTXO splitting to avoid merging coins and obscure timing analysis.
The philosophical reasons are still the same as ever. “When they (users) use Electrum and start to understand fees, and addresses, and confirmations, and coins, and how coins move for the first time, their eyes are opened,” Truth Machine said.
“That eureka moment is when Bitcoin starts to become something they understand and participate in, rather than simply something they hold.”
Mini FAQs:
What is ElectrumSVP?
ElectrumSVP is a maintained revival of the classic ElectrumSV Bitcoin wallet for BSV, developed by Truth Machine. It focuses on self-custody, user control, transparency, and SPV verification. Version 0.2.0, released September 17, 2026, is its first stable release.
What was the ElectrumSVP seed storage issue?
Under certain circumstances, BIP39 mnemonic seed words could be retained in plaintext in wallet metadata, potentially exposing them to anyone who obtained the wallet database file. Version 0.2.0 removes this storage and automatically migrates affected wallets. Users whose wallet files may have been exposed are advised to move funds to a new seed as a precaution. There is no evidence that the issue was exploited.
What is BREAD in ElectrumSVP?
BREAD (Blockchain Referenced Evidence and Data) is ElectrumSVP’s transaction proof format, compatible with the BEEF standard used across the BSV ecosystem. It lets the wallet verify transactions itself using Merkle proofs rather than trusting a server. Version 0.2.0 caches proofs locally, links unconfirmed transactions to confirmed ancestors, and allows exporting the proof cache.
What platforms does ElectrumSVP support?
ElectrumSVP v0.2.0 is available for Linux (AppImage), macOS (DMG), and Windows (installer and portable EXE). Downloads come with SHA256 checksums and GPG signatures for verification.
Does ElectrumSVP support hardware wallets?
No. ElectrumSVP deprecated the Ledger and Trezor integrations because those vendors no longer support BSV, posing risks to users. The developer recommends multisig setups and is building an air-gapped cold wallet workflow with animated QR codes designed to work with PiWallet and similar devices.
What is the “estranged state” in ElectrumSVP?
The estranged state is a fallback design in which the wallet continues to work even if the Electrum server infrastructure becomes unavailable or uneconomical. Users would still see and spend their coins without immediate confirmation proofs, querying proofs only when needed, while the market adapts to provide verification services.
Watch: Blockchain’s Big Fix for Affiliate Marketing
