What is a protocol parameter change?

It is a governance decision that adjusts a configurable value in a live contract, such as a fee, a collateral factor or a supply cap, without replacing the contract logic.

How is a parameter change executed?

Governance approves a call to a setter function on the target contract. Once quorum, threshold and any timelock are satisfied, that call is broadcast and the new value takes effect.

Should parameter changes have a timelock?

Sensitive ones should. A short delay lets users who are affected by a fee or risk change adjust their positions before it applies.

Execution

Governing protocol parameter changes

Protocol parameter changes shown as governance controlled sliders and dials

Parameters change often and matter immediately. They need a lane that is quick without being unguarded.

Bound the range, then delegate

Let a risk committee move a parameter within a governance-approved band, and require a full vote to move the band.

Publish the rationale with the number

A parameter proposal should state the model, the data and the expected effect, not just the target value.

Watch the aftermath

Set a review date at proposal time so a change that misbehaves is revisited rather than forgotten.

Parameters are the everyday work of governance

Fees, collateral factors, interest curves, reward rates and caps make up the majority of proposals in a live protocol. They are routine, but each one changes economics for real users, which is why they deserve structure rather than informality.

Every parameter proposal should state the current value, the proposed value, the expected effect and the metric that will show whether the change worked. Without the last item there is no way to know when to revert.

Guardrails and cadence

Set bounds so a single vote cannot move a sensitive value beyond a safe range, and require larger moves to be staged across multiple votes with observation between them.

Batch related parameter changes into one execution when they only make sense together. Splitting a coordinated risk adjustment across three proposals creates windows where the settings are inconsistent.

Keep the execution path connected: this guide pairs well with emergency governance action, onchain audit trail and dao tooling, which cover the neighbouring steps between an approved vote and a settled onchain transaction.

Key concepts explained

New to this topic? These are the core terms you will meet again and again in governance work. Understanding them makes every proposal easier to read.

Parameter change: A governed update to a protocol value - a fee, an interest rate model, a collateral factor. Small numbers, huge consequences, which is why they go through full governance.
Bounded parameter: A value constrained to a safe range in code, so even a malicious or mistaken proposal cannot set it to something catastrophic.
Risk parameter: Settings in lending or trading protocols - loan-to-value ratios, liquidation thresholds - where a wrong value can trigger cascading losses.
Staged rollout: Applying a parameter change gradually or to a subset first, so unexpected effects surface before the full protocol is exposed.

Frequently asked questions

What is a protocol parameter change?: It is a governance decision that adjusts a configurable value in a live contract, such as a fee, a collateral factor or a supply cap, without replacing the contract logic.
How is a parameter change executed?: Governance approves a call to a setter function on the target contract. Once quorum, threshold and any timelock are satisfied, that call is broadcast and the new value takes effect.
Should parameter changes have a timelock?: Sensitive ones should. A short delay lets users who are affected by a fee or risk change adjust their positions before it applies.