Wallet Infrastructure Watch / Applications

In Brief

ElectrumSVP has released v0.2.0-beta.1, a new testing build of the independently maintained desktop BSV wallet with substantial changes across blockchain-header integrity, BREAD transaction verification, fees, UTXO control, account management and platform compatibility.

The release adds additional header checks and recovery tools, reduces repeated dependence on Electrum servers when Merkle-proof data is already stored locally, extends BREAD verification to some unconfirmed transactions, and expands user control over coin selection and transaction construction.

The developer describes the release as a beta intended for testing before the next official release and advises users to test with small amounts and report unexpected behavior.

News Report

ElectrumSVP has released version 0.2.0-beta.1, beginning a new public testing cycle for the independently maintained desktop BSV wallet.

The release article describes the update as concentrating on security, verification, transaction control, reliability and usability. The developer announced the downloadable beta publicly on September 15 and asked users to test the wallet and report issues before the next official release.

The beta status is important.

ElectrumSVP explicitly states that v0.2.0-beta.1 is intended for testing and feedback rather than being the next stable release. Users are advised to test cautiously and report problems or unexpected behavior.

The release follows ElectrumSVP v0.1.0, which became the project’s first official non-beta release in April after ElectrumSVP emerged as an actively maintained continuation of ElectrumSV.

Version 0.1.0 had already introduced BREAD verification, revised fee handling, BIP39 wallet creation, expanded UTXO controls and updated desktop builds.

The new beta shows ElectrumSVP moving beyond its initial continuation phase and into broader wallet hardening, with substantial work on verification, transaction control, reliability and day-to-day usability.

Stronger Blockchain-Header Checks

One of the most consequential areas in v0.2.0-beta.1 concerns blockchain headers.

ElectrumSVP uses block headers as part of its lightweight verification model. The new release performs additional integrity checks before the wallet starts, intended to detect corrupted or inconsistent header data and problems associated with orphaned blocks or chain reorganizations.

The developer also reports fixing a synchronization bug that could cause the local headers file to become corrupted after 2016-block boundaries.

A new Refresh Headers option has been added to the graphical interface, giving users a direct way to recover and refresh locally stored header data when necessary.

These changes matter because lightweight wallets do not independently run the complete node infrastructure behind the blockchain. Their security instead depends partly on correctly maintaining and checking the chain information required to verify the evidence they receive.

BREAD Verification Moves More Work Local

The release also makes substantial changes to ElectrumSVP’s BREAD verification system.

BREAD stands for Blockchain Referenced Evidence and Data. ElectrumSVP introduced it in its first official release as a simplified verification format focused on establishing evidence for funds rather than carrying complete transaction ancestry.

The earlier v0.1.0 release moved the wallet toward BREAD as its primary verification approach.

In v0.2.0-beta.1, Merkle-proof data can now be obtained directly from information already stored in the wallet’s local SQLite database rather than repeatedly requesting that information from Electrum servers.

That reduces unnecessary network requests and allows more of the verification process to operate from evidence the wallet has already collected.

The update also extends BREAD verification to unconfirmed transactions.

Where suitable evidence exists, an unconfirmed transaction can be anchored to the most recent confirmed transaction for which proof data is available. ElectrumSVP can then report the number of transaction hops separating the unconfirmed transaction from that confirmed anchor.

Users can additionally export BREAD proof data in JSON format for further inspection or use with other tools.

The result is a more explicit evidence path between wallet transactions and confirmed blockchain data rather than relying solely on a remote server’s statement about transaction status.

Transaction Fees and Coin Control Reworked

Transaction construction has also received a broader overhaul.

ElectrumSVP says the fee system has been revised to give users greater visibility and control over transaction fees, including additional safeguards intended to make unusual or excessive fee cases easier to identify.

The interface now provides clearer information about the fee being applied while a transaction is being constructed.

UTXO and coin-control functions have also been substantially revised.

The release improves the coin-splitting workflow, gives users greater control over which UTXOs are selected, provides more direct control over coin selection during splitting, and adjusts the underlying transaction-construction process.

These features continue an approach already visible in v0.1.0, where ElectrumSVP emphasized individual UTXO control, freeze and unfreeze operations, and the ability to choose which coins are used in a transaction.

For users managing many outputs, those controls make the wallet less dependent on automatic coin-selection decisions.

Account and Private-Key Handling

Version 0.2.0-beta.1 also changes account and key management.

Multiple accounts are now supported by default, while new safeguards prevent duplicate private keys from being imported into an account where the same key is already present.

A bug affecting imported-private-key accounts has been corrected so affected accounts display properly again.

The release also fixes derivation-path display for wallets using custom derivation paths.

These changes are less visible than the interface improvements, but they concern information users may depend on when recovering wallets, importing keys or verifying how an account was constructed.

Address Freezing Becomes Easier to See

Address freezing has also been revised.

Frozen and unfrozen addresses can now be distinguished visually through clearer color feedback, making it easier to see which addresses have been excluded from normal spending behavior.

ElectrumSVP has continued to expose relatively direct coin and address controls. The new interface work attempts to make those controls easier to understand rather than leaving important wallet state visible only through less obvious settings.

USD Display and Additional Data Sources

Fiat-reference handling has been improved across the wallet.

The new release expands exchange-rate provider options, including BananaBlocks and WhatsOnChain alongside other available services.

The developer says USD conversion and fiat-value presentation have also been revised throughout transaction-related interfaces.

These values are informational rather than part of BSV transaction settlement. Their purpose is to provide a familiar reference while users create and review payments.

Windows QR Scanning and Sweep Signing

Several narrower fixes address specific failure conditions.

On Windows, a QR-code scanning bug could leave the camera locked after a single scan and require the application to be restarted. Version 0.2.0-beta.1 reports that issue as fixed.

The release also corrects a nonce-handling problem affecting sweep-transaction signing.

ElectrumSVP’s sweep function allows funds controlled by an imported private key to be moved into the wallet without making that imported key a continuing wallet account.

Because the signing process directly controls the transaction moving those funds, the nonce correction belongs to the security-related portion of the release rather than merely interface maintenance.

Linux, macOS and Python Compatibility

The beta includes several desktop-platform fixes.

Compatibility problems that could cause ElectrumSVP to crash under Python 3.10 have been addressed.

Linux fixes include a segmentation fault affecting newer environments, including Ubuntu 26.04 and Arch-based systems.

A macOS Vault data-path issue has also been corrected.

Default Electrum servers and block-explorer information have been updated to reflect currently available services.

The project continues to provide desktop builds across Windows, Linux and macOS rather than moving toward a mobile-only wallet model.

Interface Changes

ElectrumSVP v0.2.0-beta.1 adds several visual themes through Preferences, including Light, Dark, Pink and Orange.

Smaller interface changes also affect coin displays, spacing, status indicators, transaction information and general consistency.

These additions are secondary to the verification and transaction-control changes, but taken together the release represents a fairly broad revision rather than a narrowly targeted bug-fix build.

From ElectrumSV to ElectrumSVP

ElectrumSVP is an independently maintained fork and continuation of ElectrumSV rather than a BSV Association wallet.

The distinction has an unusual element of continuity.

Earlier in 2026, the public ElectrumSV account stated that ElectrumSV was no longer maintained and directed users toward ElectrumSVP and its maintainer.

In a later post, the same account said that if it needed to access BSV, it would personally download and use ElectrumSVP rather than continue relying on an unmaintained ElectrumSV release.

That amounted to a public handoff toward the newer project, although ElectrumSVP remains independently maintained rather than being another release from the former ElectrumSV development team.

That continuity gives ElectrumSVP a clearer place in the BSV wallet landscape than a newly created experimental fork would normally have.

The original ElectrumSV repository still preserves its earlier 1.3.x release history, including the 1.3.17 beta published in January to address server-connection problems.

ElectrumSVP has since developed along its own release path.

Still a Beta

Despite the breadth of the update, v0.2.0-beta.1 should not be confused with ElectrumSVP’s next stable release.

The project explicitly asks users to test the wallet across different operating systems, hardware configurations, wallet types and transaction scenarios.

Particular attention is requested around wallet restoration, transaction verification, BREAD proof handling, fee calculations, coin control, header synchronization, QR scanning and application stability.

The developer says continued testing and feedback will help identify remaining issues before the next stable release.

That qualification is particularly important for wallet software, where an apparently minor fault can affect transaction construction, recovery or access to funds.

BSV TIMES Read

ElectrumSVP v0.2.0-beta.1 is significant less because of any single headline feature than because of where the development effort is concentrated.

Much of the release is about allowing the wallet to verify more for itself, preserve better local evidence, expose more control to the user and recover more cleanly when local state becomes inconsistent.

The BREAD changes are a good example.

Reducing repeated dependence on remote Electrum servers when suitable Merkle data is already held locally does not eliminate network services. It does, however, move another part of the verification process toward evidence the wallet possesses and can inspect itself.

The same pattern appears in header-integrity checking and UTXO control.

A lightweight wallet inevitably uses infrastructure outside the application. The important question is how much of what that infrastructure reports the wallet can independently check, preserve and recover.

ElectrumSVP also shows that BSV wallet development remains technically plural rather than converging around only one implementation model.

BRC-100 has become an important and increasingly active application-wallet framework, but it is not the only path being developed. ElectrumSVP continues a different lightweight-wallet tradition centered on headers, transaction evidence, direct UTXO control and independent verification.

The two directions do not need to be treated as a contest for every development to be useful.

BRC-100 is oriented strongly toward a common interface through which applications can request wallet capabilities. ElectrumSVP is presently focused more directly on the wallet itself: how it manages transactions, verifies evidence, controls individual outputs and gives its user visibility into those operations.

In a still-small ecosystem, that kind of parallel development can be healthy. Different implementations expose different assumptions, test different tradeoffs and give users and developers more than one model to evaluate.

Technical standards and architectures earn their position over time through implementation, interoperability, reliability and use. At this stage, continued experimentation remains part of that process.

ElectrumSVP v0.2.0-beta.1 is still a test release, but it is a substantial one.

Its next meaningful threshold will be whether these changes survive broader testing and become part of ElectrumSVP’s next stable version.

Source Links

ElectrumSVP v0.2.0-beta.1 — Release Notes

ElectrumSVP v0.2.0-beta.1 — GitHub Release

ElectrumSVP — GitHub Repository

ElectrumSVP v0.1.0 — Earlier Official Release

Posted on September 15, 2026