> For the complete documentation index, see [llms.txt](https://docs.ambient.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ambient.finance/governance-and-policy/upgrading-code.md). # Upgrading Code The base layer `CrocSwapDex` contract is built with an upgradeable architecture. New functionality can be added by installing additional proxy contracts. Broken or sub-optimal functionality can be fixed by re-installing existing proxy contracts. With 65,000 slots for unique proxy contracts, upgradeability is practically unlimited. However since all proxy contracts have full access to the DEX contract's state and funds, introducing new code upgrades is an extremely careful process. Only the fully privileged treasury multisig can upgrade code. And then only after an extensive timelock, which gives all users with funds at the DEX time to carefully evaluate their comfort with the newly introduced code. --- # 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.ambient.finance/governance-and-policy/upgrading-code.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.