# [Ethereum, Base] Spark Guardian and Curator Multisig Configuration Ratification

- Space: [Spark](https://snapshot.box/s:sparkfi.eth.md)
- Author: 0xF97c00fab22A45eB27163D0f0065Da00Da10624B
- State: Passed
- Voting type: Basic
- Start: 2026-10-19 16:10 UTC
- End: 2026-10-22 16:10 UTC
- Votes: 5
- Discussion: https://forum.skyeco.com/t/technical-scope-spark-guardian-and-curator-multisig-key-rotations/28281/5?u=votewizard
- Open in Snapshot: https://snapshot.box/#/s:sparkfi.eth/proposal/0x0c4bc6ae25008854f0b78e778f216eb847a5e0f12fcbdbbb5d4450d0f403a568

## Results

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

## Proposal

# [Ethereum, Base] Spark Governance - Ratify the Curator Multisig Configuration - 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

The Guardian and Curator rotations defined in the [Technical Scope](https://forum.skyeco.com/t/technical-scope-spark-guardian-and-curator-multisig-key-rotations/28281) and [polled on October 5, 2026](https://snapshot.box/#/s:sparkfi.eth/proposal/0xc6387cc502c0506f090008ea66c592af681cfd6c60a45996dc120c4ec42d31df)  were executed on Ethereum and Base on October 13, 2026. The Guardian Safe was rotated as polled. The Curator Safe diverged from the poll because the original post described its signers incorrectly as:
- 2-of-2, with signers matching Soter Labs Safe [`0xAB5710211458FC8d7E0Be628202F47DdbD3F38Eb`](https://etherscan.io/address/0xAB5710211458FC8d7E0Be628202F47DdbD3F38Eb)

### Reasons for the Update

The executed setup matches what Spark and Soter Labs agreed, and it is the same nested structure as the existing Sentora RLUSD Curator Safe. It meets the Curator role requirement in [A.2.2.10.1.1.1.3.1](https://sky-atlas.io/#686b81a9-450d-4340-a25a-5a069cbe8788): the Curator Safe must be jointly controlled by the Operational Executor Agent and the Prime Agent at 2-of-2. Spark proposes Curator actions; Soter Labs co-signs and executes.

### Proposed Actions

Ratify the executed Curator Safe [`0x0f963A8A8c01042B69054e787E5763ABbB0646A3`](https://etherscan.io/address/0x0f963A8A8c01042B69054e787E5763ABbB0646A3) (same address on Ethereum and Base) configuration as 2-of-2 between two Safes:
- Spark Safe [`0x50c770E6dC6CfdEE33509273FA9a215bfAffF9B2`](https://etherscan.io/address/0x50c770E6dC6CfdEE33509273FA9a215bfAffF9B2), 3-of-5, with the same signers as the Spark operations Safe [`0x2E1b01adABB8D4981863394bEa23a1263CBaeDfC`](https://etherscan.io/address/0x2E1b01adABB8D4981863394bEa23a1263CBaeDfC)
- Soter Labs Safe [`0xAB5710211458FC8d7E0Be628202F47DdbD3F38Eb`](https://etherscan.io/address/0xAB5710211458FC8d7E0Be628202F47DdbD3F38Eb), 1-of-2, owned by the two signers matching Soter Labs Safe

---

The revised Technical Scope with the executed transactions and post-execution checks can be found in [this forum thread](https://forum.skyeco.com/t/technical-scope-spark-guardian-and-curator-multisig-key-rotations/28281/6)

## Outcomes

- If "For" receives more than 50% of votes cast, excluding abstentions, the proposal will be approved. The Curator Safe configuration executed on Oct 13 is ratified, and the instance records are updated through the [SAEP-24 pull request](https://github.com/sky-ecosystem/next-gen-atlas/pull/361). If SAEP-24 is rejected, changes will be applied through a standalone pull request limited to the Curator lines.
- If "Against" receives the most votes, the proposal will be rejected. No changes will be implemented to the records, and Spark must propose a new signer configuration.

---

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

