> For the complete documentation index, see [llms.txt](https://docs.hashstack.finance/developers/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hashstack.finance/developers/proxy-upgrade-structure.md). # Proxy/Upgrade Structure Given the nature of Hashstack's integrations, there was a requirement to have an upgrade structure robust enough to handle additions of integrations over time and the addition of new functionality frequently, while maintaining previous user balances without the need for migration. Therefore, the Open protocol is designed using the Modular Smart Contract standard, which closely mirrors the Diamond standard outlined in . There are two diamonds: the Open protocol diamond, which contains core Open functionality, and the L3-Integrations diamond, which contains all integration functionality, allowing us to independently add integrations or new functionality in a modular and seamless fashion. --- # 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.hashstack.finance/developers/proxy-upgrade-structure.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.