Skip to main content

OP_RETURN | Bitcoin Glossary | Mapping Bitcoin

OP_RETURN

Protocol

Also known as: OP RETURN, null data output

A Bitcoin Script opcode that marks a transaction output as provably unspendable while allowing up to 80 bytes of arbitrary data to be embedded in the blockchain. OP_RETURN is used for timestamping, asset protocols, and other data-anchoring applications.

Overview

OP_RETURN is a Bitcoin Script opcode that immediately marks a transaction output as invalid for spending. Any output containing OP_RETURN is provably unspendable, meaning the bitcoin sent to it is permanently removed from circulation. However, the output can carry up to 80 bytes of arbitrary data, which is permanently recorded in the blockchain.

How It Works

Standard OP_RETURN output:

  scriptPubKey: OP_RETURN <data up to 80 bytes>
  value: 0 satoshis (typically)

Example uses:
  OP_RETURN "Hello, Bitcoin!"          ← Text message
  OP_RETURN <SHA256 hash of document>  ← Timestamp proof
  OP_RETURN <protocol-specific data>   ← Colored coins, etc.

When a node encounters OP_RETURN during script execution, it immediately returns false, making the output unspendable. Bitcoin Core nodes recognize this pattern and do not add OP_RETURN outputs to the UTXO set, saving memory.

Use Cases

  • Timestamping: Embedding a hash of a document proves the document existed at the time the transaction was mined
  • Commitment schemes: Anchoring the state of external systems (sidechains, databases) to Bitcoin's timeline
  • Asset protocols: Early colored coin protocols and some token systems used OP_RETURN to encode metadata
  • Proof of existence: Services like OpenTimestamps use OP_RETURN to create tamper-proof timestamps

Why OP_RETURN Matters

Before OP_RETURN was standardized, users who wanted to embed data in Bitcoin would create fake spendable outputs (e.g., encoding data as an address). These outputs bloated the UTXO set because nodes could not know they were unspendable. OP_RETURN provided a clean, explicit way to embed data without polluting the UTXO set.

Common Misconceptions

OP_RETURN does not allow unlimited data storage on Bitcoin. The standard relay rules limit OP_RETURN data to 80 bytes, and only one OP_RETURN output per transaction is relayed by default. While miners can include non-standard transactions, the protocol is not designed as a general-purpose data storage system. Ordinals inscriptions use a different mechanism (witness data) for larger data embedding.

Related Terms

OpcodeProtocol

An operation code in Bitcoin Script that defines a specific instruction to be executed on the script stack. Bitcoin has over 100 opcodes covering stack manipulation, arithmetic, cryptographic verification, flow control, and other operations.

Bitcoin ScriptProtocol

A stack-based, non-Turing-complete programming language used to define the spending conditions of Bitcoin transactions. Scripts are embedded in transaction outputs and inputs, enabling features like multisig, timelocks, and hash locks.

TransactionProtocol

A signed data structure that transfers bitcoin from one or more inputs to one or more outputs. Transactions reference previous UTXOs, include scripts or witness data proving authorization, and are broadcast to the network for inclusion in a block.

OrdinalsProtocol

A numbering scheme that assigns a unique serial number to each individual satoshi based on the order in which it was mined. The Ordinals protocol enables inscriptions (data attached to specific satoshis), which has been used to create NFT-like artifacts on Bitcoin.