What is a Cooldown Period?
A cooldown period is a mandatory waiting interval between initiating an action and its completion in blockchain protocols. While similar to unbonding periods in staking, cooldowns appear across DeFi in various contexts. From unstaking to governance to security mechanisms.
Cooldowns in Staking
Many staking protocols implement cooldown periods before users can withdraw their staked assets. For example, Aave's Safety Module requires a 20-day cooldown before AAVE tokens can be withdrawn after initiating unstaking. This differs from network-level unbonding as it's enforced by the protocol's smart contracts.
Purpose of Cooldowns
Security: Cooldowns prevent rapid extraction of funds during exploits, giving time to respond to attacks or detected vulnerabilities. Stability: Gradual changes to protocol state prevent sudden liquidity crises or governance manipulation. Commitment Signaling: Longer cooldowns indicate stronger commitment from participants, aligning incentives. Penalty Enforcement: Time delays allow for detection and application of penalties before funds can escape.Cooldowns in Governance
Governance proposals often include cooldown periods between stages. Submission to voting, voting to execution. This gives stakeholders time to review, discuss, and potentially veto harmful proposals. Timelock contracts enforce delays between approval and execution.
Protocol-Specific Examples
- Aave Safety Module: 20-day cooldown for stkAAVE
- EigenLayer: 7-day escrow period for unstaking
- Convex: 16-week lock for maximum voting power
- GMX: 1-year vesting for esGMX rewards
Managing Cooldown Risk
During cooldowns, assets may still be at risk but often don't earn rewards. Market conditions can change significantly during long cooldowns. Factor these periods into yield calculations and liquidity planning.
Cooldown vs Unbonding vs Timelock
These terms are often used interchangeably but have nuances. Unbonding typically refers to network-level staking. Cooldown often describes protocol-level waiting periods. Timelocks specifically delay governance execution. Understanding the distinctions helps navigate different protocols.