ENS DAO’s “Governor Nexus Update” vote runs until November 3. The code behind it, built on OpenZeppelin v5.6.1, targets weaknesses that ENS’s own governance assessment rated critical, including a voting delay of a single block.
The current vote is a social one, though: an external audit and a separate executable vote still have to come before anything changes on-chain.
Most ENS token holders have probably never noticed that a proposal to the DAO can open for voting one block after it is submitted. That gives delegates about 12 seconds to coordinate before votes can be cast.
That one-block window is one of five weaknesses Governor Nexus is designed to fix. Governor Nexus is a replacement for the governor contract ENS has used since 2021. Delegates are voting on it this week.
The short coverage so far reports a list of features and leaves out what kind of vote this is. On ENS’s governance portal, Agora, “Governor Nexus Update” is listed as [7.3] [Social], a Snapshot vote that closes on November 3. It signals support for the design. It doesn’t deploy a contract or move control of the DAO’s timelock.
What This Week’s Vote Does And Does Not Do
Governor Nexus comes from Blockful, an ENS service provider. It was first set out in a March request for comments, which described it as a way to “modernize the ENS Governor while preserving full compatibility with the existing Timelock contract.” An implementation report followed on August 19, along with public code in Blockful’s nexus repository.
According to that repository, the new governor is rebuilt on OpenZeppelin Contracts v5.6.1. The live governor is an older OpenZeppelin v4, Bravo-style contract with every setting fixed at deployment. The team says the core “is composed from the standard audited Governor modules,” and that it wrote custom code only where OpenZeppelin has no equivalent.
The process has three steps:
- This week’s social vote: it signals support for the design.
- An external audit: a separate Snapshot vote, “Select OpenZeppelin to audit Governor Nexus,” closed on October 31.
- An executable migration proposal: only this can hand the timelock to the new contract. Reports of the proposal say migration proposals will use a two-day voting delay.
The “audit” mentioned in early reports is not a completed code audit. It refers to the RFC’s security assessment under the Anticapture framework, which rates ENS’s current setup at Stage 0. Blockful says the new design would move ENS to Stage 1.
The One-Block Window And The Proposal Flood
Blockful’s README lists three weaknesses in the live governor as critical. Two concern how a hostile proposal could get through before delegates have time to react.
- The voting delay. The live governor’s delay is one block, which leaves almost no time to coordinate before voting begins. Governor Nexus makes the delay a setting for each proposal type, and the README says “the migration raises it by governance, with no code change.”
- Proposal spam. Today, nothing stops an attacker from submitting proposals until delegates give up. The README calls this a “war of attrition.” Governor Nexus caps how many proposals one address can have open at once:
-
- The cap starts at two. Governance can set it anywhere from one to 10.
- Only proposals still pending or in voting count toward it. Queued, defeated, cancelled or executed proposals free up a slot right away.
The developers acknowledge one limit. Like the existing 100,000 ENS proposal threshold, the cap applies per address, so it doesn’t stop an attacker who spreads voting power across several wallets.
Closing The Last-Minute Flip
The best-known change is the anti-snipe extension. The README rates the missing safeguard as medium severity: “last-minute flips can pass without response time.”
The new rule: if a proposal goes from failing to passing in the final 24 hours, voting is extended once by 48 hours. Two details in the code make this harder to game.
- The extra time is fixed. The 48 hours are counted from the original deadline, not from when the flip happens, so timing a flip later “buys no extra calendar time.”
- The trigger can’t be switched off by manipulating the tally. The rule doesn’t react to a single moment when a proposal crosses the line. Instead, the governor records whether the proposal was seen failing at any point in the final window, and checks whether it is passing at the original deadline. The only way to avoid the extension is to keep the proposal visibly passing for the whole final 24 hours, which is exactly the time the rule is meant to give the community to respond.
Votes That Can Be Changed, And Proposers Who Must Stay Funded
The third critical weakness concerns proposers. Under the live governor, someone can submit a proposal and then sell or move their tokens right away. Governor Nexus treats the proposal threshold as a continuing requirement. If a proposer’s voting power falls below their proposal type’s threshold while the proposal is still pending or in voting, anyone can cancel it. The code says even a one-block dip counts.
Voters can also change their votes. Under the live governor, a vote is final once cast. Under Governor Nexus, voting again on an open proposal replaces the earlier vote. The README addresses the risk this fixes, “no correction path if a voting interface is compromised,” which it rates medium. Changeable votes also mean a tally can move both ways before the deadline. That is part of why the anti-snipe rule looks at the whole final window rather than a single moment.
Other changes:
- Batch voting: delegates can vote on several proposals in one transaction.
- Per-proposal signature nonces: a signed vote held by a relayer can’t be replayed to override a voter’s later choice.
- Higher gas costs: on the team’s mainnet-fork benchmark, proposing costs about 23,700 more gas and voting about 28,900 more gas than on the live governor.
Two New Ways To Propose
Governor Nexus replaces the single proposal path with three proposal types, each with its own rules.
Standard works like today’s governor: a 100,000 ENS voting-power threshold, a simple majority and a quorum of 1% of supply.
Optimistic proposals pass unless 500,000 ENS votes against them by the deadline, with no quorum required. To limit the risk:
- Only allowlisted proposers can use it, and only for allowlisted function calls.
- No action can send ETH.
- Both allowlists start empty, so on day one the path can do nothing.
- An optimistic proposal can never target the governor, the timelock or the ruleset itself.
The README also notes a gap that the anti-snipe rule covers: under changeable votes, a veto can be withdrawn at the last moment. That counts as a failing-to-passing flip, so it triggers the 48-hour extension.
Bond proposals let anyone propose by locking 1,000 ENS instead of holding 100,000 ENS in voting power. Voters get a fourth option, “Against and Slash.” The bond is forfeited to the treasury only if rejection beats support and the slash votes outnumber plain “Against” votes. That rule follows the predicate the DAO approved in EP 5.15.
Blockful lists the trade-offs openly:
- Whale force-slash: a large holder can confiscate an honest proposer’s bond.
- Zero-turnout grief: if nobody else votes, a single tiny “slash” vote takes the bond.
- Whale shield: a large holder can also protect the proposals they back.
What Happens After November 3
A yes on the social vote doesn’t change the live governor. The contract’s own documentation sets out what comes next:
- the external audit
- an executable proposal to deploy Governor Nexus and hand it control of the existing ENS timelock
- governance actions to set the new voting delays and fill the optimistic allowlists
Until those steps are done, ENS runs on its 2021 governor, with the one-block delay and fixed votes that this week’s vote aims to replace. ENS isn’t voting on the contract itself this week. It is voting on whether to start the process that leads to one.
Disclosure: This is not trading or investment advice. Always do your research before buying any cryptocurrency or investing in any services.
Follow us on Twitter @themerklehash to stay updated with the latest Crypto, NFT, AI, Cybersecurity, and Metaverse news!