> For the complete documentation index, see [llms.txt](https://ordict.gitbook.io/whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ordict.gitbook.io/whitepaper/technology/bitcoin-runes.md). # Bitcoin Runes **Introduction to Runes** Runes introduces a groundbreaking fungible token standard to the Bitcoin blockchain, enhancing the ecosystem with the ability to manage and trade digital assets efficiently. As Ordict integrates Runes, it sets a precedent for the deployment of a versatile token framework that complements the platform's prediction market functionalities. **Runes' Role in Ordict** * **Enhanced Token Flexibility**: Runes tokens provide the Ordict platform with a flexible tool for internal economics, including staking mechanisms, reward distributions, and fee management. This integration allows users to engage in prediction markets with a new level of economic interaction, where tokens can represent stakes in predictions, governance rights, or access to premium features. * **Increased Efficiency of Bitcoin Network**: By adopting the Runes token standard, Ordict leverages a system designed to minimize the creation of unnecessary UTXOs, which are often seen with traditional token implementations on Bitcoin. This approach not only streamlines transactions but also enhances the overall efficiency of the Bitcoin network, leading to faster transaction times and lower fees for Ordict users. * **Security and Stability**: Runes tokens inherit the robust security features of the Bitcoin blockchain, including its resistance to double-spending and its decentralized consensus mechanism. This integration ensures that all token-related activities on Ordict are secure and immutable, providing a stable and reliable environment for users to trade predictions. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://ordict.gitbook.io/whitepaper/technology/bitcoin-runes.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.