bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 3쪽 중 2쪽
tive to the blockchain,
easily verifiable, and highly liquid. These assets enable the protocol to operate entirely on-chain, using automated smart contracts to manage collateralization,
valuation, and liquidation processes with minimal external dependencies.
RWA vaults
RWA vaults
differ from traditional vaults primarily in the type of collateral they support and the mechanisms required to manage them. They are implemented as a set
of predefined rules on how the vault is managed within the MCD system—this implementation is described in MIP21 as part of Sky's former MIP (Maker Improvement
Proposal) framework. RWA vaults represent a protocol mechanism for interfacing with traditional financial instruments (ie. financial assets not natively issued on a
blockchain and governed by off-chain legal agreements) and gaining exposure to them. The protocol's technical architecture enables governance-approved strategies
for capital deployment into sovereign debt instruments and similar highly-rated securities, with returns accruing to the protocol's surplus buffer. These assets exist
outside the blockchain and require tokenization to represent their value digitally. Managing RWA vaults involves more complex processes, which might include legal
agreements to ensure enforceable claims on the underlying assets, reliance on third-party custodians and trustees to secure and manage these assets, and
mechanisms to handle off-chain valuation and compliance. Unlike traditional vaults, which rely on decentralized oracles for near-instant price feeds for managing risk,
RWA vaults incorporate complementary off-chain methods and settlement processes that bridge traditional and decentralized finance systems for valuing and
liquidating the collateral to manage the risk.
High-Level Technical Overview
High-Level Technical Overview
On a more technical level, each RWA vault is tailored for the specific requirements of the off-chain deal that drives it. However, there are some common
components/patterns. Each RWA deal is composed of at least 3 smart-contract components:
1
.
RWA Urn
RWA Urn
: the actual RWA Vault, with the rules that define the operation of the lower-level vault. Unlike regular crypto vaults that can be created by anyone, only
Sky Governance is able to create them. The operation of such vaults is delegated to Sky Governance-approved counterparties. For instance, they can draw or
repay Dai back and forth while the vault is active. Borrower capital use is dictated by an off-chain legal agreement with the DAO.
2
.
RWA Token
RWA Token
: tokenized representation of the off-chain asset, to ensure consistent accounting of the transaction. The token is locked into the vault as collateral,
for which the price is determined by the RWA Oracle. RWA Tokens are not freely transferable, as they have no intrinsic value, since it is not possible to redeem
them anywhere. It should be either in control of the vault operator, or ideally be locked into the vault when the RWA deal is set up.
3
.
RWA Liquidation Oracle
RWA Liquidation Oracle
: unlike regular crypto oracles, with live price feeds, the RWA Oracle is controlled by Sky Governance and only updated when required.
Besides the RWA Token prices, the RWA Oracle also stores the link to the legal documents that govern the deal – usually in the form of an IPFS hash – and the
"liquidation" status for the vault (see more on RWA Liquidation Process below).
Additionally, some helper components might be required:
1
.
RWA Output Conduit
RWA Output Conduit
[^1]: after the operator draws Dai, an intermediate step might be required before it reaches its final destination. For instance, a specified
third party might be required to authorize the transfer, or Dai should be converted into another stablecoin (i.e.: USDC) and then transferred. In those cases, a
specialized variation of RWA Output Conduit is added to the setup as the destination for the Dai drawn from the RWA Urn.
2
.
RWA Input Conduit
RWA Input Conduit
: similar to output conduits, but used when the operator wants to repay Dai into the vault. Be it third party authorization, stablecoin
swapping (i.e.: repayment is made in USDC instead of Dai), or something else, there might be a specialized variation of RWA Input Conduit added to the mix.
3
.
RWA Jar
RWA Jar
: stability fees in the Sky Protocol are inherently fixed—while they can be updated, they remain constant between updates—and accrue by the
second.Some RWA deals don’t align with this model because they invest in assets with variable interest rates. Rather than relying on approximate estimates
and making frequent on-chain adjustments—which would be operationally expensive—certain RWA Vaults set their on-chain stability fee to zero, with the
actual fee defined off-chain and enforced through binding legal documents. In these cases, for accounting consistency, the fees generated by the Dai drawn
from the vault must be transferred into an RWA Jar. From there, the fees can be permissionlessly moved to the Sky Protocol’s Surplus Buffer.
RWA Liquidation Process
RWA Liquidation Process
Unlike crypto collateral, which can be sold on-chain immediately as soon as the liquidation conditions are met, RWA liquidations might take months or even years to
complete. Liquidations for RWA vaults occur entirely off-chain, through manual processes requiring Sky Governance and Ecosystem Actor coordination.
The RWA Liquidation has 2 steps:
1
.
Soft Liquidation
Soft Liquidation
: some conditions of the deal terms (i.e. covenants) are currently not being met. Some deals have an on-chain enforced grace period through
which stakeholders can fix such issues before hard liquidation kicks in. If the relevant counterparty can meet the terms defined in the legal agreement, the
RWA vault can be moved out of the soft liquidation state.
2
.
Hard Liquidation
Hard Liquidation
: if the stakeholders and Sky Governance agree that the Dai drawn from a specific RWA Vault is unrecoverable after the soft liquidation and
the grace period has expired, then the Sky protocol needs to write off the existing debt, so the accounting reflects the reality. That means that the total
outstanding debt for that vault needs to be deducted from the protocol's Surplus Buffer. If there is not enough surplus to cover the losses, the protocol will
perform Flop auctions (mint governance tokens and purchase Dai from the market) until the surplus buffer returns to zero.
The future of RWA Vaults
The future of RWA Vaults
The inclusion of RWA vaults allowed Sky to diversify its collateral base and reduce dependence on volatile cryptocurrencies. However, this came with increased
operational complexity, slower liquidation times, and legal complexity.
Despite these factors, RWAs continue to be a key collateral type for the Sky Protocol. Since the
rebranding from MakerDAO to Sky, the creation and management of RWAs will be spearheaded by Stars, which are independent projects within the Sky Ecosystem.
Stars will be operating a new framework called the Allocation System to autonomously manage allocations into tokenized RWAs, which will be implemented with new
and improved techniques from the historical RWA vaults described above. While the Stars will have some level of autonomy, their actions will still being subject to
Sky's risk management systems. The allocation system is a framework designed to manage and deploy capital across the Sky ecosystem efficiently. It allows Stars to
borrow funds from the Sky Protocol at favorable rates, enabling targeted liquidity injections into DeFi protocols and tokenized real-world assets. This system
enhances the ecosystem's financial stability through significant allocations into liquid asset types, with an emphasis on risk management to ensure that capital
allocations are optimized for risk-adjusted returns while fostering growth and diversification within the Sky ecosystem.
Key External Actors
Key External Actors
In addition to its smart contract infrastructure, the Sky Protocol involves groups of external actors to maintain operations: Keepers, Oracles, and Global Settlers
(Emergency Oracles), and Sky Ecosystem community members. Keepers take advantage of the economic incentives presented by the Protocol; Oracles and Global
Settlers are external actors with special permissions in the system assigned to them by MKR voters; and Sky Ecosystem community members are individuals and
organizations that provide services.
Keepers
Keepers
A Keeper is an independent (usually automated) actor that is incentivized by arbitrage opportunities to provide liquidity in various aspects of a decentralized system.
In the Sky Protocol,
Keepers are market participants that help Dai maintain its Target Price
($1): they sell Dai when the market price is above the Target Price, and buy
Dai when the market price is below the Target Price. Keepers participate in Surplus Auctions, Debt Auctions, and Collateral Auctions when Sky Protocol Vaults are
liquidated.
Price Oracles
Price Oracles
The Sky Protocol requires real-time information about the market price of the collateral assets in Sky Protocol Vaults in order to know when to trigger Liquidations.
The Protocol derives its internal collateral prices from a
decentralized Oracle infrastructure
that consists of a broad set of individual nodes called Oracle Feeds. MKR
voters choose a set of trusted Feeds to deliver price information to the system through Ethereum transactions. They also control how many Feeds are in the set.
To protect the system from an attacker attempting to gain control of a majority of the Oracles, the Sky Protocol receives price inputs through the
Oracle Security
Module
(OSM), not from the Oracles directly. The OSM, which is a layer of defense between the Oracles and the Protocol, delays a price for one hour, allowing
Emergency Oracles or a Sky Governance vote to freeze an Oracle if it is compromised. Decisions regarding Emergency Oracles and the price delay duration are made
by Sky Ecosystem Governance.
Emergency Oracles
Emergency Oracles
Emergency Oracles are selected by MKR voters and act as a last line of defense against an attack on the governance process or on other Oracles. Emergency Oracles
are able to freeze individual Oracles (e.g., ETH and BAT Oracles) to mitigate the risk of a large number of users trying to withdraw their assets from the Sky Protocol
in a short period of time, as they have the authority to unilaterally trigger an
Emergency Shutdown
Emergency Shutdown serves two main purposes. It is used during
emergencies as a last-resort mechanism to protect the Sky Protocol against attacks on its infrastructure, and used to facilitate a Sky Protocol system upgrade. The
process is fully decentralized and controlled by Sky Governance.
.
The Dai Savings Rate
The Dai Savings Rate
The
Dai Savings Rate (DSR) allows any Dai holder to earn savings
automatically and natively by locking their Dai into the DSR contract in the Sky Protocol. It can be
accessed via the
SummerFi
portal or through various gateways into the Sky Protocol. Users aren’t required to deposit a minimum amount to earn the DSR,
and they
can withdraw any or all of their Dai from the DSR contract at any time.
The DSR is a global system parameter that determines the amount Dai holders earn on their savings over time. When the market price of Dai deviates from the Target
Price due to changing market dynamics, Sky Ecosystem Governance can mitigate the price instability by voting to modify the DSR accordingly:
If the market price of Dai is above 1 USD, Sky Ecosystem Governance can choose to gradually decrease the DSR, which will reduce demand and should reduce
the market price of Dai toward the 1 USD Target Price.
If the market price of Dai is below 1 USD, Sky Ecosystem Governance can choose to gradually increase the DSR, which will stimulate demand and should
increase the market price of Dai toward the 1 USD Target Price.
Initially, adjustment of the DSR will depend on a weekly process, whereby Sky Ecosystem Governance first evaluate and discuss public market data and proprietary
data provided by market participants, and then vote on whether an adjustment is necessary or not. The long-term plan includes implementation of the DSR
Adjustment Module, an
Instant Access Module
An Instant Access Module contains components to create direct, bounded changes to the Sky Protocol without
consensus in the DS-Chief.
that directly controls both the DSR and the
Base Rate
The Base Rate is part of the Stability Fee that applies to all asset types (i.e., the total
Stability Fee for each asset type includes the base rate plus the collateral rate).
.
This module allows for easy adjustment of the DSR (within strict size and frequency
boundaries set by Sky Ecosystem Governance) by an MKR holder on behalf of the larger group of Sky Ecosystem Governance. The motivation behind this plan is to
enable nimble responses to rapidly changing market conditions, and to avoid overuse of the standard governance process of Executive Voting and Governance
Polling.
In 2024, MakerDAO rebranded to Sky and introduced the Sky Savings Rate for the USDS stablecoin. They coexist, although their rates may differ and the Sky Savings
Rate utilizes the ERC4626 tokenized vault standard as opposed to the Dai Savings Rate.
Governance of the Sky Protocol
Governance of the Sky Protocol
Use of the MKR Token in Sky Governance
Use of the MKR Token in Sky Governance
The MKR token—the governance token of the Sky Protocol—allows those who hold it to
vote
on changes to the Sky Protocol. Note that anyone, not only Sky
Ecosystem Governance, can
submit
proposals for an MKR vote.
Any voter-approved modifications to the governance variables of the Protocol will likely not take effect immediately in the future; rather, they could be delayed by as
much as 24 hours if voters choose to activate the Governance Security Module (GSM). The delay would give Sky Ecosystem Governance the opportunity to protect
the system, if necessary, against a malicious governance proposal (e.g., a proposal that alters collateral parameters contrary to established monetary policies or that
allows for security mechanisms to be disabled) by triggering a Shutdown.
Polling and Executive Voting
Polling and Executive Voting
In practice, the Sky Governance process includes proposal polling and Executive Voting. Proposal polling is conducted to establish a rough consensus of community
sentiment before any Executive Votes are cast. This helps to ensure that governance decisions are considered throughtfully and reached by consensus prior to the
voting process itself. Executive Voting is held to approve (or not) changes to the state of the system. An example of an Executive Vote could be a vote to ratify Risk
Parameters for a newly accepted collateral type.
At a technical level, smart contracts manage each type of vote. A Proposal Contract is a smart contract with one or more valid governance actions programmed into
it. It can only be executed once. When executed, it immediately applies its changes to the internal governance variables of the Sky Protocol. After execution, the
Proposal Contract cannot be reused.
Any
Ethereum Address
An Ethereum Contract Account is controlled by its contract code. It cannot initiate new transactions on its own; rather, when it receives a
message from an externally owned account or another contract account, it executes its code, allowing it to read, write, and send messages or create smart contracts.
can deploy valid Proposal Contracts. MKR token holders can then cast approval votes for the proposal that they want to elect as the Active Proposal. The Ethereum
address that has the highest number of approval votes is elected as the Active Proposal. The Active Proposal is empowered to gain administrative access to the
internal governance variables of the Sky Protocol, and then modify them.
The MKR Token’s Role in Recapitalization
The MKR Token’s Role in Recapitalization
In addition to its role in Sky Governance, the MKR token has a complementary role as the recapitalization resource of the Sky Protocol. If the system debt exceeds the
surplus, the MKR token supply may increase through a Debt Auction (see above) to recapitalize the system. This risk inclines Sky Ecosystem Governance to align and
responsibly govern the Sky ecosystem to avoid excessive risk-taking.
Risk Parameters Controlled by Sky Governance
Risk Parameters Controlled by Sky Governance
Each Sky Protocol Vault type (e.g., ETH Vault and BAT Vault) has its own unique set of Risk Parameters that enforce usage. The parameters are determined based on
the risk profile of the collateral, and are directly controlled by Sky Ecosystem Governance through voting.
The Key Risk Parameters for Sky Protocol Vaults are:
The Key Risk Parameters for Sky Protocol Vaults are:
Debt Ceiling
Debt Ceiling
: A Debt Ceiling is the maximum amount of debt that can be created by a single collateral type. Sky Governance assigns every collateral type a
Debt Ceiling, which is used to ensure sufficient diversification of the Sky Protocol collateral portfolio. Once a collateral type has reached its Debt Ceiling, it
becomes impossible to create more debt unless some existing users pay back all or a portion of their Vault debt.
Stability Fee
Stability Fee
: The Stability Fee is an annual percentage yield calculated on top of how much Dai has been generated against a Vault’s collateral. The fee is paid
in Dai only, and then sent into the Sky Protocol Buffer.
Liquidation Ratio
Liquidation Ratio
: A low Liquidation Ratio means Sky Governance expects low price volatility of the collateral; a high Liquidation Ratio means high volatility is
expected.
Liquidation Penalty
Liquidation Penalty
: The Liquidation Penalty is a fee added to a Vault’s total outstanding generated Dai when a Liquidation occurs. The Liquidation Penalty is
used to encourage Vault owners to keep appropriate collateral levels.
Collateral Auction Duration
Collateral Auction Duration
: The maximum duration of Collateral auctions is specific to Sky Protocol Vaults. Debt and Surplus auction durations are global
system parameters.
Auction Bid Duration:
Auction Bid Duration:
Amount of time before an individual bid expires and closes the auction.
Auction Step Size
Auction Step Size
The minimum amount a bidder can offer above the current bid during an auction.
: This Risk Parameter exists to incentivize early bidders in
auctions, and prevent abuse by bidding a tiny amount above an existing bid.
Risk and Mitigation Responsibilities of Governance
Risk and Mitigation Responsibilities of Governance
The successful operation of the Sky Protocol depends on Sky Governance taking necessary steps to mitigate risks. Some of those risks are identified below, each
followed by a mitigation plan.
A malicious attack on the smart contract infrastructure by a bad actor.
A malicious attack on the smart contract infrastructure by a bad actor.
One of the greatest risks to the Sky Protocol is a malicious actor—a programmer, for example, who discovers a vulnerability in the deployed smart contracts, and then
uses it to break the Protocol or steal from it.
In the worst-case scenario, all decentralized digital assets held as collateral in the Protocol are stolen, and recovery is impossible.
Mitigation:
Mitigation:
The Maker Foundation's highest priority is the
security of the Sky Protocol
, and the strongest defense of the Protocol is
Formal Verification
Formal
Verification means creating mathematical specifications of the intended behavior of the system, alongside mathematical proofs that the codebase implements
behavior that is identical to the intended behavior, with no unintended side effects as there is no mathematical evidence that the intended behavior produces effects
inconsistent with the intended behavior.
.
The Dai codebase was the first codebase of a decentralized applica프로젝트로 돌아가기