> For the complete documentation index, see [llms.txt](https://docs.zeta.markets/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.zeta.markets/zeta-x/zeta-x-litepaper/role-of-usdzex.md). # Role of $ZEX The $ZEX token is the governance token of the Zeta Markets protocol, designed to strategically align the interests of our community with the protocol’s overarching goals. We are excited to expand the scope of $ZEX utility beyond governance and incentives (outlined in the token whitepaper [\[2\]](https://zeta-foundation.gitbook.io/zeta-foundation/whitepaper)) through ZX. $ZEX is designed to play a significant role in the ZX rollup infrastructure by facilitating transactions and serving as an incentive mechanism to reward stakeholders performing critical operations. These stakeholders include sequencers who order and produce blocks, full nodes that publish state commitments, and prover nodes that verify state transitions. Beyond rollup infrastructure, we are envisioning further use cases of $ZEX on ZX by offering additional utility to long term stakeholders that stake $ZEX such as exclusive fee tiers. --- # 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://docs.zeta.markets/zeta-x/zeta-x-litepaper/role-of-usdzex.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.