# [Ethereum] Spark Liquidity Layer - Morpho Vault Timelock Compliance

- Space: [Spark](https://snapshot.box/s:sparkfi.eth.md)
- Author: 0xF97c00fab22A45eB27163D0f0065Da00Da10624B
- State: Passed
- Voting type: Basic
- Start: 2026-10-19 16:13 UTC
- End: 2026-10-22 16:13 UTC
- Votes: 5
- Discussion: https://forum.skyeco.com/t/technical-scope-morpho-vault-timelock-compliance/28302
- Open in Snapshot: https://snapshot.box/#/s:sparkfi.eth/proposal/0xb00107403f527c247f50d99ac8c0a78022c7e4c53c000a355154cc1bcee8d3e9

## Results

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

## Proposal

# [Ethereum] Spark Liquidity Layer - Morpho Vault Timelock Compliance - 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:

### Required Context

Sky Core added timelock requirements for Morpho vaults and their adapters to the Atlas: [A.2.2.10.1.1.1.3.3.1 - Vault Timelock Requirements](https://sky-atlas.io/#14aba6cb-eb34-4780-84c1-908666835569) and [A.2.2.10.1.1.1.3.3.2 - Adapter Timelock Requirements](https://sky-atlas.io/#91ba9acf-6ed7-4214-8b6b-adfb03427ae1). This update brings Spark’s Morpho vaults into compliance. Only the Spark Blue Chip USDT and Sentora x Spark RLUSD vaults need changes; the other Spark Morpho vaults need no changes in this update.

This proposal fits into Spark's extended timelock compliance deadline of November 2, 2026, established in [A.2.2.10.1.1.1.3.5.2, Spark Exception](https://sky-atlas.io/#33e0e235-0031-4b44-9f56-c19df46daa02).

### Reasons for the Update

Bring Spark’s Morpho Vaults V2 exposure into compliance with the Timelock Requirements before the extended deadline:
- A zero timelock on allocator changes lets a compromised allocator be removed immediately.
- A zero timelock on the force deallocate penalty lets a penalty be introduced immediately in response to a griefing attack.
- The adapter timelock increases give sentinels a window to cancel an abdication, skim recipient change, or later timelock increase before it takes effect.

If Spark chooses not to implement these changes, the exposure in the non-compliant Morpho Vaults will be subject to 100% CRR as per [A.3.2.2.1.1.1.1.3.8.2 - Noncompliant Morpho Vault Allocations](https://sky-atlas.io/#20aa9663-214b-46f5-8b37-53be387b996b).
### Proposed Actions

#### 1. Spark Blue Chip USDT Vault: Allocator and Penalty Timelocks to Zero

On vault [`0xb0c424116172B55CbB6dD3136F5989F7959e5B91`](https://etherscan.io/address/0xb0c424116172B55CbB6dD3136F5989F7959e5B91), reduce the following timelocks to zero, as required by [A.2.2.10.1.1.1.3.3.1](https://sky-atlas.io/#14aba6cb-eb34-4780-84c1-908666835569):

- `setIsAllocator` (adding or removing an allocator): 864,000 seconds (10 days) to 0
- `setForceDeallocatePenalty`: 864,000 seconds (10 days) to 0

*The implementation of this item is dependent on the approval of [SAEP-24](https://forum.skyeco.com/t/saep-24-update-risk-curation-framework/28301/1), which is polled in parallel with this proposal.*

#### 2. Spark Blue Chip USDT Adapter: Raise Three Timelocks to the Minimums

On the USDT vault's market adapter [`0xEF4cB7e87f212F128f0b24cf35861E52B3C78A6a`](https://etherscan.io/address/0xEF4cB7e87f212F128f0b24cf35861E52B3C78A6a), raise the following timelocks to the minimum values required in [A.2.2.10.1.1.1.3.3.2](https://sky-atlas.io/#91ba9acf-6ed7-4214-8b6b-adfb03427ae1):

1. `abdicate`: 0 to 604,800 seconds (7 days)
2. `setSkimRecipient`: 0 to 259,200 seconds (3 days)
3. `increaseTimelock`: 0 to 604,800 seconds (7 days)

#### 3. Sentora x Spark RLUSD Vault: Allocator and Penalty Timelocks to Zero

On vault [`0xFC8C624B6080a0a780583799f2A862DE936F6E22`](https://etherscan.io/address/0xFC8C624B6080a0a780583799f2A862DE936F6E22), reduce the following timelocks to zero:

- `setIsAllocator` (adding or removing an allocator): 259,200 seconds (3 days) to 0
- `setForceDeallocatePenalty`: 604,800 seconds (7 days) to 0
  
*The implementation of this item is dependent on the approval of [SAEP-24](https://forum.skyeco.com/t/saep-24-update-risk-curation-framework/28301/1), which is polled in parallel with this proposal.*

---

Technical implementation details can be found under items 1, 2, and 3 at [_Proposed Actions_ in the originating Technical Scope forum post](https://forum.skyeco.com/t/technical-scope-morpho-vault-timelock-compliance/28302#p-107619-proposed-actions-12).

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

## Outcomes

- If "For" receives more than 50% of votes cast, excluding abstentions, the proposal will be approved. Item 2 is implemented on approval of this poll. Items 1 and 3 are implemented only once SAEP-24 is also approved; if SAEP-24 is rejected, Items 1 and 3 are not implemented. For approved items, 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

