Bitcoin · Ordinals · 2024

Pizza Ninjas

I led the custom Bitcoin inscription pipeline for the original 1,500-piece collection, then helped build the recursive traits, animation, customization, and games that followed.

Technical lead Pizza Ninja #1 angel artwork with a yellow mask and halo on an orange background
1,500core launch inscriptions
$139.7kSotheby’s sale
Bitcoinexecution layer

Project file

Period2024

Product
A 1,500-piece recursive Ordinals collection with extensible traits, animation, and utilities.
Delivery scope
Inscription orchestration, UTXO and fee control, ordering, retries, confirmation visibility, and the recursive systems that followed.
Public evidence
4public sources1live inscription

Project constraints

  1. 01Permanent writes with no rollback
  2. 02Live fee and mempool movement
  3. 03Strict ordering and dependency control

Ship an ordered collection on Bitcoin while fees, mempool conditions, and immature Ordinals tooling could change underneath the run.

In early 2024, reliable batch tools for Ordinals were still missing. Each inscription carried fees, UTXO state, order, and permanent provenance. A bad retry could duplicate work; a poor fee choice could strand a batch. The launch needed to surface those risks before anything irreversible reached Bitcoin.

01

Manifest-driven ordering

One manifest showed the team what was ready, sent, or confirmed, with each asset tied to its destination and dependencies.

02

Fee-aware batching

Work was grouped into controlled batches and evaluated against live fee conditions instead of assuming one static estimate would survive the full launch.

03

Recursive asset architecture

Shared SVG traits, HTML, and JavaScript are inscribed once and referenced through recursive `/content` endpoints. Each Ninja assembles and runs those on-chain resources in the browser, enabling animation and interaction without duplicating a full application inside every inscription.

04

Recoverable operations

Preparation, broadcast, and confirmation were treated as separate states so incomplete work could be reconciled and resumed without blindly replaying finished inscriptions.

A real inscription

Inspect the on-chain work, not only a screenshot.

Pizza Ninja #1 is not a static image. Its inscription is browser-rendered HTML and JavaScript that resolves shared recursive on-chain assets, runs animation, and can be interacted with directly once loaded.

Pizza Ninja #1 angel artwork with a yellow mask and halo on an orange background
Permanent Bitcoin content External content from ordinals.com loads only after you choose.
Example Pizza Ninja #1
Inscription ID 9ad43b591e58b23d8550dfdae431432b6ea3a7079d09ef80ee1554c5a3f8d543i0
Open the full inscription
  1. 01

    Built the custom orchestration needed to prepare, batch, and track the 1,500-inscription launch when reliable batch tooling did not yet exist.

  2. 02

    Designed the run around UTXO control, live fee movement, ordering, retries, and confirmation visibility.

  3. 03

    Worked on the recursive reference model that turned the artwork into reusable on-chain components rather than 1,500 isolated files.

  4. 04

    Carried the same technical foundation into follow-on utilities, including dynamic traits, animation surfaces, and Pizza Pets.

1,500 inscriptions shipped on Bitcoin. Pizza Ninja #1 later sold for $139,700 at Sotheby’s.

The launch did more than place a collection on Bitcoin. It established an extensible on-chain codebase: the official project now exposes more than 2,000 traits, recursive endpoints, animation utilities, and on-chain emulators. The first piece then crossed into a Sotheby’s Bitcoin Ordinals auction and achieved a $139,700 sale.

  • The original 1,500-piece run shipped through a custom Bitcoin inscription pipeline built for changing network conditions.
  • The recursive foundation grew into traits, animation, customization, emulators, and games.
  • Pizza Ninja #1 entered Sotheby’s Bitcoin Ordinals auction and sold for $139,700.
Bitcoin CoreOrd protocolRecursive inscriptionsSVG trait systemContent manifestsMempool operations
Next case studyProject Spartacus