Wallets & Identity / Developer Tools
In Brief
BSV Wallet Relay 0.8.0 corrects a mismatch in the information exchanged when connecting a web application to BSV Wallet by scanning a QR code. The developer package is published; existing applications need to deploy the update before users benefit.
News Report
The update was published on November 16, 2026, at 22:53 UTC, following the merger of TS Stack pull request #1590. The related application-building tool, create-bsv-app, also published version 1.2.1 with an updated relay dependency.
Wallet Relay supplies the connection between a web application and a mobile wallet, allowing the phone to handle signing and authentication requests. This release corrects a compatibility problem in establishing that connection.
Why the Wallet Rejected the Connection
After scanning a QR code, BSV Wallet checks connection details with the website identified by that code. The website must confirm the same session, application identity key and communication protocol before the wallet accepts the pairing.
An earlier wallet-side security change required all three details to match. Wallet Relay’s session response supplied the identity key but omitted two fields the wallet expected. As a result, the response failed the wallet’s check.
Version 0.8.0 returns the complete set of matching details. The correction leaves the wallet’s verification requirement in place and makes the relay’s response satisfy it.
What Application Builders Need to Change
Existing applications need to update and redeploy their relay service. Applications that construct their own session responses must also pass through all the required details; the library update cannot correct a custom response that leaves them out.
The create-bsv-app update addresses new projects using its wallet-connect capability. Its generated client and server dependencies now select the 0.8 series. The previous dependency range would have kept them on the affected 0.7 series.
These are published developer components. They do not establish that every website offering a QR wallet connection has already upgraded.
Verification and Scope
The merged change reports passing automated tests and a compatibility check using BSV Wallet’s own QR-validation and session-reading code. Published Wallet Relay 0.7.0 failed that check, while the updated code passed.
The published package contains the new response fields, and the released app starter includes the revised dependency. The reported compatibility evidence is a software-level check; it does not document a complete physical-phone transaction test.
BSV TIMES Read
A QR code can scan successfully while the connection still fails because the application and wallet expect different information. This update illustrates the coordination required when a wallet strengthens its checks: the application’s connecting service must supply the information those checks require.
Developer Context
GitHub contributor sirdeggen authored the relay correction. His recent work also includes the YubiKey Vault safeguards released in BSV Wallet’s mobile toolkit 0.25.0. Wallet Relay is maintained within the BSV Association’s TS Stack repository.
Source Links
- TS Stack PR #1590 — QR pairing response correction and compatibility tests
- npm registry — Wallet Relay publication record and version history
- npm registry — create-bsv-app publication record and version history
- Wallet Relay documentation — Connection requirements at the merged revision
- BSV Wallet PR #88 — Earlier website-identity and pairing checks
- BSV Wallet PR #104 — Related YubiKey Vault work by sirdeggen
Posted on November 17, 2026 (UTC)

Leave a Reply