> For the complete documentation index, see [llms.txt](https://docs.treehouse.finance/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.treehouse.finance/protocol/tasset/security/timelock.md).

# Timelock

All Treehouse contracts are secured by a 5-day timelock, ensuring no critical action executes immediately and giving everyone a clear window to see and respond to upcoming updates.

***

## What Is a Timelock?

A timelock is a built-in delay between scheduling a governance action (like upgrading vault logic or changing fees) and when it actually happens. This pause keeps the protocol transparent and gives everyone time to review or react.

## Why a 5-Day Delay?

* Adequate Notice: A full five days gives users ample time to spot and evaluate any changes.
* Action Window: If you’re uncomfortable with an upcoming update, there’s plenty of time to withdraw your funds.
* Security Hedge: Even if an admin key is compromised, the attacker must wait five days, giving the community or multisig holders time to intervene.

## What This Means for You

* Transparency: Every upcoming change is publicly viewable on-chain.
* Control: You have at least five days to decide if you want to stay in the protocol.
* Safety: The timelock prevents immediate, unreviewed changes and strengthens the protocol’s non-custodial security.

By enforcing a 5-day buffer on all governance actions, Treehouse balances the need for protocol upgrades with strong user protections and clear visibility for everyone.

<br>