> For the complete documentation index, see [llms.txt](https://docs.nodeset.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nodeset.io/constellation/treasurer.md). # Treasurer To better fit the real-world separation of responsibilities between fee owners and service providers, there is a role that specifically exists to manage protocol-wide revenues generated by xrETH and xRPL: the Treasurer. From a smart contract perspective, the Treasurer is simply an address which receives these revenues. Its only other capability is to change the current Treasurer address to point to another address. This role allows Constellation to fit many different types of organizational architectures. For example, the Administrator may be one segment of a DAO made up of the system’s Operators, and the Treasurer could be a secondary element of the same DAO that is responsible for protocol-wide incentives or marketing. Ultimately, the flexibility afforded by the separation of Administration, node operation, and collective fee aggregation makes Constellation a better foundation for any kind of second-layer staking project on Rocket Pool, strengthening its value as a public good. --- # 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.nodeset.io/constellation/treasurer.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.