bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 15쪽 중 3쪽
ne)”
Address:
0x38E4254bD82ED5Ee97CD1C4278FAae748d998865
Staking Engine Debt Position Migrator
Section titled “Staking Engine Debt Position Migrator”
Address:
0x473d777f608C3C24B441AB6bD4bBcA6b7F9AF90B
Clipper
Section titled “Clipper”
Address:
0x35526314F18FeB5b7F124e40D6A99d64F7D7e89a
ClipperCalc
Section titled “ClipperCalc”
Address:
0xB8f8c7caabFa320717E3e848948450e120F0D9BB
Seal Engine V1 (supports Chief V2 MKR)
Section titled “Seal Engine V1 (supports Chief V2 MKR)”
Address:
0x2b16C07D5fD5cC701a0a871eae2aad6DA5fc8f12
Codebase:
https://github.com/sky-ecosystem/lockstake/tree/602edbb682feb04af5fc1723ea427576286b8291
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/sky/token-governance-upgrade/timeline
Upgrade Timeline
Phase 1 — Partner outreach [Done]
Integration partners, exchanges, and other external stakeholders will be contacted regarding the upcoming upgrade.
Phase 2 — Migration announcement [Done]
2025-05-02
The Atlas forum will feature an official post about the migration.
The SKY migration will be publicly announced in detail.
Phase 3 — Governance poll [Done]
2025-05-12
All MKR holders will be able to participate in the governance poll.
Phase 4 — Communications [Done]
2025-05-13
A community‑wide marketing campaign for the Sky Ecosystem will be launched.
Phase 5 — Spell publication [Done]
2025-05-15
The governance upgrade spell will be published for community review.
Phase 6 — Migration go‑live [Done]
2025-05-19
The governance upgrade spell will be executed.
Phase 7 — Staking rewards activation [Done]
2025-05-29
The spell to activate USDS rewards for the Staking Engine will be published.
Phase 8 — Delayed upgrade penalty kick‑off
2025-09-18
A Delayed Upgrade Penalty will be applied to all MKR that does not upgrade to SKY before September 18.
On September 18, the moment the Delayed Upgrade Penalty begins to take effect, a 1% penalty on all MKR to SKY upgrades will immediately be applied.
Every 3 months after, the penalty will increase by an additional 1%.
Phase 9 — Penalty ramp‑up (ongoing)
2025-12
The delayed upgrade penalty will increase by 1%, unless Sky Governance decides otherwise.
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/sky/token-governance-upgrade/token-holders
Token Holders
Sky Protocol’s MkrSky Converter contracts enable MKR holders to convert MKR to SKY through an on-chain mechanism at a protocol-defined fixed rate. Converter V1 will stay active until the governance upgrade spell is executed, and
Converter V2
will activate following the passage of the MKR/SKY governance upgrade.
All conversions in the upgrade process are executed unidirectionally via the
mkrToSky
function, with fees applied according to the Delayed Upgrade Penalty schedule post-upgrade. Note that reverse conversion from SKY back to MKR requires utilizing an exchange and will not be possible through the Sky protocol.
For critical dates regarding the upgrade process, consult the
upgrade timeline
, which specifies when Converter V2 activates and when the Delayed Upgrade Penalties take effect.
mkrToSky
Conversion Function
Section titled “mkrToSky Conversion Function”
The
mkrToSky
function within the Converter contract (MkrSky.sol) facilitates on-chain MKR→SKY conversions at the protocol-defined rate.
Signature
function
mkrToSky
(
address
usr
,
uint256
mkrAmt
)
external
;
Input Parameters
usr
(address): Destination address for receiving SKY tokens.
mkrAmt
(uint256): Quantity of MKR tokens (18-decimal precision) to convert.
Fee Parameter
fee
(uint256, WAD): Protocol-wide conversion fee rate (scaled by 1e18) configurable by governance through the
file("fee", newFee)
admin operation. When non-zero, this fee is deducted from the calculated SKY output.
Event Log
Each
mkrToSky
execution emits an event containing
(caller, usr, mkrAmt, skyAmt, skyFee)
.
event
MkrToSky(
address
indexed
caller
,
address
indexed
usr
,
uint256
mkrAmt
,
uint256
skyAmt
,
uint256
skyFee
);
SKY Conversion Calculation
Section titled “SKY Conversion Calculation”
Follow this procedure to calculate the expected SKY output from your MKR conversion:
Query the current fee rate
Call the public getter on the Converter contract:
fee()
returns the current fee (WAD-scaled, where 1 WAD = 1e18).
Example: a 1% fee is represented as
0.01 × 1e18 = 1e16
.
Calculate gross SKY amount
The protocol conversion rate is fixed at
1 MKR → 24,000 SKY
.
grossSky = mkrAmt × 24,000
Calculate fee amount in SKY
skyFee = grossSky × fee ÷ 1e18
Calculate net SKY received
netSky = grossSky - skyFee
Calculation example (100 MKR, 1% fee)
grossSky = 100 × 24,000 = 2,400,000 SKY
skyFee = 2,400,000 × 0.01 = 24,000 SKY
netSky = 2,400,000 - 24,000 = 2,376,000 SKY
Converter Versions
Section titled “Converter Versions”
Converter V1 is currently operational. Upon approval of the governance upgrade proposal, Converter V1 will be deactivated and Converter V2 will become operational. Conversions are irreversible within the protocol; converting SKY back to MKR requires executing a swap on an external exchange.
SKY Token Supply
Section titled “SKY Token Supply”
Sky governance allocates the required amount of SKY tokens to the Converter V2 contract to accommodate the conversion of the entire outstanding MKR supply. During conversion, the Converter transfers these SKY tokens directly to your specified address rather than minting new tokens—you will observe a transfer event from the Converter, not a mint event on the SKY token contract. Simultaneously, Converter V2 burns the corresponding MKR tokens as part of the upgrade transaction. Please note that Converter V1 previously minted new SKY tokens on-demand unlike Converter V2.
Fee Collection Mechanism
Section titled “Fee Collection Mechanism”
Fees collected during conversions accumulate within the Converter contract and are tracked by the internal
take
variable. Governance can extract these accumulated fees by executing the
collect(to)
function at its discretion.
Delayed Upgrade Penalty Schedule
Section titled “Delayed Upgrade Penalty Schedule”
The MKR:SKY conversion ratio is fixed at 1:24,000. In the future, Sky protocol governance may activate a Delayed Upgrade Penalty that will reduce this conversion ratio by a specified percentage. Refer to the upgrade timeline for details regarding the anticipated activation date of the Delayed Upgrade Penalty and its future schedule of increases.
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/sky/token-governance-upgrade/protocol-participants
Protocol Participants
Governance Delegates
Section titled “Governance Delegates”
All current Governance Delegates must deploy a new Vote Delegate V3 contract using the Vote Delegate Factory V3
0x4Cf3DaeFA2683Cd18df00f7AFF5169C00a9EccD5
. To do this, call the
create()
function on the factory. After deployment, verify that the delegate’s
chief()
field points to the upgraded Chief contract. Migrate any self-staked MKR to SKY, and inform all MKR or SKY holders who delegate to you that they must re-delegate to your new address. Old V2 delegate contracts will stop counting votes once the new Chief is ratified.
Steps for Governance Delegates
Section titled “Steps for Governance Delegates”
Deploy a V3 Delegate:
Call
create()
on Vote Delegate Factory V3. The factory will deploy a new your new Vote Delegate contract which will be linked to the upgraded Chief and Polling contracts.
Verify the Link:
Call
chief()
on your new delegate contract. It must return the new Chief address, confirming V3 compatibility.
Migrate Your Own Stake:
Convert any MKR you have locked to SKY, then call
lock()
in your V3 delegate contract to stake your SKY.
Update Public References:
Update your Governance Portal profile, delegate registry repositories, forum threads, dashboards, and ENS records to show your new delegate address.
Announce the Change:
Share the update via forum posts, X/Twitter, Discord, newsletters, and Governance & Risk calls. Provide a direct link to the Voting Portal’s “Re-Delegate” flow, pre-filled with your new address.
Deprecate the Old Contract:
Once all delegations have moved, label the old delegate contract as deprecated wherever possible.
Broadcast Message for Delegators
Feel free to use or adapt the following message:
Action required: Our new Vote Delegate V3 contract is live at
0xAB...34
. Please open the Voting Portal and re-delegate your SKY balance to the new delegate address to keep your voting weight active under the upgraded Chief.
Governance Participants
Section titled “Governance Participants”
As a governance participant, you currently either deposit MKR directly in the Chief contract to vote yourself or delegate your voting weight through a Vote Delegate contract managed by a Governance Delegate. With the Sky Ecosystem governance upgrade, MKR and DSChief are replaced by SKY and the new Chief, and new Vote Delegate V3 contracts are introduced. After the new Chief is ratified, DSChief and all Delegate V2 contracts will stop accruing voting weight. You must move your MKR from the current Chief to your new SKY token balance in the upgraded Chief. MKR can be upgraded to SKY without incurring any Delayed Upgrade Penalties for a limited time.
Direct Self-Voting with SKY
Section titled “Direct Self-Voting with SKY”
Withdraw MKR from DSChief:
In the current Voting Portal, choose
Withdraw
, approve the IOU, then execute
free()
. DSChief requires two transactions because it burns an IOU token first.
Upgrade MKR to SKY:
Use the official converter (or any interface that calls the published
MkrSky
contract). One MKR mints 24,000 SKY until Sky Ecosystem governance activates the Delayed Upgrade Penalty on all upgrade conversions.
Deposit SKY into the New Chief:
lock(uint256)
function deposits your SKY token balance into the new Chief.
Vote:
Use
prepareSlate
and
vote(bytes32[])
as before; the only difference is the token.
Withdraw Later:
Use
free()
to withdraw SKY from Chief back to your wallet; IOU approval is no longer needed.
Delegated Voting through Delegate V3
Section titled “Delegated Voting through Delegate V3”
Withdraw MKR from the V2 Delegate:
Use
free()
to withdraw. V2 delegates will be ignored once the new Chief is live.
Upgrade MKR to SKY:
Only SKY counts in the new Chief.
Find Your Delegate’s New Address:
Every active Governance Delegate will publish a V3 contract. Look for the new address on the Delegates page or their forum thread, or select a new Governance Delegate.
Verify the Delegate Contract:
Call
chief()
on the contract; it must return the new Chief address, confirming V3 compatibility.
Confirm Official Deployment:
Ensure the Vote Delegate V3 contract was deployed using the official Vote Delegate Factory V3 by calling the
created
getter function, which returns
1
for a valid contract.
Deposit SKY into the V3 Delegate:
Use the Voting Portal to deposit SKY into the V3 Vote Delegate contract or use the
lock()
function on the Vote Delegate V3 contract.
Seal Engine Stakers
Section titled “Seal Engine Stakers”
If you have a position in the Seal Engine (also known as LockStake Engine V1), you must close it and migrate to the Staking Engine (LockStake Engine V2).
This applies to current vaults that:
Are earning farming rewards (lsMKR)
Have an active vote delegate
May or may not have USDS debt
1. Collect Your Position Data
Section titled “1. Collect Your Position Data”
Check the following before starting the migration:
What to Check
Why It Matters During Shutdown
USDS debt (drawn balance)
Must be zero before you can unlock collateral in V1.
Collateral locked (MKR)
Ensure your receiving wallet has enough gas for the conversion.
lsMKR farm rewards
Claim any outstanding rewards; unclaimed lsMKR is burned at close.
Vote delegate address
You’ll need to re-delegate after opening your V2 vault.
2. Close the V1 Position
Section titled “2. Close the V1 Position”
All actions are performed using the V1 UI or contract.
Harvest lsMKR rewards:
Call
harvest()
to claim any outstanding lsMKR.
Repay USDS debt (if any):
Call
wipe(uint wad)
to bring your USDS debt to exactly zero. Include stability fees in the wipe.
Remove the vote delegate (optional):
Call
delegate(0x000...00)
to clear the delegate address.
Unlock collateral:
Call
free(uint wad)
to release MKR to your wallet.
Revoke unlimited approvals (optional):
In your wallet UI, remove infinite MKR and lsMKR spend approvals for LockStake Engine V1.
3. Upgrade MKR to SKY
Section titled “3. Upgrade MKR to SKY”
LockStake Engine V2 accepts SKY, not MKR. If you already hold SKY from another source, you can skip this conversion for that portion.
Convert MKR to SKY:
Call
mkrToSky()
on the Converter V2 contract.
Receive SKY:
You now hold SKY. When you lock SKY in V2, lsSKY is minted automatically.
4. Open a New V2 “Staking Engine” Vault
Section titled “4. Open a New V2 “Staking Engine” Vault”
Approve SKY for V2:
Call
sky.approve(lockstakeEngineV2, type(uint256).max)
once.
Lock collateral:
Call
lock(uint wadSKY)
.
(Optional) Draw USDS:
Call
draw(uint wadDai)
. The per-vault fee is now immutable; check the UI for the set value.
Set your vote delegate:
Call
delegate(<delegateAddress>)
.
Confirm farming has started:
V2 emits
Lock()
and
DelegateChanged()
events. Farming rewards accrue in lsSKY.
5. What You Get Back When Closing V1
Section titled “5. What You Get Back When Closing V1”
Asset
Returned?
Notes
MKR collateral
Yes
All locked MKR is returned to your wallet.
lsMKR farming rewards
Only if claimed
Unclaimed lsMKR is burned when the vault is closed.
Vote power
Removed
You must re-delegate in V2.
Any fees
No refund
Stability fees are consumed on wipe.
You cannot lock MKR directly in V2—convert to SKY first.
On-Chain Migration with LockstakeMigrator
Section titled “On-Chain Migration with LockstakeMigrator”
If you want to migrate a Seal Engine position with USDS debt without repaying the debt manually, use the on-chain migrator (if the new Staking Engine has enough debt ceiling).
LockstakeMigrator (flash-loan helper):
Use the LockstakeMigrator contract instead of steps 2–4 for zero-debt-repayment migration.
The migrator will:
Take a short-lived USDS flash loan.
Repay your V1 debt, unlock MKR, and convert it to SKY.
Lock SKY into a new V2 vault.
Draw USDS from the new vault to repay the flash loan.
Your vault will end up in V2 with the same debt and collateralization ratio, but with the new fee schedule and SKY collateral.
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/sky/token-governance-upgrade/integrators
Integrators
MKR Upgrade Notice
Section titled “MKR Upgrade Notice”
Display a notice prominently on your interfaces wherever MKR or SKY tokens are referenced. This helps users understand the upgrade process and the steps required to avoid the Delayed Upgrade Penalty.
The Sky Ecosystem Governance community has voted to make SKY the sole governance token of the Sky Protocol. You can no longer vote with MKR. MKR holders are encouraged to upgrade to SKY promptly to maintain the ability to participate in governance and avoid the Delayed Upgrade Penalty. For more information, please visit the MKR to SKY Upgrade Hub.
Integrator Categories
Section titled “Integrator Categories”
This section provides guidance for various platform types to ensure a seamless transition from MKR to SKY tokens. As the protocol upgrades from MKR to SKY, integrators play a critical role in helping users navigate this change. The transition involves a one-directional conversion mechanism with a time-sensitive fee structure that increases after September 2025.
Each category below addresses specific integration points and offers actionable steps to:
Support both MKR and SKY tokens during the transition period
Help users convert their MKR to SKY through the Converter V2 contract
Update interfaces to accommodate the new token while maintaining user experience
Mitigate risks associated with diminishing MKR liquidity and potential price volatility
Review the
Upgrade Timeline
and
Codebase Change Analysis
sections to identify the necessary steps that best fit your use case. You can contact the Integrations team at
[email protected]
to discuss your specific situation and develop a custom action plan.
Wallets
Section titled “Wallets”
List SKY Token
Ensure your wallet lists the SKY token with the proper brand assets:
Token symbol:
SKY
Token address:
0x56072C95FAA701256059aa122697B133aDEd9279
SKY token logo: Available on the
brand assets page
Facilitate MKR to SKY Upgrade
Direct users to the Sky Portal where they can upgrade from MKR to SKY. You can facilitate this conversion by integrating with the Converter V2 contract.
DEXes
Section titled “DEXes”
Integrate with Converter Contract for Optimal Liquidity
The Converter V2 contract provides the most reliable source of MKR to SKY swap liquidity. Users can convert their tokens at a fixed ratio without incurring slippage. To support your users during the transition period:
Add SKY Token Support
to your trading pairs and interfaces
Implement Direct Integration
with the Converter V2 contract for seamless conversion
Display Conversion Information
to educate users about the fixed conversion ratio
Update Trading UI
to highlight the MKR to SKY upgrade opportunity
As MKR liquidity decreases over time, routing users to the Converter V2 contract will deliver a superior user experience compared to traditional market-based trading.
Exchanges
Section titled “Exchanges”
Direct users to navigate the upgrade process on the Sky portal. You can also integrate with the Converter V2 contract to upgrade your users’ MKR balances to SKY efficiently on their behalf.
Rewards and Borrow Positions
Section titled “Rewards and Borrow Positions”
The Staking Engine introduces important changes that affect all integrators who offer Seal Engine functionality. Key improvements include the removal of exit fees and transition from MKR to SKY token support. Exit fees in the current Seal Engine V1 have also been set to 0 to allow current users to migrate without incurring any additional fees.
If you currently offer an interface to Seal Engine, you must update it to support Staking Engine functionality.
Key Changes
Section titled “Key Changes”
Token Support
: Staking Engine only accepts SKY tokens, while Seal Engine V1 supported both MKR and SKY tokens.
Exit Fee Removal
: The exit fee previously charged when withdrawing from positions has been eliminated. The exit fee value is set to zero in Seal Engine V1 and the feature is removed in V2.
Migration Strategies
Section titled “Migration Strategies”
For Positions Without Debt
The recommended approach for positions without debt is a three-step process:
Close the existing Seal Engine V1 position to withdraw MKR
Upgrade the withdrawn MKR to SKY using the Converter V2 contract
Open a new position in Staking Engine with the converted SKY
Users can maintain the same reward settings as their previous positions after migration.
For Positions With Outstanding Debt
The Sky Portal supports a specialized migration pathway that allows users to:
Transfer their position from Seal Engine V1 to Staking Engine
Automatically convert their MKR to SKY in the process
Maintain their existing debt without requiring repayment to complete the migration, provided there is sufficient space in the debt ceiling of Staking Engine
Lending Protocols
Section titled “Lending Protocol프로젝트로 돌아가기