Comment on page

Protocol Specification

Ordinals-compatible, built on Bitcoin SV
Protocol: 1Sat Ordinals
Status: DRAFT


This output script represents an inscription on an ordinal. The output value is 1 satoshi.
OP_FALSE OP_IF 6f7264 OP_1 <content-type> OP_0 <data> OP_ENDIF
This script is then appended to the payment script (typically P2PKH).
<Locking Script> <Inscription Script>
The rest of the Ordinals protocol is identical as it relates to ordinal numbers. See the Ordinals Docs for more information on ordinal theory.

Creating an Inscription

Creating an inscription requires a single transaction. To summarize the transaction template:
Input #1 - Any valid utxo
Output #1 - Locking Script w/ Inscription (1 Satoshi)
Output #2 - Change
The output with this script must lock exactly 1 Sat.

Locking Script

Typically, a P2PKH script is used to lock the ordinal. Simply send the 1 sat output to a new destination to transfer it. From here on, 1SAT_P2PKH refers to a standard p2pkh output with a single sat value, but keep in mind, any locking script can be used.

Inscription Script

Next, inscribe a data file by filling in the two inscription fields, data and content-type. Append the inscription script to the locking script.
OP_FALSE OP_IF "ord" OP_1 <content-type> OP_0 <data> OP_ENDIF


To transfer ownership, simply send a 1sat output to the intended recipient as you normally would with any utxo.
i1 - 1sat_p2pkh
i2 - funding utxo
o1 - 1sat_p2pkh
o2 - change
You can also append to the inscriptions on an ordinal by inscribing the same sat again.
i1 - previously inscribed ordinal
i2 - funding utxo
o1 - 1sat_p2pkh w/ second inscription
o2 - change


In this example, we inscribe a 3d model (GLTF binary) and tag it with a geolocation:
Mint & Inscribe: (1SAT_P2PKH + inscription)


Last modified 16d ago