The vote cleared its participation threshold

Sky Governance’s Atlas Edit Weekly Cycle poll reported approximately 4.888 billion SKY supporting the proposal and about 2.25 million SKY opposing it. The poll required support to exceed opposition and at least 480 million SKY of positive participation. The associated Atlas pull request 377 was marked merged on 12 November.

The result changes the Sky Atlas, the ecosystem’s governance rulebook. It does not automatically establish that every referenced contract action has executed, that capital has been deposited or that all future spell conditions have been satisfied. The vote and repository merge are the verified outcomes; later allocations and executive actions require their own evidence.

Portal discrepancy: Sky Governance’s detailed poll page reports 4,887,545,086 SKY voting Yes and 2,249,825 SKY voting No, while the portal’s Recent Polls summary currently displays a contradictory “No winner condition met” message. The merged Atlas pull request records the rulebook change on the repository’s main branch. NetNapz therefore treats the detailed vote data and merged repository state as the evidence of adoption, while flagging the inconsistent summary card rather than silently resolving it.

weETH receives an eligibility framework and a shared cap

The merged edit adds weETH as eligible collateral for Morpho vaults used by Sky ecosystem Prime Agents and sets a 60,000-weETH aggregate exposure limit shared between Spark and Grove. The proposal discussion and validation record said 38,317.98 weETH of counted exposure was already associated with SparkLend during review, leaving 21,682.02 weETH under the overall ceiling to be divided between Spark and Grove under the proposal’s accounting.

That ceiling is a governance constraint, not evidence of a 60,000-weETH deposit. The same validation record said no active Spark, Grove or Osero Ethereum Morpho vault then had a weETH market. It also noted that the initial vault caps and the accounting date required careful coordination. Readers should therefore distinguish eligibility and maximum exposure from an active market, current utilisation or committed capital.

The edit also establishes a Morpho-vault curation process. Some changes require governance approval, while qualifying lower-level changes can proceed through disclosure, announcement and reporting rules. A proposed Vault Change Note can replace the fuller Technical Scope Template for eligible changes; where that template is not yet available, the validation record identifies the existing technical template as the working fallback.

The package reaches beyond collateral eligibility

The weekly Atlas package consolidates governance-poll rules, changes how the Demand Side Buffer is replenished through monthly settlement, renames recognised audit-firm categories and places OpenZeppelin, ConsenSys Diligence and Trail of Bits in Category 1. It also records foundation grants, controller functions for a CCTP facet and audit-recordkeeping requirements.

Another group of edits prepares Osero parameters and Base infrastructure ahead of a separately identified 19 November executive vote. The Atlas merge is not proof that this later executive vote has passed or that its spell has executed. The proposal record also describes November grants, but an Atlas authorisation should not be presented as evidence that every transfer has already settled.

Validation found no blockers, but six warnings remain material

The forum’s pinned validator report recorded six passes, six warnings and no failures. The warnings did not block the Atlas merge, but they identify details investors and protocol users should not collapse into a simple “live” label.

Among them, the review said the governance-poll rewrite added procedural rules beyond the headline summary, the Demand Side Buffer language included details not disclosed in the short description, and some Osero wording depended on later contract registration or the 19 November spell. It also treated the proposed Osero capital-requirement and maximum-exposure settings as conditional on that later action.

Those findings do not reverse the vote. They show why the scope of the verified outcome is the rulebook change itself. Contract registration, executive execution, vault deployment and asset movement should each be checked separately when they occur.

NetNapz assessment: governance capacity is not deployed exposure

NetNapz assessment: the most consequential immediate change is the combination of a shared weETH exposure ceiling and a formal process for curating Morpho vaults. The framework gives governance a documented limit and a route for reviewing later vault changes, while leaving operational execution to subsequent steps.

The 60,000-weETH figure is therefore best read as a system-wide maximum under the approved framework, not as a current balance, investment commitment or forecast of demand. The economic effect will depend on which markets are actually enabled, how much capital is allocated, the terms applied to each vault and whether later executive actions pass and execute.

Verification scope: NetNapz checked the official polling page, the merged Sky Atlas repository record, the proposal discussion and Sky’s public description of its vault interface. We did not vote, connect a wallet, inspect private governance communications or verify any live vault allocation. No claim is made about SKY price, guaranteed yield or the availability of a particular product in every jurisdiction.

Sources checked

• Sky Governance: Atlas Edit Weekly Cycle Proposal, 9 November 2026
• Sky Ecosystem: Atlas pull request 377, merged 12 November 2026
• Sky Forum: proposal discussion and validator report
• Sky.money: public vault and governance-token descriptions