The Plug and the Appliance: PaiyBit and the BRC-100 Wallet Standard

If you spend any time around the BSV ecosystem right now, you will hear people talking about BRC-100. It is worth understanding, because it answers a question every blockchain application eventually has to answer: how does an app talk to a wallet?

Here is the plain-language version. BRC-100 is a standard interface — a common plug shape. If every wallet exposes the same plug and every application expects the same socket, then any app works with any wallet. You bring your own wallet, the app connects to it, and neither side has to know anything about the other's internals. It is vendor-neutral, open, and designed so the ecosystem does not fragment into a dozen incompatible walled gardens. That is a genuinely good idea, and PaiyBit supports it wholeheartedly.

The same foundations

At the heart of BRC-100 sits a key derivation scheme called BRC-42 — often called Type-42 derivation. Without drowning in the mathematics: it is a way of growing an entire tree of keys, identities, and payment addresses out of a single master seed, so that one secret backs everything you own, and every relationship you have gets its own private branch of the tree.

PaiyBit runs on exactly this. One account seed derives every wallet and every persona identity a user has, and the same Type-42 derivation scheme the standard is built on has been proven live on BSV mainnet inside PaiyBit. The user holds a twelve-word phrase, and that phrase is their money — fully non-custodial, recoverable on any device, touchable by nobody else, including us.

So at the layer that actually matters — the cryptography, the ownership model, the self-custody — PaiyBit and BRC-100 are already speaking the same language.

A different packaging choice

Where PaiyBit differs is the packaging, and the difference is deliberate.

BRC-100 assumes a particular order of operations: the user goes and gets a wallet first, and then applications connect to it. That is the right model for an ecosystem of interoperating apps and power users. But it puts a step in front of the very first thing a newcomer tries to do — and for the people PaiyBit is built for, that step is fatal. Ask someone to install a wallet before they can tip a creator, and you lose the overwhelming majority of them at the door.

So PaiyBit flipped it. The wallet is built into the site itself. You click a link and you have a working self-custody wallet in seconds — no install, no extension, no setup, nothing to download. Same ownership model, same twelve-word phrase, zero friction. If BRC-100 defines the plug shape, PaiyBit built the appliance with the wallet already inside.

What building the wallet in makes possible

The embedded wallet is not just an onboarding trick. Because the wallet and the application live in the same place, PaiyBit can do things a generic send-receive-and-sign interface does not attempt:

• Streaming payment channels — pay per page of a book, per five seconds of video, per letter of a chat message, with the unspent budget refunded the moment you walk away.
• On-chain escrow — booking deposits and meetups held by a script, not a company, refundable by consensus rules if things fall through.
• Bearer-token cards — collectible persona cards that are real on-chain property, tradeable peer-to-peer with royalties the blockchain itself enforces.

These are application-layer money features. A wallet standard, rightly, does not try to define them. But they are only smooth to use because the wallet is native to the experience rather than a separate program the site has to negotiate with.

The honest gap

What PaiyBit does not do today is expose the plug. If you already carry a BRC-100 wallet, you cannot currently connect it to PaiyBit and pay from it, and a PaiyBit wallet does not yet travel with you to other BRC-100 applications. That is a real limitation, and it is the fair criticism of the embedded approach.

It is also, importantly, a bridge rather than a rebuild. Because PaiyBit already runs on the same derivation scheme the standard is built on, adding BRC-100 compatibility is integration work, not new cryptography — wiring up the standard interface, not re-architecting the wallet. The foundations were laid to make that possible from day one.

First the appliance, then the plug

PaiyBit's users are creators and fans, not crypto people. The bet has always been that self-custody should be invisible before it is interoperable — that the way you win people over to owning their own money is to never make them think about it until the day they ask. BRC-100 is where the ecosystem is converging, and PaiyBit expects to meet it there. But the appliance had to work first.

Got my bib, have you got yours?