> For the complete documentation index, see [llms.txt](https://pixer-eternity.gitbook.io/pixer-eternity/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://pixer-eternity.gitbook.io/pixer-eternity/ecosystem/infrastructure.md). # Infrastructure Pixer Eternity full version runs gradually entirely on the blockchain, after the beta version starts with running a centralized application. It will provide a level of trust unlike common traditional applications and allow all users to verify the DAPP's running code, as well as verify all interactions taken place on smart contracts. Pixer Eternity uptime will be 99.99% and we ensure that all features pushed to the Website are produced and deployed smoothly, as well as the Website availability for all players. DDOS attacks can destroy market and leaderboard data, but on the blockchain it can ensure that assets are always safe and DAPPs are always functioning properly. --- # 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://pixer-eternity.gitbook.io/pixer-eternity/ecosystem/infrastructure.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.