Welcome to the next crypto level
← Nexorena

DeFi

Morpho’s MidnightAdapter vote falls short of quorum

Proposal MIP 136 received about 253,945 units of voting power, all in favor. The threshold on Snapshot was 500,000. The proposal sought to list the adapter subject to audit conditions.

Nexorena Editorial Team

Morpho’s MidnightAdapter vote falls short of quorum

Unanimous support below the required threshold

The vote on listing MidnightAdapter in the Morpho Registry closed on November 22 at 7:09 a.m. UTC with about 253,945 units of voting power in favor. The record for proposal MIP 136 in Morpho’s official Snapshot space shows 15 participants and no votes against or abstentions. It lists a quorum of 500,000 units, just over half of which was reached.

The vote opened on November 19 and concerned an adapter intended for Vault V2 curators. The result distinguishes two aspects of the vote. All voting power cast went to the option in favor. The total nevertheless fell below the decision threshold, by about 246,055 units of voting power. This ballot therefore did not supply the governance approval that the proposal called for before listing.

A connection between Vault V2 and Midnight markets

In its proposal published on the governance forum on November 11, the Morpho Association describes MidnightAdapter as a way to allocate liquidity from a Vault V2 directly to Morpho Midnight markets. The registry listing would have applied to the adapter providing that option to curators. The proposal sets neither an allocation amount nor a distribution of liquidity by market. Those decisions concern how curators might use the adapter once available.

The Morpho Registry lists adapters approved by its governance. Under the proposed procedure, the association would deploy MidnightAdapter on the chains where Morpho Midnight is present, and the DAO multisig would then add it to the registry on each of those chains. The vote was intended to authorize that process, which had separate deployment and listing steps.

Code reviews remain a separate condition

The text sought conditional approval ahead of the end of the security reviews. Before any deployment under MIP 136, the reviews cited in the proposal were to be completed, findings addressed, and fixes incorporated into the final version. The association was also to publish the reviewed code, the corresponding commit hash, and the audit reports in the governance thread. Those items would allow readers to match the announced version with the one reviewed.

The proposal mentions audits and a public audit contest. The Snapshot tally records support and participation. The governance thread sets out the proposed technical conditions. Establishing a change in the adapter’s status would call for new evidence of a decision and, if the process described in MIP 136 is followed, a record of deployment and actual registry listing. The November 22 vote leaves that step open. The available text gives neither a date for a new vote nor a timetable for a new listing. The result describes the state of the proposal when the vote closed.

Article sources

Written with love byEthan BrooksMeet this editorial pen name ↗

Explorer Nexorena