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