> For the complete documentation index, see [llms.txt](https://aor.gitbook.io/astra-omnirise/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aor.gitbook.io/astra-omnirise/features/fully-integrated-web3-game-with-btc-ecosystem.md). # Fully Integrated Web3 Game with BTC Ecosystem As a blockchain game pioneer, Astra:OmniRise has adopted a powerhouse combination of Nostr and Bitcoin as its underlying infrastructure, realizing the industry’s first genuinely “playable” on-chain asset system. Astra:OmniRise tokenizes in-game assets into NFTs, leverages state channels for extremely low gas fees, inherits Bitcoin’s security assurances, and supports continuous evolution of the asset system. Such a seamlessly integrated on-chain asset system not only solves the performance and gas fee dilemmas but also enables reliability and security for blockchain game assets. This signals that the new era of technically viable on-chain games has arrived. Moving forward, more exhilarating on-chain gameplay possibilities will be unlocked and discovered. --- # 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://aor.gitbook.io/astra-omnirise/features/fully-integrated-web3-game-with-btc-ecosystem.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.