> For the complete documentation index, see [llms.txt](https://docs.tajirchain.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tajirchain.com/governance/participation-guide/timelock-and-execution-delays.md).

# Timelock & Execution Delays

### After Voting Ends

A proposal can finish in one of two outcomes:

* **Succeeded** (quorum + threshold met)
* **Defeated**

If a proposal **succeeds**, it moves into the **Executable** state.

### Timelock Delay

Some proposals may require a configured delay before they can be executed.\
This delay:

* Prevents sudden or unexpected governance changes
* Gives the community time to review results
* Provides a buffer for security monitoring

If no timelock is configured, the proposal becomes executable immediately after voting ends.

### Execution

Once the timelock (if any) expires, the proposal can be executed.

Execution is triggered by the Guardian Multisig (or the authorized governance executor), and it:

* Runs the proposal’s payload (if included)
* Applies updates to the contract or system state
* Marks the proposal as **Executed**

After execution, the proposal is finalized and cannot be modified.

### Participation Lock Rule (Critical Requirement)

When you vote on a proposal, the locked participation used for voting remains locked until the proposal is resolved.

* You cannot withdraw your participation before the original participation period ends.
* Only the specific participation position used for voting remains locked...
* If multiple participation positions are used, each follows its own participation period.
* Locking applies **per proposal**, based on the snapshot for that vote

This prevents users from voting and immediately withdrawing their participation before the proposal lifecycle is complete.

#### Notes

* Participation locking ensures fair and secure governance participation.
* It prevents manipulation of voting power through early participation withdrawal.
* Execution is completely on-chain and transparent for public verification