Under the Surface looks at projects, standards, experiments, and community activity that may not rise to the level of a headline but are still worth noticing. Some are new, some are continuing work, and some are quieter developments that help show what is taking shape across the BSV community.

Wallets / Payments Infrastructure

A substantial mobile-wallet project is developing publicly inside the BSV Blockchain GitHub organization.

bsv-wallet is a dedicated self-custodial payments wallet for iOS and Android, built separately from the broader BSV Browser project. Rather than combining wallet functions with web browsing, it opens directly into a conventional wallet environment centered on balance, payments, receiving funds, activity, and security.

Private keys remain on the device, with wallet records stored locally through SQLite.

The project currently supports several ways of making a payment.

Users can send through MessageBox and PeerPay identities, use conventional P2PKH addresses, or make nearby phone-to-phone payments through a local wireless connection.

That last capability is particularly interesting.

On iOS, Local Payments use Apple Wireless Direct Link. On Android, they use Nearby Connections. A transaction can therefore be passed between nearby devices without an internet connection, with offline-created payments queued for delivery or internalization when the required connection later becomes available.

This does not make BSV Blockchain itself operate offline. The transaction still ultimately needs to reach the network. What changes is the immediate relationship between the two devices: the payer and recipient can exchange the transaction locally without requiring internet connectivity at the moment of payment.

The wallet also contains several recovery and security layers.

A BIP-39 recovery phrase controls the main wallet, while Shamir Secret Sharing can divide recovery material into multiple printable or scannable QR shares. Full wallet databases can also be exported and imported for migration and backup.

An optional Vault adds a separate hardware-backed spending key secured through a YubiKey. On iOS, the hardware interaction uses NFC; on Android, it uses USB. The repository includes the enrollment process, key derivation, ceremony state, and interface needed to operate that additional security boundary.

Identity and trust functions are also appearing inside the wallet.

The project includes BRC-68 certifier management and can pair with external wallets or clients through dedicated deep links. That points toward a role beyond simply sending to an address: the mobile wallet can potentially provide payment, identity, and key-management capabilities to other applications through the developing BRC-100 ecosystem.

That architectural distinction may ultimately be one of the more important parts of the project.

BRC-100 defines a vendor-neutral interface between applications and wallets. An application does not necessarily need to contain its own complete wallet if it can request the required signing, payment, identity, or cryptographic functions from a compatible wallet selected by the user.

A dedicated mobile wallet could therefore remain relatively focused while serving many different applications above it.

The repository is already unusually complete for public development work. It includes twelve interface languages, multiple BSV network environments, transaction monitoring, backup infrastructure, native mobile modules, test coverage, and commands for producing App Store and Google Play production builds.

But this is not yet a public wallet launch.

The project documentation still instructs developers to create development builds before running the application, and no formal consumer release announcement or public App Store or Google Play listing has been identified.

That distinction is worth preserving.

What can be seen today is a substantial dedicated mobile-wallet architecture under active development, including capabilities that reach beyond an ordinary payment interface. A formal beta, store listing, tagged release, or BSV Association launch announcement would represent a different milestone and could warrant separate Latest News coverage when it occurs.

For now, the public repository offers an early view of what that wallet may become: a self-custodial mobile payment and key-management layer that can work directly between people, function locally when internet access is unavailable, protect higher-security funds behind dedicated hardware, and connect with applications through common wallet standards.

Source: GitHub — bsv-blockchain/bsv-wallet / BRC-100

Update — September 8, 2026