The extension, the web app and pairing
bWalletX also runs as a Chrome and Brave extension and as a web app. On iPhone the web app is the only way to get the full wallet, so we made backup mandatory there.
Back to an extension
Since the code started as an extension, building one again was cheap. On 1 October we branded it; on 3 October it shipped as bWalletX, with the full mobile interface in Chrome's side panel and a gold strip to open it full screen. We serve it from this site, not the Chrome Web Store, so you install it in developer mode. Brave works too.
Two fixes mattered. Each version used to install with a new extension ID, which meant a new, empty wallet. Since 5.1.9 a fixed key in the manifest keeps the same ID across versions. And on the question of who answers websites: on 3 October the extension set window.CWI only if no other wallet had. The next day we reversed that: bWalletX takes it by default, even over Yours, and a setting hands it back.
Letting websites find the wallet
Websites can discover bWalletX through BRC-100 wallet announcements, in the style of EIP-6963. A small connect.js on the Developers page shows how. For desktop sites and a phone wallet, there is phone pairing: scan a code, check the same 4-digit code on both screens, and requests travel through an encrypted relay that stores nothing. Each request still needs approval on the phone.
The web app, and iPhone
The web wallet runs at web.bwalletx.com. On iPhone, Apple only allows App Store apps, and the store edition can't trade. So bWalletX on iPhone is the web app, added to the Home Screen from Safari.
The iPhone page says it plainly: the keys are on your phone, not our servers, but browser storage is fragile. Safari can clear it. On 5 October we asked the browser for persistent storage, and added a mandatory backup step. After you create or restore a wallet, you save an encrypted backup or write down your recovery phrase and pass a three-word quiz. Receive waits until you have backed up. The only way to skip is "remind me later" at zero balance. In the native apps and the extension the step can be skipped.
What's not done
- The extension is not in the Chrome Web Store.
- Persistent storage is a request; Safari may still clear site data. A backup is the only protection.
- Pairing depends on our relay being up.