bWalletX is in beta: test with small amounts.
bWalletX DownloadWeb →
bWalletX

A BRC-100 wallet

bWalletX implements the BRC-100 wallet interface. Any app or site built on the standard can connect to it, from Chrome, Android or the web. Your keys stay on your device, and you approve what each site may do.

Get bWalletX Developer guide

Where it works

How an app finds it

1. In the browser: BRC-100 discovery

The page dispatches brc100:requestWallet. The extension answers with brc100:announceWallet, info.rdns com.bwalletx.extension. In the Android app’s browser the answer is space.bwallet.mobile.

2. On a phone or the web wallet: pairing

The page shows a pairing link as a QR code. bWalletX scans it, or the web wallet takes it pasted, and both screens show the same 4-digit code. Calls then go end to end encrypted through our relay.

3. Either way: a standard WalletInterface

All three give your app the same BRC-100 WalletInterface from @bsv/sdk. The open-source @bwalletx/connect (MIT) does the discovery and pairing for you, and works with any BRC-100 wallet.

window.dispatchEvent(new Event('brc100:requestWallet'));
// bWalletX answers 'brc100:announceWallet' with info.rdns 'com.bwalletx.extension'
const { publicKey } = await wallet.getPublicKey({ identityKey: true });

BRC-100 calls

The extension, the Android app and the web wallet answer the same calls. A sheet means the user is asked first.

CallsbWalletXbwalletx serve
createAction, signActionYes · payment sheetYes · daily cap
abortAction, internalizeAction, listActionsYesYes
listOutputs, relinquishOutputYes · basket sheetYes
getPublicKeyYes · sheet on first connectYes
createSignature, verifySignature, createHmac, verifyHmac, encrypt, decryptYes · protocol sheetYes
revealCounterpartyKeyLinkage, revealSpecificKeyLinkageYes · sheetNo
acquireCertificate, listCertificates, proveCertificate, relinquishCertificateYes · sheetNo
discoverByIdentityKey, discoverByAttributesYes · sheetNo
isAuthenticated, waitForAuthentication, getHeight, getHeaderForHeight, getNetwork, getVersionYesYes

Certificate and discovery calls go to the standard wallet toolbox. We haven’t tested them end to end with every certifier and overlay yet; tell us if one doesn’t work for you.

What bWalletX refuses

The wallet’s own protocols

Protocols bWalletX uses for itself are refused for sites before any sheet is shown, with ERR_RESERVED_PROTOCOL.

Signatures anyone could reuse

Level-0 signatures are refused for sites. Signatures that another service could accept as the user ask for approval every time, and that approval covers one request only.

Mainnet only

getNetwork returns mainnet. bWalletX does not run on testnet.

Source and docs

Questions: support@bwalletx.com