OP_RETURN Share Trend
Share of OP_RETURN outputs among all outputs created, smoothed over one month. Measures how much of block space carries unspendable data outputs - a channel used by several families of data protocols, and not the Ordinals inscriptions themselves, which travel in Taproot witness scripts.
What is it?
OP_RETURN is the Bitcoin opcode allowing arbitrary data (up to 80 bytes by default) to be inscribed in the blockchain. The output is unspendable - it serves exclusively to carry metadata. This metric computes the 30-day rolling share of OP_RETURN outputs among all created outputs. This channel does not carry Ordinals inscriptions, whose content travels in Taproot witness scripts: the series tracks the protocols that write their metadata directly into an unspendable output, and the upstream classification tags the bulk of the OP_RETURN outputs counted in recent regimes as Runes protocol metadata. These uses move in regime steps, not continuously.
How to read
The vertical axis is a percentage. The series reads in steps: regimes where the channel stays marginal alternate with regimes where a significant fraction of created outputs carries no transferable value. The switch between regimes is fast, on the scale of a few weeks, and the composition of outputs changes along with the level: a high regime corresponds to the arrival of a protocol family that writes massively into OP_RETURN. Levels are not comparable term by term across regimes, because the total number of outputs created over the same window varies too and forms this share's denominator.
Key zones
No fixed empirical threshold. Observed regimes range from marginal use (low share, carried by a few timestamping and anchoring families) to high regimes where a substantial fraction of created outputs are data outputs. A return to a low regime does not mean the end of data-protocol usage: it marks the halt or decline of the protocol that carried the previous regime, not the disappearance of the practice.
What to observe
Watch regime transitions and, at each transition, the composition: which protocol family carries the counted outputs. Cross-reference with #373 OP_RETURN Cumulative Value to distinguish an expansion in output count from a rise in immobilised value, and with the P2TR share (#370/#371) to locate inscriptions, which do not travel through this channel. A softening of the share without a fall in the number of created outputs marks a relative retreat of the channel within block space, not its end.
Historical context
OP_RETURN was standardised in 2014 with an initial 40-byte limit, later raised to 80 bytes by default. The first decade is dominated by timestamping and protocol anchors, with already-high regimes unrelated to inscriptions. The launch of Ordinals inscriptions in January 2023 produces no break in this series: over the following months the share falls instead of rising, consistent with inscription content travelling in Taproot witness scripts rather than OP_RETURN. The high regimes measured afterwards correspond to the arrival of other data protocols, tagged by the upstream classification as the Runes protocol, which carry the bulk of the OP_RETURN outputs counted since.
Expert notes
The OP_RETURN share captures only part of data-protocol usage on Bitcoin, and none of the inscription traffic: inscription envelopes travel in Taproot witness scripts (P2TR script-path). The upstream classification tags the bulk of the OP_RETURN outputs counted in recent regimes as the Runes protocol. A complete reading of inscribed data therefore cross-references this share, the P2TR share (#370/#371) and the total number of outputs created over the same window, which is the share's denominator.
Common mistakes to avoid
Believing OP_RETURN captures the entirety of Ordinals inscriptions is wrong - inscription content travels in Taproot witness scripts (P2TR script-path), and the OP_RETURN share declined while inscriptions were expanding. The series measures the pressure of protocols that write their metadata directly into an unspendable output: it measures neither inscription volume, nor immobilised value, nor human use of the network.
Programmatic access
REST API
curl -sS \
'https://api.trinityinsights.io/api/v1/onchain/metrics/op-return-share-trend/data?timeframe=90d' \
-H 'X-API-Key: $TRINITY_API_KEY'MCP server
{
"tool": "get_chart_value",
"metric_id": "op-return-share-trend",
"timeframe": "1y"
}Required tier: free. See the pricing grid for the tier list and the MCP documentation for multi-client configuration.
Related metrics
Institutional disclaimer
Trinity Insights is an educational and analytical tool. The metric above does not constitute investment advice. Trinity Insights is not a Crypto-Asset Service Provider (CASP) registered under MiCA Regulation (EU) 2023/1114. See the full disclaimer.