Inscriptions

An inscription is arbitrary content — an image, text, JSON, even small applications — stored directly on the Bitcoin blockchain inside a transaction's witness data and bound to a specific satoshi through the Ordinals protocol. Inscriptions piggyback on two earlier upgrades: SegWit (2017), which moved signature data into a separate witness section with its own fee accounting, and Taproot (2021), which made it practical to embed larger payloads in spending scripts. The result is on-chain digital artifacts that live entirely within Bitcoin — no external storage, no sidechain, no separate token contract — replicated by every archival node on earth.

The commit-reveal pattern

Creating an inscription takes two transactions. The commit transaction creates a Taproot output whose script tree contains the inscription content wrapped in an "envelope" — a construction of the form OP_FALSE OP_IF ... OP_ENDIF that consensus rules treat as provably unexecuted script, meaning the data can never affect spending logic. The reveal transaction then spends that output, exposing the script and writing the content into the witness section of the blockchain permanently. Because witness bytes receive the SegWit fee discount relative to ordinary transaction data, inscribing a file costs roughly a quarter of what the same bytes would cost in legacy space — though still real money, and multi-hundred-kilobyte inscriptions have paid substantial fees. Ordinal theory then assigns the inscription to the first satoshi of the reveal transaction's first output, letting it be tracked, held, and transferred like any other coin.

Operational impact on miners and the mempool

Inscription waves have repeatedly and sharply raised mempool congestion and fee rates, and that matters directly to anyone running hardware. Fees are the variable slice of miner revenue on top of the block reward, and inscription demand has at times pushed fee income to levels that meaningfully improved mining margins — a preview of the fee-driven security budget Bitcoin must eventually rely on as subsidies halve away. A home miner watching fee estimates should understand that inscription mints, not only monetary payments, can drive those spikes; a lucky solo-mining block found during an inscription frenzy pays noticeably more than the subsidy alone.

The debate, plainly

Inscriptions are contentious, and both sides have a real point. Critics argue they consume block space for non-monetary data, price out ordinary transactions, and bloat the chain that every node must store; some proposed filtering them at the relay level. Supporters respond that inscriptions pay full market-rate fees under the same consensus rules as everyone else, and that Bitcoin's neutrality — the property that miners and nodes do not judge what a valid, fee-paying transaction is for — is precisely what makes it censorship-resistant money. In practice, filtering attempts have limited effect, since miners have a direct financial incentive to include whatever pays.

The wider asset landscape

For node runners, the storage story is more nuanced than the alarm suggests. Inscription data lives in the witness, so a pruned node discards it along with the rest of historical block data, and it never enters the UTXO set that every node must keep hot — the design channels arbitrary data into the cheapest, most discardable part of the chain. Archival nodes do carry the full weight, and initial sync grows accordingly, but the resource that actually gates running a node long-term was deliberately protected by the same witness structure inscriptions exploit.

Inscriptions are the mechanism behind the BRC-20 token standard, which encodes token mints and transfers as JSON inscriptions, and they sit alongside the newer Runes protocol as competing approaches to issuing assets on Bitcoin. D-Central presents these neutrally as part of the evolving base-layer landscape: whatever one thinks of JPEGs on the timechain, the fees they pay flow to the machines securing it.