Open Protocol Labs

Beered by 0 people

6 standards · 2 topics

Tokens

159
1Sat Ordinals — Single-Satoshi Tokens and Origin Tracking
A single satoshi, the smallest unit of bitcoin, can be moved around like any other coin, but there was no agreed way to treat one specific satoshi as a unique, trackable item that keeps its identity as it passes from wallet to wallet. Without that, you cannot build things like collectibles or one-of-a-kind tokens directly on bitcoin transactions, because every coin looks fungible and interchangeable. This gives that single satoshi a permanent name and a way to prove where it has been, so it can act like a non-fungible token.
David Case2026
160
1Sat Ordinals — Inscription Envelopes
A tiny on-chain token can prove it is unique and traceable, but on its own it carries no real content, it cannot hold a picture, a document, or app data. Developers needed a standard way to attach that content directly to the token so wallets and apps can find and display it without inventing their own format.
David Case2026
161
BSV-21 Fungible Tokens (JSON / Legacy)
Before this, issuing a token on Bitcoin meant choosing between a global ticker that anyone could race to claim first, or a custom indexing scheme that only your own app understood. There was also no standard way to say "this token's supply can grow later because the issuer controls minting" versus "this supply is fixed forever." This standard gives tokens a stable identity tied to the transaction that created them, and a shared set of rules so any wallet or indexer can agree on balances, minting, and burning.
David Case2026
162
1Color
Different token projects on Bitcoin invented their own ways to mark which coins represent a balance and which represent permission to create more, so wallets and apps had to learn each scheme separately, and some schemes needed a JSON file parsed just to tell a value from an identifier. This made it hard to combine a token balance with a custom spending rule, like requiring two signatures or a smart contract condition.
David Case2026
176
BSV-21 — Validity Proofs
A wallet receives a token payment and has no way to check, on its own, that the tokens are real and not just a made-up balance in some JSON. Unlike simple payments where a chain of ownership is a straight line, token transfers can split and merge across many transactions, so proving one output is valid means gathering and checking a whole web of related transactions. This defines exactly which transactions must be bundled together and how to walk them to confirm the tokens are genuine, without needing to trust a central index.
David Case2026

Peer to peer

231
Binary Encoding for the Message Relay Interface
If your app sends messages between users and those messages contain binary data, like signatures or encrypted blobs, encoding everything as JSON text makes the payload bigger than it needs to be, and that waste gets worse the more binary content you pack in. This matters once you care about bandwidth or are sending a lot of small messages. It makes it possible to send and receive the exact same messages more compactly.
David Case2026

Open Protocol Labs

Search Beersy