LBSX Desktop Wallet Opens Public Windows Beta With BSV-21 Support

Wallets & Identity / Applications

In Brief

LBSX Desktop Wallet has opened a public beta for Windows, with a downloadable installer and published source code. The wallet is designed to send and receive BSV tokens and manage BSV-21 assets while keeping private keys on the user’s computer. It requires an existing recovery phrase and has not undergone an independent security audit.

News Report

Developer Captain (@bsvdrip) announced the public beta on November 7, 2026. Version 2.1.00 is available through GitHub for Windows x64, marking a new stage beyond the project’s earlier introduction and token-minting demonstration.

The published application includes support for ordinary BSV token payments, receiving addresses with QR codes, BSV-21 token transfers, token creation, and time-lock functions. It also includes peer-to-peer token listings and an on-chain community chat feature.

The repository contains application source code and development tests for wallet storage, transaction construction, token operations, and transaction-proof verification. These tests use simulated data and broadcasting rather than live mainnet transactions. The availability of the installer and source code is confirmed, although the released application has not been independently tested by BSV TIMES.

Importing an Existing Wallet

LBSX takes an import-only approach. Rather than generating a new recovery phrase, it requires users to import an existing BIP39 phrase, generally consisting of 12 or 24 words.

The wallet derives an address from that phrase using a specified derivation path. Because different wallet applications may use different paths, importing the same phrase does not always produce the address a user expects. The developer advises checking that the displayed address matches the intended wallet before transferring funds.

This design means users who do not already have a recovery phrase must create one through another suitable application or an independent offline process.

Local Keys and Transaction Verification

LBSX is designed to derive and use private keys locally, with encrypted storage for recovery information and wallet data. According to the project’s documentation, users do not need an LBSX-hosted account, and their recovery phrases are not held on a developer-operated server.

The wallet also incorporates simplified payment verification (SPV). This allows it to examine evidence that a transaction was included in a block without downloading and processing every transaction in BSV Blockchain’s history.

LBSX maintains a local chain of block headers and checks transaction proofs against it. However, proof of inclusion does not establish whether an output remains unspent. The application therefore continues to use an external service for current balance and spending information.

BananaBlocks supplies the wallet’s ordinary blockchain data and transaction-broadcasting services. An API key is optional, although requests without one have lower usage limits. A configurable alternative provider is planned but has not been implemented. The current code includes limited alternative broadcasting routes for certain rejected transactions.

Security and Current Limitations

The developer has published a security policy detailing recovery-phrase handling, local encryption, transaction verification, and external service dependencies.

The documentation explicitly states that no independent third-party security audit has been performed. The Windows installer is also unsigned, which may trigger an unknown-publisher warning from Microsoft SmartScreen.

The developer advises users to preserve offline recovery backups and begin with small test amounts. Hardware-wallet signing, multisignature arrangements, and manual coin control are not supported in this release.

Some operations carry application service fees in addition to ordinary BSV Blockchain transaction fees. The published schedule lists 10,000 satoshis for a standard BSV token send and 0.5 BSV tokens for minting a BSV-21 asset.

The Peer Chat feature also has an important privacy limitation: its messages are recorded publicly on-chain, and the encoding used by the application can be reversed. The developer describes it as a community feed rather than confidential messaging.

Windows is currently the only supported operating system. The project has not announced independently verified support for macOS or Linux.

BSV TIMES Read

The public beta makes LBSX available for users and developers to examine as an independent desktop wallet, rather than merely a project demonstrated through development updates.

One interesting aspect is its division of responsibilities. Private-key management and transaction construction take place on the user’s computer, while external infrastructure supplies information about the blockchain and handles broadcasting.

This distinction matters because control over private keys and independence from service providers are different properties. A wallet may keep its users’ keys locally while still depending on another service to retrieve balances, identify available funds, or deliver transactions to the network.

LBSX attempts to strengthen that arrangement through local transaction-proof verification, giving the application a way to check certain blockchain evidence for itself. Nevertheless, it remains dependent on BananaBlocks for current spending information and routine network access.

The release therefore adds another approach to the BSV Blockchain wallet ecosystem: a desktop application combining local key custody, transaction-proof verification, and BSV-21 management. Its practical reliability and security will become clearer as the public beta receives further testing, development, and external review.

Developer Context

LBSX Desktop Wallet is developed by Captain (@bsvdrip) and distributed through the captainsvbot GitHub repository under the MIT open-source license.

The application is built with Electron and React. Its repository includes source modules for local key management, transaction construction, SPV verification, BSV-21 operations, and interactions with external blockchain services.

Source Links

Posted on November 9, 2026 (UTC)