Atlas Edit Proposal

The Core Facilitator may recommend changing the approved emergency contact mechanism specified in Approved Emergency Contact Mechanisms, but they must do so in consultation with the Protocol Security Workstream Lead. The Core Facilitator’s recommendation is subject to a poll through the Operational Weekly Governance Cycle.

Edit scope

Debt Ceiling Breaker Exception

1 edited document

EditedA.1.10.3.2.3

Debt Ceiling Breaker Exception

The LINE_MOM contract manages the breaker for the Debt Ceilings of a configurable subset of the vault types in the Sky Protocol. This Debt Ceiling Breaker allows a successful governance proposal to reduce the debt ceilings of a pre-configured whitelist of vault types to zero without waiting for the GSM Pause Delay to expire.

The Debt Ceiling Breaker affects both the Debt Ceiling and the Maximum Debt Ceiling of a given vault type when activated, disabling the Dynamic Debt Ceiling functionality for that vault type if enabled. To reverse the effect, parameters of affected vault types must be reconfigured with an Executive Vote which is subject to the GSM Pause Delay.

The whitelist may be configured via a successful governance proposal, but must wait for the GSM Pause Delay before changes come into effect. The whitelist is defined in Debt Ceiling Breaker Exception Whitelist and can be changed via the Weekly GovernanceOperational Weekly Cycle.

Edit scope

Core Facilitator’s Authority To Create Proposals

1 edited document

EditedA.1.11.1.5

Core Facilitator’s Authority To Create Proposals

The Core Facilitator may create proposals using the Weekly GovernanceOperational Weekly Cycle to enable them to fulfill their responsibilities.

Edit scope

Revision of Minimum Positive Participation

1 edited document

EditedA.1.12.2.6.1

Revision of Minimum Positive Participation

The Minimum Positive Participation value defined in Ratification Poll Requirements may be modified via a successful Governance Poll under the Operational Weekly Governance Cycle.

If such a vote is successful, the new Minimum Positive Participation value will come into effect in the _following_ Monthly Governance Cycle. The Minimum Positive Participation value may not be changed for Ratification Polls that are in progress under any circumstances.

Edit scope

Resources

1 edited document

EditedA.2.1.1.4

Resources

Core GovOps is granted a budget to procure the necessary administrative support and services from Governance Process Support Ecosystem Actors. The budget can only be used to perform tasks described in Governance Process Support and its subdocuments. Core GovOps can modify the budget using an Operational Weekly Governance Cycle poll.

Edit scope

Diamond PAU

5 new documents

InsertedA.2.2.10.1.1.1.2

Diamond PAU

The documents herein define the shared parameters, roles, contracts, and operational processes of the Diamond PAU (Parallelized Allocation Unit), the facet-based Allocation System Primitive controller architecture.

A.2.2.10.1.1.1.2.1

Liquidity Layer Parameter Definitions

InsertedA.2.2.10.1.1.1.2.1.7

Maximum Exposure Tolerance

Where the Atlas specifies a maximum exposure, actual exposure may exceed that maximum by up to 5%, provided the excess is solely attributable to accrued interest and not to new principal. A Prime Agent is responsible for claiming and returning accrued interest as necessary to keep exposure within the specified maximum.

A.2.2.10.1.1.1.2.3

Liquidity Layer Shared Contracts

InsertedA.2.2.10.1.1.1.2.3.6

Configurator

The Configurator (Configurator) is the contract through which designated actors operate a Diamond PAU's rate limits and pre-approved controller actions, within the ceilings and permissions as specified in PAS. Further details will be specified in a future iteration of the Atlas.

InsertedA.2.2.10.1.1.1.2.3.7

Beam State

Beam State (BeamState) is the contract that records which actors, rate limits, and controller actions are authorized under PAS. Further details will be specified in a future iteration of the Atlas.

InsertedA.2.2.10.1.1.1.2.4

PAS

The PAS (Parallelized Allocation System) is a permissioned layer that lets designated actors operate a Diamond PAU's rate limits and pre-approved controller actions, within governance-set ceilings, without direct administrative control over the Diamond PAU. Further details will be specified in a future iteration of the Atlas.

Edit scope

Unbanning

1 edited document

EditedA.2.7.1.2.1.1.3

Unbanning

Bannings are by default permanent. However, Ranked Delegates can propose the unbanning of users by publishing a forum post that states the handle(s) of the user(s) whose unbanning they request and the rationale for their unbanning. The forum post must tag the Core Facilitator, who will in turn prepare a binary Weekly Cycle Governance PollGovernance Poll through the Operational Weekly Cycle to be published on the Voting Portal as soon as reasonably possible. The outcome of the Governance Poll is binding.

Where identity can be proven, the ban on unbanned users will be lifted across all communication channels.

Edit scope

Resilience Fund Budget

1 edited document

EditedA.2.9.1.1.1.1

Resilience Fund Budget

The budget of the Resilience Fund is defined in Resilience Fund Current Budget. The Core Facilitator can propose to pay out the budget manually through a Weekly Governancean Operational Weekly Cycle, according to the rules related to claims described in this Section. The Core Facilitator can propose modifications to the document cited above through the Weekly GovernanceOperational Weekly Cycle.

Edit scope

Resilience Fund Claim Approval Core Facilitator Decision

1 edited document

EditedA.2.9.1.1.1.4.2.2.8

Resilience Fund Claim Approval Core Facilitator Decision

Based on the recommendation of the Resilience Technical Committee, the Core Facilitator will decide whether to trigger a Governance Poll through the Weekly GovernanceOperational Weekly Cycle to perform a claim payout.

Edit scope

Lite Peg Stability Module Parameter Modification

1 edited document

EditedA.3.3.2.7.1.1.3

Lite Peg Stability Module Parameter Modification

The Core Facilitator, in consultation with the Core Council Risk Advisor, may recommend changes to any of the parameters specified in the subdocuments of Lite Peg Stability Module Parameter Definitions. These changes will be subject to an Executive Vote through the Operational Weekly Governance Cycle.

Edit scope

Smart Burn Engine Parameters

3 edited documents

A.3.5.2

Smart Burn Engine Parameters

EditedA.3.5.2.3

Modification

The Core Facilitator, in consultation with the Core Council Risk Advisor, can modify the kbump and hop parameters of the Smart Burn Engine. Such a modification can be enacted either by proposing it for inclusion in an Executive Vote pursuant to the Operational Weekly Cycle, without requiring a prior Governance Poll, or by executing it directly through the SBE-BEAM within its bounds, as specified in Smart Burn Engine Bounded External Access Module. LSEV2-SKY-A-USDS rewardsDuration should always match the value of the hop parameter without requiring prior governance authorization. Changes to other parameters require a Governance Poll followed by an Executive Vote.

The Smart Burn Engine parameters must be updated Core Facilitator must modify all parameters of the Smart Burn Engine as necessary to implement the allocation specified in Step 3: Smart Burn Engine. Such updates can be executed either through an Executive Votea modification can be enacted either by proposing it for inclusion in an Executive Vote pursuant to the Operational Weekly Cycle, without requiring a prior Governance Poll, or by executing it directly through the SBE-BEAM within its bounds.

Except as provided in the preceding paragraphs, modifications to the parameters of the Smart Burn Engine require a Governance Poll followed by an Executive Vote.

EditedA.3.5.2.4

Smart Burn Engine Bounded External Access Module

The Smart Burn Engine Bounded External Access Module (SBE-BEAM) enables a designated, Governance-whitelisted Operator to adjust the Kicker Lot Size (kbump), the SKY Accumulation Percentage (burn), and the Splitter Interval (hop) parameters of the Smart Burn Engine, as specified in Kicker Lot Size Parameter, SKY Accumulation Percentage Parameter, and Splitter Interval Parameter. Adjustments are governed by the SBE-BEAM smart contract logic and specific parameters set by Sky Governance.

The SBE-BEAM Operator can raise or lower these parameters freely within the bounds set by Sky Governance. Those bounds are one-sided guardrails on the rate of accumulation: the Kicker Lot Size cannot be set above maxKbump, the Splitter Interval cannot be set below minHop, and the combined throughput, expressed as the Kicker Lot Size divided by the Splitter Interval, cannot exceed maxRate. The rate of accumulation therefore cannot be raised beyond the maximum that Sky Governance has sanctioned, while no corresponding bound limits reductions to it. The SKY Accumulation Percentage (burn) can be set to any value between 0% and 100%is not subject to these bounds, which limit only the rate of accumulation, and the only technical constraint on it is the maximum specified in Technical Limitations. The tau parameter separately requires a minimum interval between operations, applying to any operation regardless of whether it raises or lowers the parameters. The SBE-BEAM holds the following bounding parameters: (i) maxKbump, (ii) minHop, (iii) maxRate, and (iv) tau. The bases on which these parameters may be modified are specified in Modification.

EditedA.3.5.2.4.5

Operators

The SBE-BEAM Operator is a Governance-whitelisted entity that can use the SBE-BEAM to alter the three Smart Burn Engine parameters within its control — the Kicker Lot Size (kbump), the SKY Accumulation Percentage (burn), and the Splitter Interval (hop). Changes to the kbump and hop parameters, and to their combined throughput, are limited by the maxKbump, minHop, and maxRate parameters, and every change is subject to the tau cadence. The burn parameter is not subject to the maxKbump, minHop, or maxRate bounds, which limit only the rate of accumulation, and is constrained only by the technicalthe only technical constraint on it is the maximum specified in Technical Limitations. The Operator can be changed by an Executive Vote.

Edit scope

Parameter Adjustments / Stability Parameter Bounded External Access Module

1 edited document

EditedA.3.7.1.3.4

Parameter Adjustments

All Stability Parameter Bounded External Access Module parameters can be modified by the Core Executor Agents, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.

Edit scope

Operator Update Process / Operators / Stability Parameter Bounded External Access Module

1 edited document

EditedA.3.7.1.3.5.2

Operator Update Process

Stability Parameter Bounded External Access Module Operators can be modified by the Core Facilitator, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.

Edit scope

Parameters Modification

1 edited document

EditedA.4.4.1.3.2.2

Parameters Modification

The parameters specified in Parameters Definition that are set by governance may be modified by the Core Executor Agents, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.

Edit scope

Slope 1 Modification

1 edited document

EditedA.4.4.1.3.5.1.1.4.2

Slope 1 Modification

The Slope 1 parameter may be modified by the Core Executor Agents, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.

Edit scope

Slope 2 Modification

1 edited document

EditedA.4.4.1.3.5.1.1.5.2

Slope 2 Modification

The Slope 2 parameter may be modified by the Core Executor Agents, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.

Edit scope

Parameter Adjustments / stUSDS Bounded External Access Module

1 edited document

EditedA.4.4.1.3.8.3

Parameter Adjustments

All stUSDS BEAM parameters can be modified by Core GovOps, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.

Edit scope

Operator Update Process / Operators / stUSDS Bounded External Access Module

1 edited document

EditedA.4.4.1.3.8.4.3

Operator Update Process

stUSDS BEAM Operators can be modified by Core GovOps, in consultation with the Core Council Risk Advisor. This process will be conducted through the Operational Weekly Governance Cycle or, if necessary, through out-of-schedule Executive Votes.

Edit scope

Capital Ratio Requirement

1 edited document

A.6 — The Agent ScopeA.6.1 — Agent ArtifactsA.6.1.1 — List Of Prime Agent ArtifactsA.6.1.1.7 — OseroA.6.1.1.7.2 — Sky PrimitivesA.6.1.1.7.2.6 — Supply Side Stablecoin PrimitivesA.6.1.1.7.2.6.1 — Allocation System PrimitiveA.6.1.1.7.2.6.1.3 — Active InstancesA.6.1.1.7.2.6.1.3.1 — Ethereum Mainnet InstancesA.6.1.1.7.2.6.1.3.1.1 — SparkLendA.6.1.1.7.2.6.1.3.1.1.1 — Ethereum Mainnet - SparkLend USDS Instance Configuration DocumentA.6.1.1.7.2.6.1.3.1.1.1.2 — ParametersA.6.1.1.7.2.6.1.3.1.1.1.2.5 — Off-chain Operational Parameters

EditedA.6.1.1.7.2.6.1.3.1.1.1.2.5.3

Capital Ratio Requirement

The Capital Ratio Requirement for this Instance, as specified in Capital Ratio Requirement, is 100%25%.

Summary

Document Changes