Open Protocol Labs

Beered by 0 people

6 standards · 2 topics

What Open writes about

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)
Issuing a fungible token, like a points balance or stablecoin unit, on Bitcoin used to mean inventing your own tracking scheme or relying on a global name registry that anyone could squat or collide with. There was no agreed way to say "this balance belongs to this token, forever" without a central ledger, and no standard way for an issuer to mint more supply later without rewriting the rules each time. This standard fixes the token's identity to the transaction output that created it and lets ordinary wallet transactions carry and mint balances.
David Case2026
162
1Color
Different fungible token systems on Bitcoin SV have each invented their own way of writing an amount and a token identifier onto a transaction output, so wallets and contracts have had to support multiple incompatible formats just to move the same kind of balance. That means extra parsing code, extra bugs, and scripts that cannot easily inspect a token output the way they can a plain payment. A shared, script-readable layout means any wallet or contract can check and build these outputs the same way, every time.
David Case2026
176
BSV-21 — Validity Proofs
When someone sends you a token on Bitcoin, you cannot just trust the number they tell you: you need to check it came from a real issuance and was never double-counted through splits or merges, without running a full blockchain indexer. Existing proof formats either strip out the very transaction history token math depends on, or only work for simple single-path assets, leaving no safe way to check a token tip you just received while offline.
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

What Open writes about

Search Beersy