Privilege Constraints

Evaluates how easily privileged actions can be executed and how much time the community has to respond. Quorum thresholds, timelock durations on non-upgrade/non-mint actions, and active monitoring are the primary inputs.

Tier	Reasoning	Evidence
Weak quorum and minimal timelocks	Quorum thresholds and timelock durations determine how easily privileged actions can occur and how much time the community has to detect and respond. Weak settings mean privileged actions execute essentially on demand.	Beanstalk's emergencyCommit ($182M) bypassed timelocks entirely for supermajority proposals, demonstrating how weak constraints collapse the response window to zero.
Moderate quorum and partial timelocks	Moderate quorum and partial timelock coverage raise the bar for privileged execution but leave gaps — either in the threshold required or in which actions are delayed — and offer no protection where the proposal queue is unmonitored.	Moonwell (March 2026) showed that a 48-hour timelock provided no protection because no one monitored the proposal queue.
Strong quorum, meaningful timelocks, community veto	Strong settings — high quorum, meaningful timelocks on non-upgrade non-mint privileged actions, public visibility of pending actions, and active monitoring — convert privileged execution from a top-down to a contestable process.	Lido's dual-governance structure, where on-chain actions entering execution can be challenged by stakeholders who trigger dynamic delay mechanisms, anchors the best tier.