Sky governance’s official executive portal records the 5 November proposal as passed on 6 November at 18:52 UTC, with execution available on 9 November at 14:00 UTC. The status is approval, not a claim that the package’s changes are already live.

What the approved package would change

The executive text finalizes offboarding of the GUSD and USDP Peg Stability Modules, authorizes a 900,000-USDS transfer from the Skybase SubProxy to the Skybase Foundation, updates the Safe Harbor Agreement and whitelists specified Spark and Grove proxy spells. The grant uses existing SubProxy funds rather than minting new USDS debt.

For Spark’s allocator, the package doubles the debt-ceiling increase cooldown from 12 to 24 hours. The maximum debt ceiling remains 10 billion USDS and the target available debt remains 1.5 billion USDS. This changes the frequency of increases, not those two limits.

The executive specifies a 48-hour governance pause and weekday execution hours of 14:00–21:00 UTC. Its portal’s displayed 9 November availability is therefore an operational checkpoint, not proof of a completed transaction.

Spark’s cross-chain permissions deserve separate checks

The underlying Spark submission describes a Diamond PAU controller operating alongside the existing Base controller. Its first fund-moving integration would burn USDC on Base for minting to the Ethereum liquidity-management proxy. The legacy CCTP V1 route is described as unchanged, so observers should consider the combined outbound capacity rather than examining the new route alone.

The submission also separates the Ethereum payload from the relayed Base payload. It proposes changes to operator permissions, configuration administration and the authority that administers the integration registry. These are control changes; they do not establish that any particular cross-chain transfer has settled. The submission’s original forum timestamp is 26 October, while its package is labelled for the 5 November executive.

NetNapz assessment: authority, execution and delivery are different

Assessment: the useful new fact is that the executive has crossed the voting stage. A complete follow-up needs to establish when the top-level spell executes, whether downstream payloads execute and whether the intended configuration or recipient balances are reached. One successful stage should not be used as a substitute for evidence about the others.

A longer allocator cooldown can slow how frequently capacity expands, but does not by itself measure actual borrowing, utilization or risk. Likewise, removing legacy module permissions is an administrative action whose effects should be assessed against the affected contracts; the headline does not imply that all GUSD or USDP tokens cease to exist or that holders have received a new redemption guarantee.

Readers monitoring the package should track the execution record and resulting settings after the displayed eligibility time. An approved treasury transfer is not a completed receipt, and an authorized route is not measured liquidity. No token-price response, yield improvement or reduction in losses follows automatically from this governance result.

Sources and verification limits

Checked 6 November: official executive status, full executive specification and Spark’s technical submission. These are project-published records. NetNapz did not connect a wallet, execute a spell, audit the code, independently query live contract settings or verify downstream transfers. This is distinct from the 29 October Osero executive covered earlier.