What this section is for
These pages are for developers building against the HandCash BRC wallet — the self-custodial Open BSV wallet that ships as:
It is not documentation for:
If your integration still uses Connect auth tokens or WaaS access keys, stay in those sections. Switch here when you target the user’s local BRC wallet (identity key, baskets,
createAction / internalizeAction, permissions).
Mental model
- The user holds keys in HandCash Desktop or Mobile.
- Your app requests wallet methods over BRC-100.
- On Desktop, HandCash exposes a local HTTP bridge (loopback) so web and native apps can call those methods with origin-gated permissions.
- Custody stays with the user. Cloud messagebox / handle resolve are convenience services, not required for payments to succeed.
In this section
- Getting started — prerequisites, when to use the BRC wallet vs Connect / WaaS
- Wallet interactions — the map: every app-facing method and permission level
- Payments and actions — connect, balance, send BSV, stage and sign, receive, history
- Collectables — read inventory, mint, transfer, and receive 1Sat items
- Tokens — read balances, mint BSV-21, transfer, and receive
- Signing and encryption — keys, signatures, encryption, HMAC, certificates
- Local bridge — connect to Desktop on loopback, discover the wallet, and handle errors
Protocol references
- BRC-100 — wallet ↔ application interface
- BRC-46 — output baskets
- BRC-29 — peer payments (when paying another HandCash / BRC identity)