Skip to main content
Beta — BRC wallet only. These methods apply to HandCash Desktop / Mobile over BRC-100. They are not Connect (authToken + @handcash/sdk) or Wallet API (/v1/waas/*).
Apps talk to the wallet with standard BRC-100 methods. Payments, items, and tokens are not separate APIs — they are transactions your app describes and the user approves.

Payments and actions

Connect, read balance, send BSV, stage and sign, receive, list history

Collectables

Read inventory, mint, transfer, and receive 1Sat items

Tokens

Read balances, mint BSV-21, transfer, and receive tokens

Signing and encryption

Identity key, derived keys, signatures, encryption, HMAC, certificates

Permissions and scopes

Origins, prompts, auto-pay, scoped baskets, error codes, deadlines

Local bridge

Loopback ports, discovery, transport errors

​
Overview

Payload shapes follow BRC-100.

​
Permissions at a glance

Grants are bound to your origin and stored per wallet account. Plain BSV payments can skip the prompt when the user enabled auto-pay; item and token mints, sends, and releases always prompt. Full model — origin identity, auto-pay and spending limits, scoped basket grammar, every error code, and request deadlines: Permissions and scopes.

​
HandCash extensions

These travel over the same bridge but are not part of BRC-100, so feature-detect them:

​
Reserved for HandCash hosts

Market, migration, and account-administration methods are origin-gated and return 403 to other apps: createMarketListingAdvert, createMarketPurchaseIntent, verifyMarketListingProvenance, purchaseMarketListing, getMarketSettlementReceipt, createCancelMarketListingAdvert, getMarketListingStatus, markMarketListingPublishFailed, getTokenIcon, getLegacyAddress, refreshLegacyAddress, listMigrationTxids, claimCloudHandle, clearClaimedCloudHandle, and createAdminIdentityProof. Build on createAction and internalizeAction instead — they are portable across BRC-100 wallets.

​
Next steps