Spark proposes guardian and curator signer rotations on Ethereum and Base

What happened

Spark proposed four Safe owner-rotation transactions transferring guardian control to Operational GovOps and replacing the standard Morpho curator owners.

What changed

If executed, guardian quorum becomes 2-of-3 and standard curator quorum becomes 2-of-2. Existing vault permissions would become exercisable by the incoming owners.

What did not change

Safe addresses and vault assignments remain unchanged in the proposal. The separate Sentora curator is excluded. Fork simulations do not establish production execution.

Confirmed

• The guardian Safe is 0xf5748bBeFa17505b2F7222B23ae11584932C908B on both chains.
• The standard curator Safe is 0x0f963A8A8c01042B69054e787E5763ABbB0646A3 on both chains.
• The proposal requires both curator rotations to be verified before either guardian handover.
• Retained guardian and sentinel powers include cancellation and, for V2 vaults, cap decreases and deallocation.
• The official record requires organizational representation, key control and personnel/custody separation checks.

Still open

• Required governance approvals and Atlas instance reconciliation.
• All four staged transactions, production execution receipts and final owner sets.
• Incoming signer possession, organizational attribution and operational availability.
• Personnel and custody separation beyond distinct on-chain addresses.
• Whether any selected Ketju vault uses an affected curator or sentinel.

What it means for an advisor

• Review the Spark authority map and Morpho curator diligence for the proposed handover.
• Map affected vaults to any selected exposure before asserting a client-specific curator-change trigger.
• Require chain-specific completion evidence and operating handover records before updating the authority baseline.