Payments & transactions
Create actions, accept incoming transactions, and organize outputs into baskets. Build the experience your application needs.
createActionlistOutputsTHE WALLET ↔ APP STANDARD
A common language for applications and BSV wallets. Build with payments, identity, and cryptography—while keeping wallet choice in the user’s hands.
wallet.getPublicKey({ identityKey: true })
Your app requests. The wallet authorizes.
Interface illustration · no requests are sent.
Build for an interface.
Leave room for choice.
01 / THE STANDARD
BRC-100 defines how an application asks a wallet to act. The wallet handles the keys, permissions, and implementation.
Create actions, accept incoming transactions, and organize outputs into baskets. Build the experience your application needs.
createActionlistOutputsRequest public keys, sign data, and encrypt messages within a protocol context. Private key handling stays with the wallet.
getPublicKeyencryptWork with identity certificates and selectively reveal fields to a verifier. Ask for the information your application actually needs.
acquireCertificateproveCertificateThe interface is the agreement. Apps target a common API; wallets can have different user experiences, storage, and service choices. Check support and permission behavior in the implementations you target.
Explore the specification (opens in a new tab)02 / EXPLORE THE API
Get a feel for the interface. Choose an operation, edit the example, and copy the code into your project.
import { WalletClient } from "@bsv/sdk";
const wallet = new WalletClient();
const { publicKey } = await wallet.getPublicKey({
identityKey: true
});
Examples only. No wallet connection, transaction, or payment is made here.
03 / YOUR FIRST INTEGRATION
Use the TypeScript SDK’s WalletClient to speak BRC-100. Pair your app with a compatible wallet, handle permissions and errors, then build outward.
npm install @bsv/sdkCreate a WalletClient, then use the methods your app needs. Test the transport with your chosen wallet.
Make requests deliberate. Explain what your app needs, handle declined permissions, and confirm the network before transacting.
04 / THE ECOSYSTEM
Meet wallets and apps from across the BSV ecosystem. Integration labels help you find the right starting point for your project.
Reference implementations first. Other wallets A–Z.
BSV Association
A mobile browser with an integrated BRC-100 wallet.
BSV Association
The desktop reference wallet for applications using BRC-100.
HandCash
Desktop and mobile beta wallets implementing BRC-100 for app identity, permissions, and payments.
Hodos
A browser with a native BSV wallet and BRC-100 application interface.
Project Babbage
Desktop and mobile wallet experiences for identity, payments, and BRC-100 apps.
Peer-to-peer Privacy Systems Research
A native desktop wallet for BRC-100 identity, permissions, and payments.
Yours
A browser extension with a BRC-100 wallet engine, ordinals, and app connections.
A–Z. Follow each app’s guide to connect a wallet.
1Sat / bOpen
Explore and trade ordinals and tokens with the 1Sat wallet ecosystem.
opl.dev
Create, encrypt, and publish agent plans using a BRC-100 wallet.
BSV Radar
Discover BSV apps and developer tools, with BRC-100 wallet sign-in.
Project Babbage
Discover and publish apps in the Metanet catalog using a BRC-100 wallet.
BSV Association / Project Babbage
Connect social identity with wallet-held certificates for BRC-100 apps.
Know an app or wallet that belongs here? Add its name, official link, and integration details in a pull request.
05 / GO DEEPER
Go straight to the sources: the specification, reference code, wallet implementations, and developer tools.
The interface, data types, methods, and underlying standards. Start at the source.
WalletClient and the API documentation for building your integration.
Explore the tooling behind wallet implementations and wallet storage.
Explore the desktop wallet’s source, setup instructions, and releases.
See how a browser wallet brings the interface into web applications.
Follow the standards for keys, payments, certificates, and the wider ecosystem.
A FEW GOOD QUESTIONS
It’s an open wallet-to-application interface specification for BSV. Wallets implement it; applications use it. BRC-100 itself is not a wallet product or a token.
No. This explorer displays code and request shapes locally. To run that code in an application, use the SDK with a compatible wallet. The wallet may request user authorization.
The API gives applications a common contract. Wallet UX, supported transports, permission policies, storage, backup, and recovery can differ. Test against your target implementations rather than assuming identical behavior.
Start with the BRCs repository (opens in a new tab) for specification discussions. For an implementation issue, use that project’s repository and include a minimal reproducible example.
OPEN INTERFACES MAKE ROOM FOR IDEAS.