Skip to content
Crypto.world

The Ledger

ENS DAO Puts Governor Nexus Upgrade to a Vote After Reversing Audit Poll

ENS DAO is voting on whether to proceed with the Governor Nexus upgrade, after an earlier poll to select an auditor was canceled. The proposed system introduces multiple voting rulesets and safeguards, with an external audit and a separate migration vote still ahead.

ENS DAO Puts Governor Nexus Upgrade to a Vote After Reversing Audit Poll

ENS shifts the vote from auditor to upgrade

ENS DAO’s Governor Nexus proposal asks members to approve the governance upgrade itself, after an earlier Snapshot poll put the audit firm at the center of the decision. The new social vote opened October 29 and runs through November 3. Blockful said the earlier poll was a mistake because it asked the DAO to select an auditor before asking whether to approve the update.

In an October 28 forum update, Blockful explained the distinction between the two decisions:

“The DAO’s decision is whether to approve the Governor update and follow the governance process to ship it.”

Blockful, author of the October 28 ENS DAO forum update

Blockful also wrote: “Our proposal put the audit at the center and left the update itself out of the vote.” The new vote concerns whether the DAO supports proceeding with Nexus; it does not itself deploy the new governor. In an October 30 update, Blockful said the proposal presents quotes from audit firms, with costs ranging from $14,000 to $25,000, and leaves the choice of option to MetaGov.

New rules would change how ENS proposals pass

Governor Nexus is built on OpenZeppelin v5.6.1 and introduces a registry of proposal types, each with its own voting rules. The implementation report names three initial types: Standard, Optimistic and Bond. Standard follows the live ENS ruleset; Optimistic proposals would pass unless opposed by 500,000 ENS, while the Bond ruleset requires a deposit. The report lists a 1,000 ENS bond among migration parameters and says that bond is what the DAO already ratified in EP 5.15. That earlier ratification does not mean the migration is approved: the report says concrete migration parameters still go to a separate proposal for ratification. The optimistic proposer and action allowlists would start empty, so that route would not be available at launch.

The proposal also adds voting safeguards and flexibility. A proposer would initially be limited to two live proposals, with the cap adjustable by governance between one and 10. Anyone could cancel a pending or active proposal if its author fell below the required threshold. Voters could replace their vote before the deadline, and a proposal observed failing during the final 24 hours would receive a 48-hour extension if it is passing at the original deadline.

Audit comes before an executable migration

The audit is a required step, not a completed check. Blockful’s October 30 forum update said quotes from audit firms ranged from $14,000 to $25,000, with MetaGov to decide which option is best. The August implementation report says internal reviews addressed all high-severity findings, but also states that those reviews do not replace an external audit.

If the DAO approves proceeding with Nexus, an external audit would follow, then a separate executable migration proposal. That later proposal would set migration parameters, seek their ratification and move the system on-chain. The existing ENS timelock remains unchanged in the design described by Blockful.

Immutable rulesets leave a governance trade-off

Nexus separates the governor’s proposal lifecycle from the rules that determine voting outcomes. Once registered, a proposal type’s ruleset and parameters cannot be edited in place; governance can activate types, change the default, or register new ones. That design aims to make the rules being voted on the rules that run.

It also places weight on the DAO’s decision to register a ruleset. Blockful’s implementation report warns that an active type can execute actions through the timelock, and a faulty or malicious ruleset can determine which proposals of that type pass. The immediate question for voters is whether the upgrade should proceed to the audit stage; deployment still requires the later migration vote.

Sources

  1. Original source ENS DAO Governance Forum discuss.ens.domains

Other pages read

  1. DAO Radar (Alea Research) governance.alearesearch.io

Related stories

Explore

More articles