1Sat Ordinals Basket Profile for BRC-46 / BRC-100
Wallets and applications both need to agree on where collectible items live and how they are described. This reserves the group name and pins down what may go in it and how it is labelled.
8 standards
Ordinals
The 1Sat family: an asset pinned to one satoshi, moved by spending that satoshi, with content inscribed alongside it. Several standards cover how a BRC-100 wallet stores them and what an application may do with them.
Also searched as 1Sat, 1Sat Ordinals, inscription, ordinal, NFT.
Filed under
8 standards, spread across 2 of the 12 topics.
Start with
BRC-147
1Sat Ordinals Basket Profile for BRC-46 / BRC-100
Wallets and applications both need to agree on where collectible items live and how they are described. This reserves the group name and pins down what may go in it and how it is labelled.
Filed under Tokens
Standards about this
Ordinals is the main subject of these 6.
147 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.
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.
210 Derived Collectibles
A digital collectible is normally just a picture plus a boring list of past owners nobody looks at. This standard describes a way for the picture itself to change over time and with use, so that a piece can visibly age, shift with the seasons, or wear a mark its owner chose, all computed fresh by anyone looking rather than fetched from a server.
217 Authenticated 1Sat Inscription
If you inscribe content onto a Bitcoin satoshi, anyone can copy the exact bytes into a new output and claim they made it, because the inscription itself proves content existed but not who put it there. Meanwhile, naive ways of adding a signature or label to that output can accidentally make the coin permanently unspendable, freezing the token forever. This standard fixes the layout so you can prove authorship and still move the token.
370 Sealed 1Sat Ordinal Reveal
A 1Sat Ordinal normally has its content sitting in plain view on the blockchain forever, which is useless for anything meant to stay private until a chosen moment or a chosen person, like an unopened collectible, a licensed file, or a credential. Before this, there was no agreed way to publish such content as encrypted data on that ordinal and later unlock it, either for everyone or for one named recipient, without putting the content back on chain again. This closes that gap so an owner can seal an ordinal once and decide later, and separately, whether the world or one person gets to read it.
Standards that touch it
These are about something else, and deal with ordinals on the way.
150 1Sat Provenance Remittance for Basket `1sat`
Proving an item is the genuine one, and not a copy of it, means tracing it back to where it began. This packages that trail so it can be checked without asking any service for help.
156 Latched 1Sat Provenance for Basket 1sat (Withdrawn)Withdrawn by the author. Do not implement.
Sometimes a standards document gets written, then the people behind it change plans and stop building what it described. If nothing marks that document as dead, other developers can still find it, assume it works, and build against something that was never finished or safe to use. This document exists to stop that from happening by pointing everyone to the real, working approach instead.
Usually read alongside
Concepts that keep appearing on the same standards as this one.
Was this helpful?