Atlas Edit Proposal · PR #360

Atlas Edit Proposal — 2026-10-19

17 documents changed · 15 edited, 1 new, 2 removed

Summary

Summary

This proposal includes the following edits:

  • Add Standards For Audits Not Commissioned By Sky And Revise Recognized Audit Firms - Sets audit standards and coverage requirements for audits not commissioned by Sky, and updates the recognized audit firm lists.
  • Executive Process Liaison Confirms Prime Spell Actions Are Authorized In The Atlas - Requires the Executive Process Liaison to check that each Prime Spell action is authorized in the Atlas before confirming the Prime Spell address.
  • Clarify Core Council Multisig Is Deployed Separately On Arbitrum - Clarifies that the Core Council Multisig on Arbitrum is a separate deployment, and requires its signer requirements and signer changes to apply on every network on which it is deployed.
  • Record Permissioned Role Holders For Morpho Vaults - Requires the records for each Prime Agent's Morpho vaults to specify every permissioned role, its holder and address, and brings the Spark, Grove and Osero Morpho vault records up to date with the current role holders.
  • Clarify Burn USDS And USDC Swap Rate Limit Restoration Is Capped At maxAmount - Clarifies that the rate limit capacity restored by burning USDS or swapping USDC to USDS is capped at the rate limit's maxAmount.
  • Set River I Instance Capital Ratio Requirement To 7% - Sets the Capital Ratio Requirement for Pattern's River I Instance to 7%.
  • Increase Osero Gauntlet Vault Deposit Slope To 650,000 USDC Per Day - Increases the deposit rate limit slope for Osero's Gauntlet USDC Prime Morpho Vault V2 Instance from zero to 650,000 USDC per day.
  • Housekeeping Updates - Corrects wording in the Obex Relayer Multisig and RateLimitID documents.

Document Changes

Edit scope

Timelock

1 edited document

EditedA.6.1.1.1.2.6.1.3.1.5.2.4.2

Timelock

Timelock: 240 hours (10 days), except for setIsAllocator and setForceDeallocatePenalty, which have a timelock of 0 hours (no delay).)

Edit scope

Timelocks

2 edited documents

A.6.1.1.1.2.6.1.3.1.5.3.4.2

Timelocks

EditedA.6.1.1.1.2.6.1.3.1.5.3.4.2.4

setIsAllocator Timelock

Timelock: 0 hours (no delay72 hours (3 days)

DeletedA.6.1.1.1.2.6.1.3.1.5.3.4.2.5

setForceDeallocatePenalty Timelock

Timelock: 0 hours (no delay)

Edit scope

Curator Roles

2 edited documents

A.6.1.1.1.3.9.3

Curator Roles

EditedA.6.1.1.1.3.9.3.2

Scope of Authority

Curators may only implement changes that have been explicitly approved by Spark governance in accordance with Governance Approval Process, including risk-reduction actions approved in advance under Risk-Reduction Actionsvia polling. Curators may queue changes before approval in accordance with Polling Requirement, and may cancel pending changes in accordance with Cancellation Reasons.

EditedA.6.1.1.1.3.9.3.3

Reporting of Curator Actions

All actions taken under a Curator role must be reported by the Curator in the Spark Prime categorySpark-Prime subsection of the Sky forum within 24 hours of submission. The report should include a transaction hash of the action, the UTC time at which the timelock period for the action elapses where the action is subject to a timelock, a description of the action being implemented, and a link to the related proposal and governance poll, if the poll is available. For a change queued before approval, the report must state that governance approval had not been obtained when the change was queued and include the expected poll closing time in UTC used when queueing. For a risk-reduction action taken under Risk-Reduction Actions, the report must state which of the actions listed in that section it is, in place of a link to a governance poll.

Edit scope

Governance Approval Process

2 edited documents

EditedA.6.1.1.1.3.9.4

Governance Approval Process

The documents herein describe the requirements for governance approval before implementation of Curator changes, and the conditions for queueing changes before approval, and the risk-reduction actions that Spark governance approves in advance.

EditedA.6.1.1.1.3.9.4.1

Polling Requirement

Except for risk-reduction actions approved in advance under Risk-Reduction Actions, allAll curator-executed changes must be approved by Spark governance through a polling process before they are implemented.

A Curator may queue a proposed change before the related governance poll is created or approved, provided that the onchain timelock for the pending change will expire no earlier than twenty-four (24) hours after the expected closing time of that poll. Queueing means submitting a change to the onchain timelock without implementing it. All applicable timelock delays continue to apply.

The twenty-four (24) hour condition applies when the change is queued. Once the related poll is created, its actual closing time, including any subsequent change to that time, must be used to assess the remaining period before the pending change becomes executable. Cancellation on timing grounds is required only if that period is less than twenty (20) hours.

The pending change must match the change submitted for approval. If the poll does not approve that change, or the actual poll closing time leaves less than twenty (20) hours before the pending change becomes executable, the pending change must be cancelled in accordance with Cancellation Reasons.

DeletedA.6.1.1.1.3.9.4.3

Risk-Reduction Actions

Spark governance approves in advance, without a governance poll, the following risk-reduction actions when taken by a Curator:

  • Reducing a supply cap, absolute cap or relative cap.
  • Removing an account from the Allocator role, or from any other role whose holder can allocate funds or increase a cap. Removing an account from a guardian or sentinel role is not a risk-reduction action.
  • Cancelling a pending change in accordance with Cancellation Reasons.

No other action is a risk-reduction action.

This section approves only the risk-reduction action itself. Any other change submitted in the same transaction or batch of transactions requires approval under Polling Requirement.

Each risk-reduction action must be reported in accordance with Reporting of Curator Actions.

Edit scope

Cancellation Authorities

3 edited documents

EditedA.6.1.1.1.3.9.6

Cancellation Authorities

The documents herein define the cancellation mechanisms and authorities for pending actions within the Timelock period, and the conditions under which cancellation authority holders may reduce caps or deallocate funds.

EditedA.6.1.1.1.3.9.6.3

Cancellation Authority

A Guardian is a specific admin role defined within the Morpho smart contract system. In Morpho Vaults v1 this role is named Guardian; in Morpho Vaults v2 it is named Sentinel. Within this framework, the two are together referred to as the cancellation authority. In Morpho Vaults v2, multiple addresses may hold the Sentinel role. The vault owner may remove a Sentinel role holder without a timelock; where the vault owner is the Spark SubProxy, removal requires a Sky Executive Vote.

In addition to cancelling pending changes, a cancellation authority holder may reduce an absolute or relative cap, or deallocate funds from a market or adapter, where its role permits that action at the smart contract level. It may do so only for one of the reasons set out in Cancellation Reasons, other than a request by the Curator.

EditedA.6.1.1.1.3.9.6.3.2

Cancellation Authority Reporting

All actions taken under the cancellation authority must be reported by the acting role holder in the Spark Prime categorySpark-Prime subsection of the Sky forum within 24 hours of submission. The report should include a transaction hash of the action, a description of the action, general reasoning for the action, and justification for the action being within the governance-approved mandate.

Edit scope

Timelock Requirement

1 edited document

EditedA.6.1.1.1.3.9.5.1

Timelock Requirement

All admin or privileged controls managed by curator roles must be subject to a minimum timelock delay of three (3) days between scheduling and execution, except as set out below.

For any function for which Vault Timelock Requirements or Adapter Timelock Requirements sets a requirement, that requirement applies in place of the minimum in this section.

The minimum in this section does not apply to cancelling a pending change, reducing a cap or deallocating funds.

Edit scope

Scope of Curator Authority

1 edited document

EditedA.6.1.1.1.3.9.7.1.4

Scope of Curator Authority

The specific execution actions the curator is permitted to take, subject to approval by Spark governance in accordance with Governance Approval Processprior Spark governance approval via polling.

Edit scope

Approved Instances

4 edited documents, 1 new document

A.6.1.1.1.3.9.7.2

Approved Instances

InsertedA.6.1.1.1.3.9.7.2.1

Spark USDS Morpho Vault - Ethereum Mainnet

The Spark USDS Morpho Vault on Ethereum Mainnet is an approved instance with the following details:

  • Instance Name: Spark USDS Morpho Vault (Ethereum Mainnet)
  • Contract Address: 0xe41a0583334f0dc4E023Acd0bFef3667F6FE0597
  • Curator: Soter Labs and Spark, implemented via a Gnosis Safe multisig at 0x0f963A8A8c01042B69054e787E5763ABbB0646A3, requiring a 2 of 2 signer approval threshold between a Soter Labs multisig and a Spark multisig
  • Scope of Curator Authority: Execution of risk parameter changes and operational actions approved by Spark governance polls
  • Cancellation Authority: Operational GovOps Soter Labs, implemented via a Gnosis Safe multisig at 0xf5748bBeFa17505b2F7222B23ae11584932C908B, requiring a 2 of 3 signer approval threshold
EditedA.6.1.1.1.3.9.7.2.2

Spark Blue Chip USDC Morpho Vault - Ethereum Mainnet

The Spark Blue Chip USDC Morpho Vault on Ethereum mainnet is an approved instance with the following details:

  • Instance Name: Spark Blue Chip USDC Morpho Vault (Ethereum Mainnet)
  • Contract Address: 0x56A76b428244a50513ec81e225a293d128fd581D
  • Curator: Soter Labs and Spark, implemented via a Gnosis Safe multisig at 0x0f963A8A8c01042B69054e787E5763ABbB0646A3, requiring a 2 of 2 signer approval threshold between a Soter Labs multisig and a Spark multisig
  • Scope of Curator Authority: Execution of risk parameter changes and operational actions approved by Spark governance in accordance with Governance Approval Processpolls
  • Cancellation Authority: Operational GovOps Soter Labs, implemented via a Gnosis Safe multisig at 0xf5748bBeFa17505b2F7222B23ae11584932C908B, requiring a 2 of 3 signer approval threshold
EditedA.6.1.1.1.3.9.7.2.3

Spark Blue Chip USDT Morpho Vault - Ethereum Mainnet

The Spark Blue Chip USDT Morpho Vault on Ethereum mainnet is an approved instance with the following details:

  • Instance Name: Spark Blue Chip USDT Morpho Vault (Ethereum Mainnet)
  • Contract Address: 0xb0c424116172B55CbB6dD3136F5989F7959e5B91
  • Curator: Soter Labs and Spark, implemented via a Gnosis Safe multisig at 0x0f963A8A8c01042B69054e787E5763ABbB0646A3, requiring a 2 of 2 signer approval threshold between a Soter Labs multisig and a Spark multisig
  • Scope of Curator Authority: Execution of risk parameter changes and operational actions approved by Spark governance in accordance with Governance Approval Processpolls
  • Cancellation Authority: Operational GovOps Soter Labs, implemented via a Gnosis Safe multisig at 0xf5748bBeFa17505b2F7222B23ae11584932C908B, requiring a 2 of 3 signer approval threshold
EditedA.6.1.1.1.3.9.7.2.4

Spark USDC Morpho Vault - Base

The Spark USDC Morpho Vault on Base is an approved instance with the following details:

  • Instance Name: Spark USDC Morpho Vault (Base)
  • Contract Address: 0x7BfA7C4f149E7415b73bdeDfe609237e29CBF34A
  • Curator: Soter Labs and Spark, implemented via a Gnosis Safe multisig at 0x0f963A8A8c01042B69054e787E5763ABbB0646A3, requiring a 2 of 2 signer approval threshold between a Soter Labs multisig and a Spark multisig
  • Scope of Curator Authority: Execution of risk parameter changes and operational actions approved by Spark governance in accordance with Governance Approval Processpolls
  • Cancellation Authority: Operational GovOps Soter Labs, implemented via a Gnosis Safe multisig at 0xf5748bBeFa17505b2F7222B23ae11584932C908B, requiring a 2 of 3 signer approval threshold
EditedA.6.1.1.1.3.9.7.2.5

Sentora RLUSD Morpho Vault - Ethereum Mainnet

The Sentora RLUSD Morpho Vault on Ethereum Mainnet is an approved instance with the following details:

  • Instance Name: Sentora RLUSD Morpho Vault (Ethereum Mainnet)
  • Contract Address: 0xFC8C624B6080a0a780583799f2A862DE936F6E22
  • Curator: Soter Labs and Sentora, implemented via a Gnosis Safe multisig at 0xff070333654aaE76A0A77465E4F0fd101C57c03F, requiring a 2 of 2 signer approval threshold
  • Scope of Curator Authority: Execution of risk parameter changes and operational actions approved by Spark governance in accordance with Governance Approval Processpolls
  • Cancellation Authority: Sentinel role held by the Operational GovOps Soter Labs multisig at 0xf5748bBeFa17505b2F7222B23ae11584932C908B, requiring a 2 of 3 signer approval threshold, together with a Soter Labs multisig at 0xb5bFd4883256089Dc58D962b80ab7068e71E7c80, requiring a 2 of 3 signer approval threshold, and a Sentora multisig at 0x9e396dE3312D373b87F9BD8763fb48184b42aac0, requiring a 1 of 1 signer approval threshold
  • Allocator: Sentora, at 0x9e396dE3312D373b87F9BD8763fb48184b42aac0 and at 0xC4Ba4e822C420452fe2BAB93211208D3CcBd79D3