Timelocked Parameters
How timelocks protect users from sudden configuration changes
Critical protocol parameters are protected by timelocks. When the owner wants to change a parameter, they first queue the change. After a mandatory delay (CONFIG_DELAY = 1 hour), the change can be applied. This gives users time to review and react.
Timelocked Parameters
| Parameter | Queue Function | Apply Function |
|---|---|---|
| Global Slippage | setSlippageBps() | applySlippageBps() |
| Cycle Threshold | setCycleThresholdBps() | applyCycleThresholdBps() |
| Engine Version Upgrade | queueEngineVersion() | activateEngineVersion() |
The queue-state view surface lives partly on HelioxConfigs and partly on HelioxEngineRegistry. Config queues expose pending values and ETAs directly. Engine upgrades use the registry's queued-version state.
Engine Upgrade LifecycleThe governed module lifecycle is documented once on the Engine Families page. This page focuses only on the timelock boundary and where to read queued state.