# [Ethereum, Base] Spark Governance - Rotate Guardian and Curator Multisig Signers

- Space: [Spark](https://snapshot.box/s:sparkfi.eth.md)
- Author: 0xeF45Ee558e7AB2517446cBC8A397C07f207bd833
- State: Passed
- Voting type: Basic
- Start: 2026-10-05 16:09 UTC
- End: 2026-10-08 16:09 UTC
- Votes: 3
- Discussion: https://forum.skyeco.com/t/technical-scope-spark-guardian-and-curator-multisig-key-rotations/28281
- Open in Snapshot: https://snapshot.box/#/s:sparkfi.eth/proposal/0xc6387cc502c0506f090008ea66c592af681cfd6c60a45996dc120c4ec42d31df

## Results

- For: 451,041,886.22 voting power, 100.0%
- Against: 0 voting power, 0.0%
- Abstain: 0 voting power, 0.0%

## Proposal

# [Ethereum, Base] Spark Governance - Rotate Guardian and Curator Multisig Signers - October 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:

### Required Context

The Spark guardian Safe `0xf5748bBeFa17505b2F7222B23ae11584932C908B` holds Morpho guardian and sentinel permissions. It uses the same address on [Ethereum mainnet](https://etherscan.io/address/0xf5748bBeFa17505b2F7222B23ae11584932C908B) and [Base](https://basescan.org/address/0xf5748bBeFa17505b2F7222B23ae11584932C908B). On both chains, replace its owners with three Operational GovOps signing accounts and change **3-of-5 to 2-of-3**.

The standard Morpho curator Safe `0x0f963A8A8c01042B69054e787E5763ABbB0646A3` uses the same address on [Ethereum mainnet](https://etherscan.io/address/0x0f963A8A8c01042B69054e787E5763ABbB0646A3) and [Base](https://basescan.org/address/0x0f963A8A8c01042B69054e787E5763ABbB0646A3). On both chains, replace its owners with exactly two nominated direct owners and change **3-of-5 to 2-of-2**, requiring both signatures. Addresses, permissions and vault assignments remain unchanged. The Sentora RLUSD curator and nested owner Safes are not rotated.

Four standalone Safe transactions are required: one per Safe per chain, authorized by each current quorum. A Spark governance payload cannot call their owner-management functions. No contract is deployed or upgraded; calls use Safe `1.4.1` owner-management and batching.

The [Sky Morpho Vault Curation Framework's Role Configuration, A.2.2.10.1.1.1.3.1](https://sky-atlas.io/#686b81a9-450d-4340-a25a-5a069cbe8788), requires an Operational Executor Agent-controlled sentinel and curator/sentinel separation. The [Spark Cancellation Authority Independence provision, A.6.1.1.1.3.9.6.3.1](https://sky-atlas.io/#ea50c8da-008e-4f0f-b2df-ac666d5faf13), provides an Operational GovOps independence exception. The 2-of-3 guardian threshold is the sponsor's choice; the Core 2-of-2 requirement applies to the **curator** Safe, not to the guardian Safe.

### Proposed Action

Each Safe executes one atomic owner-management batch per chain, replacing all former owners and setting threshold `2`. Each batch requires at least three current owners' approval and reverts if an inner call fails. No other calls, approvals, transfers, role grants or implementation changes are permitted.

### Roles Transferred by the Rotation

The guardian rotation transfers control of six retained vault roles and inherited revocation authority on three Morpho V2 adapters; role-holder addresses remain unchanged.

- Guardian: [Spark Blue Chip USDC](https://etherscan.io/address/0x56A76b428244a50513ec81e225a293d128fd581D) and [Spark USDS](https://etherscan.io/address/0xe41a0583334f0dc4E023Acd0bFef3667F6FE0597) on Ethereum mainnet, and [Spark USDC](https://basescan.org/address/0x7BfA7C4f149E7415b73bdeDfe609237e29CBF34A) on Base.
- Sentinel, all on Ethereum mainnet: the [current Spark Blue Chip USDT V2 vault](https://etherscan.io/address/0xb0c424116172B55CbB6dD3136F5989F7959e5B91), the [Sentora x Spark RLUSD V2 vault](https://etherscan.io/address/0xFC8C624B6080a0a780583799f2A862DE936F6E22), and the [superseded Spark Blue Chip USDT V2 vault](https://etherscan.io/address/0xc7CDcFDEfC64631ED6799C95e3b110cd42F2bD22), migration does not remove retained permissions.

V1 guardian powers revoke pending guardian replacements, timelock decreases, market-cap increases or market removals. V2 sentinel powers cancel queued actions, decrease absolute and relative caps and deallocate assets from adapters; the three V2 adapters' `revoke(bytes)` authority follows the sentinel role automatically. Neither role makes the Safe an owner, curator or allocator. No contract-level permission is granted or revoked.

The legacy DAI vault has zero `guardian()` and `curator()`, contributing no permission. Registry and identified historical-contract checks found no additional non-Morpho guardian Safe permissions; the inventory is not exhaustive.

The curator retains five vault assignments: all listed above except [Sentora x Spark RLUSD V2 vault](https://etherscan.io/address/0xFC8C624B6080a0a780583799f2A862DE936F6E22), which keeps its separate curator. Curator parameter configuration and submitted actions remain subject to timelocks and cancellation controls.

The two curator accounts already own a 1-of-2 nested Safe within the 2-of-2 Sentora RLUSD curator. The standard curator uses them directly at 2-of-2; Sentora remains unchanged. A 2-of-2 threshold alone does not establish joint organizational control.

### Rationale

Placing cancellation authority under Operational GovOps and coordinating the curator handover support Spark's compliance with Sky Morpho vault requirements. Soter Labs requested coordination to avoid shared curator/sentinel team members; distinct addresses do not establish distinct people or custody. The rotation includes legacy permissions but does not alone establish compliance with all vault ownership, curator, market or timelock requirements.

### Verification after Execution

After each execution, Operational GovOps and curator parties record the receipt and post-execution block; verify exact proposed owners and threshold `2`, unchanged proxy, implementation, modules, guard and fallback handler, and every inventory role and exception.

Each new quorum must authorize a benign Safe message while one signer cannot. Guardian and curator owners must share no address; no guardian key may appear in the unchanged Sentora curator owner tree. Soter Labs must attest to personnel/custody separation, including relayer/sentinel separation.

Local fork tests passed using impersonation and approved-hash signatures, not real signer possession or consent. No auditor reviewed signer identities or transaction data. Simulate the exact ordered calls against final transaction state before signing.

---

Technical implementation details can be found under items 1 and 2 at [_Proposed Actions_ in The Technical Scope: Spark Guardian and Curator Multisig Key Rotations](https://forum.skyeco.com/t/technical-scope-spark-guardian-and-curator-multisig-key-rotations/28281).

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

## 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

