# SAEP-24: Update Risk Curation Framework

- Space: [Spark](https://snapshot.box/s:sparkfi.eth.md)
- Author: 0xF97c00fab22A45eB27163D0f0065Da00Da10624B
- State: Passed
- Voting type: Basic
- Start: 2026-10-19 16:16 UTC
- End: 2026-10-22 16:16 UTC
- Votes: 5
- Discussion: https://forum.skyeco.com/t/saep-24-update-risk-curation-framework/28301
- Open in Snapshot: https://snapshot.box/#/s:sparkfi.eth/proposal/0x41bb0aa96e451bbe44ebbd3bb948540c911bbd39ce123e41c5901a532f94d9c7

## Results

- For: 629,941,436.97 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

# SAEP-24: Update Risk Curation Framework - October 19, 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:

### Summary

The proposal recommends that Spark governance amend the [A.6.1.1.1.3.9 - Risk Curation Framework](https://sky-atlas.io/#78018ebc-c69d-44f6-b602-190edca11483) to do four things:

- Give standing approval, without a governance poll, to a closed list of risk-reduction actions taken by a Curator: reducing a cap, removing an account from the Allocator role or any other role that can allocate funds or increase a cap, and cancelling a pending change in accordance with the existing Cancellation Reasons.
- Allow a cancellation authority holder ([A.6.1.1.1.3.9.6.3](https://sky-atlas.io/#900c4a0d-ed93-41ad-b914-f84d50d6940e)) to reduce a cap or deallocate funds where its role permits, for the existing Cancellation Reasons ([A.6.1.1.1.3.9.6.2](https://sky-atlas.io/#0e572cad-bdf2-437f-b272-0cd634424b19)) other than a request by the Curator.
- Amend the Timelock Requirement ([A.6.1.1.1.3.9.5.1](https://sky-atlas.io/#9cb30c4c-ecbb-4874-a931-b900b868b888)) so that, for every function addressed by the Sky timelock requirements for Morpho vaults and adapters ([A.2.2.10.1.1.1.3.3.1](https://sky-atlas.io/#14aba6cb-eb34-4780-84c1-908666835569) and [A.2.2.10.1.1.1.3.3.2](https://sky-atlas.io/#91ba9acf-6ed7-4214-8b6b-adfb03427ae1)), the Sky requirement applies in place of the framework's three (3) day minimum. The minimum is kept for every other function, and cancellations, cap reductions, and deallocations are exempt from it.
- Remove the Spark USDS Morpho Vault from the approved instances ([A.6.1.1.1.3.9.7.2.1](https://sky-atlas.io/#3e8ed24b-da4a-4c3f-9a74-c3dd6a557abf)), since the Spark Liquidity Layer can no longer deposit into or withdraw from it, and correct the Curator recorded for three of the remaining instances to Soter Labs and Spark. 

The proposal does not change any on-chain contract, role holder, timelock value or cap value, the Cancellation Reasons, or the Cancellation Authority or Allocator recorded for any approved instance. It does not change the Spark Liquidity Layer instance configuration for the Spark USDS Morpho Vault.

### Background

#### The Polling Requirement

The Polling Requirement ([A.6.1.1.1.3.9.4.1](https://sky-atlas.io/#218f889f-6a5d-46a8-b8a3-cb0a075825c2)) requires every Curator-executed change to be approved by poll before implementation, regardless of the direction of risk, so a Curator wanting to cut exposure to a deteriorating market must wait for a poll. 

#### The Cancellation Authority

The framework treats the Morpho Vaults v1 Guardian and Morpho Vaults v2 Sentinel as one cancellation authority whose only function is cancelling pending changes. The Guardian can only revoke pending changes, while the Sentinel can also call `decreaseAbsoluteCap`, `decreaseRelativeCap` and `deallocate`, which the framework does not address.

#### The Timelock Requirement

The Sky timelock requirements ([A.2.2.10.1.1.1.3.3.1](https://sky-atlas.io/#14aba6cb-eb34-4780-84c1-908666835569) and [A.2.2.10.1.1.1.3.3.2](https://sky-atlas.io/#91ba9acf-6ed7-4214-8b6b-adfb03427ae1)) conflict with the framework's three (3) day minimum in three places: adding or removing an allocator and setting the force deallocate penalty must not be subject to a timelock delay, and cap decreases may be executed without delay.

#### Approved Instances

The Spark Liquidity Layer deposit and withdraw rate limits for the Spark USDS Morpho Vault ([`0xe41a0583334f0dc4E023Acd0bFef3667F6FE0597`](https://etherscan.io/address/0xe41a0583334f0dc4E023Acd0bFef3667F6FE0597)) are set to zero. The residual balance of about 22 USDS would cost more to recover than it returns, and can be recovered in a later spell if Spark governance so chooses.

The Spark Blue Chip USDC, Spark Blue Chip USDT and Spark USDC (Base) records name only Soter Labs as Curator, although the 2-of-2 Curator multisig ([`0x0f963A8A8c01042B69054e787E5763ABbB0646A3`](https://etherscan.io/address/0x0f963A8A8c01042B69054e787E5763ABbB0646A3)) is controlled by Soter Labs and Spark. 
*This item is dependent on the approval of the curator Safe configuration ratification poll requested by Phoenix Labs in [this post](https://forum.skyeco.com/t/technical-scope-spark-guardian-and-curator-multisig-key-rotations/28281/5) and submitted in parallel to this proposal in the Oct 19th cycle.*

### Proposal Details

To implement the changes above, the proposal:

- Adds a new section A.6.1.1.1.3.9.4.3 - Risk-Reduction Actions under the Governance Approval Process, and amends [A.6.1.1.1.3.9.4](https://sky-atlas.io/#e3ddbd39-ee57-4b17-b66e-8bc823a03098) and [A.6.1.1.1.3.9.4.1](https://sky-atlas.io/#218f889f-6a5d-46a8-b8a3-cb0a075825c2) to refer to it.
- Amends Scope of Authority, the Scope of Curator Authority instance parameter, and that field of each remaining instance record to define governance approval by reference to the Governance Approval Process.
- Removes the Spark USDS Morpho Vault instance record and renumbers the four remaining records.
- Amends Reporting of Curator Actions so that the report for a risk-reduction action states which listed action was taken in place of a governance poll, and gives a timelock expiry only where the action has one.
- Names the Spark Prime category of the forum as the location for reports under Reporting of Curator Actions and Cancellation Authority Reporting ([A.6.1.1.1.3.9.6.3.2](https://sky-atlas.io/#ac45b63b-3394-49d6-aab7-ff67b1d4fd0c)).

### Justification

**A risk-reduction action should not wait on a poll.** A poll remains the rule for anything that can add risk, but for an action that can only lower exposure, it adds delay without protection. A reduction made in error costs lower yield or idle liquidity until a later poll restores it (a cap restoration also waits out the vault's seven (7) or ten (10) day timelock); a reduction made late can cost depositors a loss.

**The list is closed**, so the Curator does not have to judge under time pressure whether an action counts. Timelock increases are excluded because a longer timelock also delays the next risk reduction. Removing an account from a Guardian or Sentinel role is excluded because it removes a holder whose powers are used to cancel or cut exposure. Any other change submitted together with a listed action still requires a poll.

**Reporting still applies.** Every risk-reduction action is reported within 24 hours, naming the listed action taken, and can be reversed through the normal polling process.

**Cancellation authority powers stay bounded.** A cancellation authority holder can reduce caps or deallocate only for reasons the framework already recognises: misalignment with the Sky Atlas or Spark Artifact, excessive or unacceptable risk as identified by the Sky Core Council, and an emergency under the Sky Atlas. Excluding Curator requests stops the Curator directing a holder to deallocate funds, which its own list does not permit. This matters only for Morpho Vaults v2.

**The timelock rule matches the Sky Core Atlas.** This removes a provision that could not be complied with as written. The separate exemption covers deallocation, which the Sky table does not list, and the three Morpho Vaults v1 instances, whose functions the table does not name.

**Governance approval is defined in one place**, so a future change to how Curator changes are approved needs to amend only the Governance Approval Process.

---

The required Spark Artifact changes can be found in the following pull request: https://github.com/sky-ecosystem/next-gen-atlas/pull/361
The source for these changes (broken down per document and type of change) can be found in the [originating forum post](https://forum.skyeco.com/t/saep-24-update-risk-curation-framework/28301).

## Outcomes

- If "For" receives more than 50% of votes cast, excluding abstentions, 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.

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

