Wallet Infrastructure Watch / Developer Tools

The official BSV Desktop project has released version 2.7.1, adding native wallet support for STAS, DSTAS, and BSV-21 tokens alongside its existing BRC-100 application-to-wallet infrastructure.

The new token functionality supports receiving tokens, full and partial on-chain transfers, peer-to-peer settlement through MessageBox, and discovery through WhatsOnChain. A common protocol registry connects the different token standards to the wallet interface while retaining the transaction logic required by each standard.

The release also introduces Back-to-Genesis provenance verification. Rather than accepting a token solely because its visible identifier and amount appear valid, the wallet can trace its transaction ancestry toward the originating outpoint. The implementation records verification results and can display authenticity status within the wallet.

According to the merged development record, the new functionality was exercised end to end on BSV Blockchain mainnet across all three token standards. Testing included minting, full and partial transfers, receipt, verification, and rejection of a constructed token that copied the identifier and amount of an authentic token without possessing the required ancestry.

Version 2.7.1 also adds Who I Am to the default trust-certifier list for newly configured wallets. The certifier is described as verifying control of email addresses, telephone numbers, and X accounts. Existing wallets with previously saved trust settings are not automatically changed.

BSV Desktop is a cross-platform, self-custody-capable wallet for macOS, Windows, and Linux. It also serves as an official reference implementation for the BRC-100 interface, allowing applications to request wallet functions through a standardized permission layer.

View the BSV Desktop v2.7.1 release

Review the multi-standard token implementation

BSV TIMES read:
The important addition is not merely that another wallet can display several token formats. BSV Desktop is bringing transfer, discovery, peer settlement, and provenance checking into one BRC-100-oriented wallet environment. Back-to-Genesis verification is especially notable because token identity depends on verifiable lineage, not only on a name, symbol, or issuer identifier presented by an application. That moves token support closer to independently inspectable digital issuance infrastructure.

Posted on July 17, 2026