ENS: a vote to select OpenZeppelin to audit Governor Nexus

The vote, as read on 28 October 2026

• For39.4k100%
• Abstain00%
• Against00%

Voting power, not people: 20 votes cast.

blockful, which wrote Governor Nexus, posted a Snapshot vote on 26 October 2026 asking token holders to select OpenZeppelin as the contract's external auditor. The vote, labelled [Social] [7.3] Select OpenZeppelin to audit Governor Nexus, points to blockful's own implementation report thread on discuss.ens.domains as its discussion. The vote runs until 31 October 2026; as of 28 October it had 20 votes cast and no opposition. Governor Nexus is ENS's rebuilt governor contract: as blockful describes it, "Governor Nexus is built on OpenZeppelin v5.6.1. The core is composed from the standard audited Governor modules," with blockful's own code layered on top to add a vote-governed proposal-type registry, three rulesets named Standard, Optimistic and Bond, mutable votes, and a late-vote extension. The vote matters because the proposal makes an external audit the condition for any deployment proposal: it picks who checks the code before delegates are asked to put it live.

What it changes

• This vote does not change Governor Nexus's code; it selects who audits it and releases the budget to pay for that audit.
• Auditor: OpenZeppelin, which wrote the base Governor contracts Nexus extends and was also the recommended auditor in EP 5.15, which the proposal calls the last governor change the DAO discussed.
• Scope: the Governor Nexus contracts exactly as published in blockful's August 2026 implementation report, with no changes since, covering the proposal-type registry, the Standard, Optimistic and Bond rulesets, mutable voting, and the late-vote extension.
• Funding: paid by the Meta-Governance Working Group from the contract-audits line of its Term 7 budget; the proposal makes no new funding request to the DAO, and gives no dollar figure for the audit's cost.
• A vote For approves OpenZeppelin as auditor; a vote Against sends blockful back to the other options with the MetaGov stewards. The August report had named Trail of Bits alongside OpenZeppelin, and three firms returned quotes.
• If it passes, MetaGov releases the funds and schedules the audit with OpenZeppelin; once the audit is done, blockful publishes the report and its fixes, then posts a separate deployment proposal, which needs its own vote, to actually put the audited contracts live.

The case for it

blockful's stated reason is direct experience with the underlying code: "OpenZeppelin wrote the Governor code that Nexus builds on, so their team already knows the base contracts our changes extend." The proposal also points to community input gathered during the implementation report's feedback window: in that thread, nick.eth wrote that "OZ would definitely be my top choice here, by a fair margin."

The objections

The clearest open question came after the vote went live. On 27 October 2026, nick.eth replied to the implementation thread asking about the budget: "I don’t see any mention of the cost of the audit here?" The Snapshot proposal names the funding source but not an amount, so as of 28 October 2026 that question has not been answered in the thread. blockful's August report said it would publish the firms' quotes alongside the audit proposal, and its 24 September update said quotes had come back from three firms and that the proposal would carry "the firm, the scope and the price".

Where it stands

The Snapshot vote runs from 26 October 2026, 17:37 UTC, to 31 October 2026, 17:37 UTC. As of 28 October 2026 it had drawn 20 votes, all of them For, totalling about 39,403 ENS of voting power, with none Against or Abstain. If it passes, the next step is OpenZeppelin's audit, followed by a separate deployment proposal to put the audited Governor Nexus contracts live.