> For the complete documentation index, see [llms.txt](https://flint-rwa.gitbook.io/flintrwa-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://flint-rwa.gitbook.io/flintrwa-docs/technical-architecture/upgradability.md).

# Upgradability

## Proxy architecture

Lagoon vaults use transparent upgradeable proxies built from three components:

1. **Proxy contract** — the main entry point users interact with
2. **Silo helper contract** — manages the deposit and redemption silos
3. **DelayProxyAdmin** — enforces mandatory waiting periods before upgrades apply

## How upgrades work

```
Vault Admin proposes upgrade to a whitelisted implementation
        |
        v
Waiting period (24 hours minimum, 30 days maximum)
        |
        v
Upgrade applied
```

The waiting period gives depositors time to review what's changing and exit before it takes effect if they want to. It's the same logic as a timelock in governance contracts.

## Whitelisted implementations only

Vault Admins can only upgrade to implementations pre-approved by Lagoon through the ProtocolRegistry. Arbitrary code can't be pushed into a live vault.

## Going immutable

A vault can be made permanently immutable by renouncing ProxyAdmin ownership. This is irreversible. Once done, no further upgrades are possible by anyone.

***

*Back to:* [*Architecture Overview*](/flintrwa-docs/technical-architecture/architecture-overview.md)


---

# 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:

```
GET https://flint-rwa.gitbook.io/flintrwa-docs/technical-architecture/upgradability.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.