# Timelock Certain vault actions that could negatively impact user interests (e.g., increasing leverage limits or modifying risk parameters) are protected by a **timelock**. This ensures users have adequate time to respond, such as withdrawing their funds if they disagree with proposed changes, and offers critical protection if vault owner keys are compromised. **Key Features:** * The **Owner** or **Guardian** can revoke pending actions during the timelock * Timelock durations can range from 0 to a delay of up to 2 weeks (minimum of 24 hours recommended) **Owner Actions Subject to Timelock:** * Vault Upgrades * Oracle Configuration Changes * Ownership Transfer or Renouncement * Gurdian Assignment or Replacement * Reduction of Timelock Duration * Asset Configuration Adjustment : (e.g., adding/removing whitelisted assets, increasing exposure caps) * Lending Pool Configuration Adjustment : (e.g., adding/removing whitelisted pools, increasing exposure limits) * Increasing Leverage Cap #### Vault Upgradability * Affluent Vault is designed to be upgradable to: * Maintain liquidity continuity even if transactions fail, distinct from EVM environments * Support necessary oracle integrations when introducing new assets * After ownership is renounced, a vault becomes non-upgradable and immutable --- # Agent Instructions: 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://docs.affluent.org/strategy-vault/timelock.md?ask= ``` 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.