> For the complete documentation index, see [llms.txt](https://hub.bsvblockchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-opcodes/op_return-and-data-storage.md). # OP\_RETURN and Data Storage **Chronicle Release Update:** This chapter has been updated to reflect compatibility with BSV's Chronicle release. All OP\_RETURN functionality remains fully backward compatible with existing scripts. Bitcoin Script includes a special opcode designed not for computation or validation, but for data storage: **OP\_RETURN**. Unlike other opcodes that process values or check conditions, OP\_RETURN marks a transaction output as provably unspendable while allowing arbitrary data to be permanently recorded on the blockchain. Understanding OP\_RETURN is essential for developers building applications that need **to anchor data, create timestamps, or implement token protocols on Bitcoin, ergo the BSV blockchain**. From document verification to complex data structures, OP\_RETURN provides a clean, efficient way to leverage Bitcoin's immutability without cluttering the UTXO set. {% embed url="" %} #### In this course, you will explore: * How OP\_RETURN marks outputs as provably unspendable * The distinction between blockchain storage and UTXO set storage * Common use cases including timestamping, tokens, and data anchoring * Data capacity limits and encoding strategies * Best practices for efficient implementation #### By the end of this course, learners will: * Understand OP\_RETURN's technical function and purpose * Identify appropriate use cases for on-chain data storage * Construct valid OP\_RETURN outputs following network standards * Apply encoding techniques to optimize data storage efficiency --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://hub.bsvblockchain.org/higher-learning/bsv-academy/bsv-opcodes/op_return-and-data-storage.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.