[Ethereum, Base] Morpho Vault Configuration - January 5, 2026

Spark's Operational Facilitator has placed a proposal into the voting system on behalf of nested contributor Phoenix Labs.

Review

The Spark community can hereby express support or opposition to the following changes, as described by the author of the proposal:

[Ethereum] Spark USDS Morpho Vault - Update Vault Roles

In Morpho vaults, the curator role is responsible for onboarding or offboarding pools and adjusting pool supply caps. This is a critical risk management role, and should be held in a secure manner as theoretically the curator could onboard unsafe pools that would result in losses to vault suppliers. Since launch, Spark has managed all curator functionalities on Morpho vaults under the owner role, which is assigned directly to Spark governance. While this provides maximal security, it also increases workload on the spell process for both Spark and Sky, and can introduce significant delays for accessing new lending opportunities.

We propose to assign the curator role to a multisig to allow greater agility in updating pools and supply caps. To appropriately mitigate risk of a multisig curator, the vault timelocks will be increased from 1 day to 10 days, and a guardian multisig will also be implemented allowing a Sky affiliated multisig to cancel pending actions during the timelock. This means, if a faulty or malicious action is initiated and queued by the curator multisig, either the guardian multisig or Spark and Sky governance would be able to cancel the action during the timelock period. In effect, curation actions will move from an active responsibility of governance to a system of approval by non-objection; vault changes can be implemented under the Spark governance polling and artifact edit process without needing a spell, and action from the guardian multisig or Sky governance is only needed to override faulty curator actions.

The curator role will be set as a multisig composed of Phoenix Labs contributors, with a minimum approval threshold of 3 signers. The guardian role will be set as a multisig composed of non Phoenix Labs contributors, with a minimum approval threshold of 3 signers.

Parameter summary:

• Curator role: multisig address to be provided before executive vote
  • Threshold: 3 of 5
• Guardian role: multisig address to be provided before executive vote
  • Threshold: 3 of 5
• Timelock: 10 days (240 hours)

[Ethereum] Spark Blue Chip USDC Morpho Vault - Update Vault Roles

Similar to above, we propose to update the vault configuration for the Spark Blue Chip USDC vault on Ethereum mainnet to set new curator and guardian roles alongside a longer timelock.

Parameter summary:

• Curator role: multisig address to be provided before executive vote
  • Threshold: 3 of 5
• Guardian role: multisig address to be provided before executive vote
  • Threshold: 3 of 5
• Timelock: 10 days (240 hours)

[Base] Spark USDC Morpho Vault - Update Vault Roles

Similar to above, we propose to update the vault configuration for the Spark USDC vault on Base to set new curator and guardian roles alongside a longer timelock.

Parameter summary:

• Curator role: multisig address to be provided before executive vote
  • Threshold: 3 of 5
• Guardian role: multisig address to be provided before executive vote
  • Threshold: 3 of 5
• Timelock: 10 days (240 hours)

The proposed Spark Artifact changes can be found in the following pull request: https://github.com/sky-ecosystem/next-gen-atlas/pull/154

Outcomes

• If "For" receives the most votes, the proposal will be approved. The associated pull request will be merged into Spark's artifact. When required, the listed changes will proceed to implementation by the relevant actors.
• If "Against" receives the most votes, the proposal will be rejected. No changes will be implemented.