Inscription with MAP

Inscription + MAP

An inscription with a MAP tail after the lock, naming the object's fields.

What it is

The same envelope and lock as any inscription, followed by OP_RETURN and a MAP record. The MAP record holds key-value pairs about the object, such as its name, its collection or its traits. Everything after OP_RETURN is data, so the tail never affects who can spend the output.

Script pattern

  1. OP_DUP OP_HASH160 <pubkey hash> OP_EQUALVERIFY OP_CHECKSIG A P2PKH lock: who owns the object.
  2. OP_FALSE OP_IF "ord" OP_1 <type> OP_0 <data> OP_ENDIF The inscription envelope.
  3. OP_RETURN Ends the script. What follows is data.
  4. "1PuQa7K62MiKCtssSLKy1kh56WWU7MtUR5" The MAP prefix.
  5. "SET" <key> <value> … The object's fields, as pairs.

How it is spent

The owner's signature, as P2PKH.

Background

Collections minted on 1Sat Ordinals commonly use a MAP tail to carry names and traits beside the file.

On chain

Examples coming. They come from the blocks we have typed, and no typed block holds one yet.

Specification