What is Ordinals?

Introduction

Ordinals is a scheme for giving every satoshi on Bitcoin a stable identity and then following that satoshi as it moves through transactions. That sounds almost paradoxical, because Bitcoin is usually understood as a system of balances and interchangeable units: if you receive 10,000 sats, the protocol does not ask which particular sats they are. Ordinals matters because it shows that, even without changing Bitcoin’s consensus rules, you can impose a deterministic ordering on satoshis and use that ordering as a foundation for collectibles, inscriptions, and other asset-like constructions.

The key point is easy to miss. Ordinals does not add a new token, does not create a sidechain, and does not ask Bitcoin nodes to recognize a new asset type. It works by reading ordinary Bitcoin data in a very particular way. If everyone agrees on how sats are numbered when mined, and how they are assigned to outputs when spent, then software can talk about this sat rather than merely this amount.

That shift from amount to identity is the whole story. Once a satoshi can be named and tracked, it can carry social meaning, collector value, or attached data. Inscriptions, which bind content to specific sats, are the most famous consequence. But inscriptions are downstream. The more fundamental idea is that Bitcoin already has enough structure to let software distinguish one satoshi from another, if you choose a consistent convention.

How does Bitcoin normally treat satoshis; are they fungible or individuated?

At the consensus level, Bitcoin cares about values and spending conditions. A transaction consumes previous outputs and creates new outputs. The rules ensure that value is conserved: apart from the subsidy created in coinbase transactions, sats are neither created nor destroyed. What Bitcoin does not explicitly track is the path of each individual satoshi through every transaction.

That omission is natural. Most payments do not need identity at the satoshi level. If Alice pays Bob 50,000 sats, neither party normally cares whether the sats came from the beginning of a block reward, the middle of an exchange withdrawal, or the first sat ever mined after a halving. For ordinary money, fungibility is a feature.

Ordinals begins by asking a different question: *if we wanted to refer to a specific satoshi anyway, could we do it deterministically from public chain data? * The answer is yes, because Bitcoin transactions already have an order. Blocks are ordered. Transactions inside blocks are ordered. Inputs and outputs inside transactions are ordered. Values are discrete. Those facts are enough to construct a reproducible mapping from “the nth sat ever mined” to “where that sat is now.”

This is why the scheme feels surprising at first and obvious once it clicks. Bitcoin does not natively label sats, but it does preserve exactly the accounting invariants needed for an external numbering system.

The core mechanism: number sats by mining order

Ordinal theory assigns every satoshi an integer starting at 0, in the order in which sats are mined. The very first satoshi in Bitcoin’s history gets ordinal 0. The next gets 1, and so on across the entire supply.

This gives each sat a serial number, but the serial number is not arbitrary. It is tied to Bitcoin issuance itself. New sats appear only in block subsidies, so the ordering begins with the subsidy in the genesis block and continues block by block as new subsidies are created. In that sense, ordinal numbers are not trying to invent a parallel asset universe. They are simply indexing the satoshis Bitcoin already created.

A subtle part of the scheme is how sats are ordered within a block, especially around the coinbase transaction. The specification treats the coinbase as if it had an implicit input for the subsidy, followed by implicit inputs corresponding to fees from each fee-paying transaction in block order. That convention gives a definite sequence for both newly minted sats and fee sats collected by the miner. Without such a rule, “which sat came first in this block?” would be ambiguous.

The important thing here is not that this is the only imaginable ordering. It is that the ordering is precise, deterministic, and shared. Ordinals is a convention layered on top of Bitcoin, so its power depends on everyone using the same convention.

How does Ordinals determine which sats move in a transaction (the FIFO rule)?

Once sats have numbers, you need a rule for how those numbered sats move through transactions. Ordinals uses a first-in, first-out rule, usually shortened to FIFO. The sats assigned to transaction inputs are concatenated in input order, then distributed to outputs in output order according to each output’s size.

This sounds abstract until you picture a transaction as a stream of satoshis. Suppose a transaction has two inputs. The first input contains 5 sats, and the second contains 7 sats. Under ordinal accounting, the transaction therefore controls a 12-sat sequence: first the 5 sats from input 0, then the 7 sats from input 1. If the transaction creates an output of 8 sats and another of 4 sats, the first 8 sats in that sequence go to output 0, and the remaining 4 go to output 1.

That is the entire transfer algorithm. There is no separate consensus message announcing “the rare sat moved here.” Software infers the location from the ordinary transaction graph plus input and output ordering.

A worked example makes the mechanism concrete. Imagine an output holding sats with ordinals 100 through 109. Another output holds sats 210 through 214. A new transaction spends both outputs, with the 100–109 output listed first and the 210–214 output listed second. The transaction creates one output worth 12 sats and another worth 3 sats. The first output receives 100 through 109, then 210 and 211, because FIFO consumes the first input’s sats before moving to the second. The second output then receives 212, 213, and 214. If a wallet wanted to preserve sat 210 for a collector, it would need to construct the transaction so that 210 lands in the desired output rather than being swept along with ordinary payment change.

This is where Ordinals becomes operational rather than merely conceptual. If you care about individual sats, input order, output order, and exact amounts become a form of sat control.

What is a satpoint and how do Ordinals index a sat's location?

A numbered satoshi still needs a current location. Ordinals uses the idea of a satpoint, which identifies a sat inside a specific output. A satpoint consists of an outpoint (transaction ID plus output index) and an offset showing where the sat sits inside that output.

This is a natural representation because Bitcoin stores coins as unspent transaction outputs, not as account balances. If an output contains 10,000 sats, an ordinal-aware index can say that a particular sat is at offset 237 inside that output. If the output is spent, the index applies the FIFO rule and computes the sat’s new offset in one of the resulting outputs.

Mechanically, this means Ordinals is mostly an indexing problem. Bitcoin consensus already enforces conservation of value. Ordinal-aware software replays the chain, tracks ranges of sats inside outputs, and answers questions such as “where is ordinal x now?” or “which ordinals are inside this UTXO?” The reference ord software is built around exactly this job: it talks to a synced Bitcoin Core node, builds an index of sat locations, and exposes wallet and explorer functions on top.

This also explains an important limitation. The indexing burden is large. The draft specification notes that indexes supporting fast ordinal queries can become very large, and historical coverage is especially expensive. So while Ordinals needs no consensus change, it does need substantial off-chain infrastructure to be practical at scale. The scheme is simple in logic, but not free in implementation cost.

How does giving sats an identity change what Bitcoin can represent?

Once a satoshi has a stable public identifier, it can act as an anchor for meaning outside ordinary payment semantics. That is the reason Ordinals exists. A wallet, marketplace, or protocol can say: this asset is associated with ordinal n, and ownership of the asset follows control of the sat carrying that number.

The simplest use is numismatic. Some sats become interesting because of where they appear in Bitcoin’s issuance schedule. The first sat of a block, for example, can be singled out by the ordinal scheme. Community members can then treat those sats as collectibles. This is not a consensus property; Bitcoin itself does not know or care that a sat is “special.” But the identity is objective enough that people can coordinate around it.

A more consequential use is attaching digital artifacts. If a piece of content is linked to a particular sat, then transferring that sat transfers the artifact in the social and software sense recognized by ordinal-aware systems. This is how Ordinals turns a unit of Bitcoin into a carrier for NFT-like behavior without deploying an ERC-721-style contract system.

The important distinction is between what is fundamental and what is conventional. The numbering and FIFO transfer rule are the mechanical core. Collector value, rarity labels, and asset semantics are conventions built on top.

What are inscriptions and how do they attach content to a satoshi?

An inscription attaches arbitrary on-chain content to a specific satoshi by revealing that content in a transaction that transfers the sat. The Ordinals handbook describes the result as a Bitcoin-native digital artifact whose content becomes inextricably linked to that sat.

This is where Ordinals meets the broader public imagination. Images, text, code, and other payloads can be committed on-chain and then tracked via the ordinal-bearing satoshi. Because the sat already has an identity and movement rule, the inscription has a stable carrier. Without ordinal numbering, the content would still be in the chain, but there would be no equally natural answer to “which unit is this artifact attached to?”

Historically, this design reflects dissatisfaction with earlier NFT models that often relied on off-chain media or contract-specific semantics. The Ordinals approach tries to make the artifact itself live on Bitcoin and let transfer ride on Bitcoin’s native UTXO model. That is why the idea resonated so strongly with some Bitcoin users: it felt less like importing an account-based token standard and more like reinterpreting Bitcoin’s own discrete units.

The implementation details of inscriptions are distinct from ordinal numbering, but the conceptual relationship is tight. **Ordinals gives the pointer; inscriptions give the payload. ** That is why inscriptions depend on Ordinals, not the other way around.

How does Ordinals define rarity, and why is market value still subjective?

Ordinals also introduced several representations for a sat’s identity, including integer notation, decimal notation, degree notation, percentile notation, and a name encoding. These are mostly interface choices: different ways to make the same sat easier for humans or software to discuss.

The deeper cultural layer is rarity. The handbook defines a taxonomy in which certain sats are considered uncommon, rare, epic, legendary, or mythic based on periodic Bitcoin events such as being the first sat of a block, difficulty adjustment period, halving epoch, cycle, or the genesis block. The structure works because Bitcoin issuance has a nested periodic rhythm, and the ordinal numbering makes a sat’s place in that rhythm explicit.

What matters here is a distinction between rule-based rarity and market meaning. It is objectively true, within Ordinals’ convention, that a given sat is the first sat of a block or the first sat of a halving epoch. It is not objectively true that the market must care. The handbook is explicit that “rare” and especially more exotic designations are ultimately community judgments. Ordinals supplies the coordinates; culture supplies the valuation.

This is one reason the protocol has both technical and numismatic appeal. The technical scheme identifies unusual sats cleanly. The social layer decides which unusual patterns deserve attention.

How must wallets change to preserve ordinal-bearing sats and inscriptions?

If sats are treated as distinct, ordinary wallet behavior can become dangerous. A standard Bitcoin wallet is designed to optimize spending, not to preserve the identity of particular sats. It may merge UTXOs, reorder inputs, create change outputs in ways that move an inscription unintentionally, or spend a collectible sat as fee-bearing dust in an otherwise normal transaction.

That is why ordinal-aware wallets need sat control. They must know which UTXOs contain important ordinals or inscriptions and construct transactions so those sats land where intended. The ord project warns that Bitcoin Core itself is not aware of inscriptions and does not perform sat control, so using generic Bitcoin RPC flows with an ordinal-bearing wallet can result in loss of inscriptions.

There is also a practical constraint from Bitcoin policy: transferring a single sat in isolation may create outputs below the dust limit, making the transaction non-standard and hard to relay or mine. In practice, moving a particular sat often requires splitting and reassembling value across multiple transactions so the desired sat remains in a spendable output that satisfies standardness rules. This is a good example of a broader pattern in Bitcoin: consensus may permit something that day-to-day relay policy makes awkward.

So when people say Ordinals works “without changing Bitcoin,” that is true in the narrow protocol sense. But it does not mean the user experience is effortless. It means the scheme is compatible with Bitcoin as it exists, while relying on specialized software to navigate Bitcoin’s transaction mechanics safely.

What privacy and fungibility trade-offs do Ordinals introduce?

The moment you give sats public identities, you change their social and analytical properties. The draft BIP and related discussion are direct about this. Ordinals is opt-in, but the identifiers are public. If you intentionally use ordinal-bearing sats, you are making their history easier to talk about and trace.

That has Privacy consequences. A collectible sat or inscribed sat can become a visible object with provenance, not just value. It also has fungibility consequences. Bitcoin units are normally treated as interchangeable, but ordinals invite people to care about where some sats came from and what they carry. In practice, most sats remain “cardinal,” meaning their individual identity does not matter. But Ordinals creates a formal language for the minority that do matter to someone.

There are system-level consequences too. Indexes are large. Specialized explorers and marketplaces add infrastructure overhead. Heavy inscription activity has also fed broader disputes about block space and relay policy. Some Bitcoin developers and node operators argue that inscription-style data use imposes costs on the network and node operators, while supporters argue that this is simply one more valid use of scarce block space. That disagreement is partly technical and partly political, and it remains unsettled.

It is worth being exact here: **Ordinals itself is not a consensus fork of Bitcoin. ** Nodes can ignore ordinal semantics entirely and still validate the chain correctly. But once enough users and applications coordinate on the scheme, it becomes economically and socially real even if it remains external to consensus.

Why did Ordinals gain adoption on Bitcoin?

Ordinals spread because it solved two problems at once. Technically, it gave Bitcoin a native-looking way to identify individual units and bind artifacts to them. Culturally, it gave users a reason to look at Bitcoin’s issuance structure not just as monetary policy, but as a landscape of collectible objects.

That combination explains the ecosystem around the core idea: indexers, explorers, wallets, inscription services, and marketplace infrastructure. The reference project includes a draft BIP, an index communicating with Bitcoin Core, wallet tooling, explorer functions, inscription support, and documentation. Other service providers and indexers built around the same conventions because once the numbering rule is shared, a whole application layer can emerge without asking the base protocol for new features.

It also explains why related constructions appeared quickly, including token protocols that use inscriptions and ordinal-aware indexing. Those systems are not Ordinals in the narrow sense, but they inherit the same basic pattern: Bitcoin transaction data interpreted by off-chain software according to a common rulebook. Where those higher-layer systems become fragile, as in some inscription-based token transfer designs, the weakness is usually not in ordinal numbering itself but in the extra conventions layered on top.

When and why can Ordinals fail or lose a shared convention?

Ordinals depends on a simple but strong assumption: that the community will continue to honor the same deterministic reading of Bitcoin transaction order. If implementations diverged on input ordering, coinbase treatment, or related edge cases, the shared identity system would fracture. In that sense, the scheme is robust only to the extent that its conventions remain canonical.

It also depends on Bitcoin staying transparent enough for public tracing. The scheme works because transaction structure, values, and ordering are visible. A radically different privacy model could make this style of global sat tracking much harder or impossible.

And there is a more philosophical limit. Ordinals can identify individual sats, but it cannot force anyone to care. The base layer still sees only spendable outputs and amounts. The significance of a particular sat is always partly social. That is not a flaw so much as the nature of the construction. Ordinals turns Bitcoin units into addressable objects; markets and communities decide which objects matter.

Conclusion

Ordinals is best understood as a deterministic naming system for satoshis. By numbering sats in mining order and moving them through transactions with a FIFO rule, it lets software treat individual sats as persistent objects inside Bitcoin’s ordinary UTXO model.

Everything else follows from that. Inscriptions become possible because content can be attached to a particular sat. Rare sats become collectible because a sat’s position in Bitcoin’s issuance schedule becomes legible.

And the tradeoffs all come from the same source: making previously interchangeable units individually visible.

• larger indexes
• more careful wallet design
• weaker privacy for participating users
• ongoing block-space disputes

If you remember one thing tomorrow, remember this: **Ordinals does not change Bitcoin’s rules. It changes what careful readers of Bitcoin’s existing rules can agree to track. **

How do I buy Bitcoin after learning about Ordinals?

To get practical exposure after learning Ordinals, buy Bitcoin (BTC) on Cube Exchange and hold or move the on-chain sats if you plan to interact with inscriptions. Cube supports funding by fiat or supported crypto, spot trading on BTC markets, and withdrawals to your own Bitcoin address when you need direct on-chain sat control.

1. Fund your Cube account with fiat (bank transfer or card) or deposit a supported stablecoin such as USDC.
2. Open the BTC/USDC or BTC/USD spot market on Cube and choose an order type; use a limit order for price control or a market order for immediate execution.
3. Enter the BTC amount or fiat spend, review the estimated fill, fees, and execution price, then submit the order.
4. If you plan to use Ordinals on-chain, withdraw BTC to a SegWit or Taproot address you control and wait for the recommended confirmation threshold before relying on the received sats for inscription or collector workflows.