> For the complete documentation index, see [llms.txt](https://litepaper.pixels.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://litepaper.pixels.xyz/usdpixel-whitepaper/rors.md). # RORS Central to the success of Pixels is our pioneering metric: Return on Reward Spend (RORS). \ \ RORS measures the direct economic impact of rewards distributed to players. It is analogous to ROAS - Return on Ad Spend - it is a very simple measurement comparing the amount of rewards distributed to the amount of revenue a protocol recieves back in fees.\ \ Currently around \~0.8, our clear and ambitious goal is surpassing a RORS of 1.0, meaning every reward token spent generates net-positive revenue for the ecosystem. Achieving RORS > 1.0 solidifies our economic sustainability and positions Pixels as the leader in efficient, effective player rewards. --- # 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://litepaper.pixels.xyz/usdpixel-whitepaper/rors.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.