> For the complete documentation index, see [llms.txt](https://docs.dydx.community/dydx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dydx.community/dydx/modules/distribution/protocol-revenue-sharing.md). # Protocol Revenue Sharing On August 12, 2024, dYdX Trading Inc. [announced](https://dydx.exchange/blog/dydx-unlimited-coming-this-fall) dYdX Unlimited, software featuring significant improvements to the dYdX Chain open-source software, including potential revenue sharing, among other things. Protocol Revenue Sharing enables the dYdX community to use `MsgUpdateUnconditionalRevShareConfig` to adjust the allocation of net revenue received by the protocol with addresses other than the Distribution module account (which distributes to validators, stakers, and community pool). On November 13, 2025, the dYdX community [approved](https://www.mintscan.io/dydx/proposals/313) the following distribution: * 75% revenue sharing to the Buyback Program, * 5% to Treasury SubDAO, * 5% to MegaVault, and * 15% to the Distribution module account. --- # 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.dydx.community/dydx/modules/distribution/protocol-revenue-sharing.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.