BSV TIMES

BSV Wallet Merges Review Step for Payments Restored From Backup

BSV Wallet Merges Review Step for Payments Restored From Backup
, ,

Wallets & Identity / Payments Infrastructure

In Brief

BSV Wallet has merged a safeguard against an old database backup reviving a payment its owner had canceled. The updated code holds unfinished PeerPay payments for review after restoration and requires a separate Send action before delivery can resume.

The change is available in the project’s source code. Its inclusion in a downloadable mobile app has not been confirmed.

News Report

The fix was merged on November 5, 2026, at 21:18 UTC. It concerns the BSV Wallet project for iOS and Android, where users control their own keys, and PeerPay, its person-to-person payment system.

How an Old Backup Could Restart a Payment

Imagine saving a wallet database while a payment is waiting to be sent, then canceling that payment. Restoring the earlier backup could bring back the outdated instruction and allow automatic delivery to proceed. That is the failure described in the project’s pull request.

The affected records belong to the wallet’s outgoing payment queue. Here, cancellation means stopping that outgoing payment in the wallet.

A Fresh Decision Before Sending

The changed code places imported, unfinished PeerPay payments on hold. The owner first reviews the payment and then separately chooses Send. Records already marked as sent remain part of the payment history.

Before showing the recipient and amount for approval, the wallet checks those details against the signed payment stored in the backup. It checks again when the owner approves delivery. If the stored record has changed since the review, the wallet refuses to release it.

The fix also prevents the older resend mechanism from bypassing the hold.

Testing and Availability

The contributor reports 208 automated tests passing across 12 affected suites, covering imported payments, the review screen, record retention, and resending. The pull request explicitly says that integration with live payment services and physical devices remains unverified.

As of November 9, the latest published version of the shared mobile toolkit, @bsv/expo-wallet-toolbox 0.23.0, still comes from November 1 and does not contain this fix. The confirmed development is the merged source change.

BSV TIMES Read

A wallet backup can preserve more than balances and history. It can also preserve instructions that its owner no longer wants carried out. Requiring a fresh decision after restoration gives the owner control over whether those unfinished payments should proceed.

Developer Context

Siggi, who contributes on GitHub as icellan, authored the fix. The pull request was merged by sirdeggen.

Source Links

Posted on November 9, 2026 (UTC)

Leave a Reply