bitpro가 원문에서 글자만 모은 내용이에요. 표·그림·수식은 빠지거나 깨질 수 있어요. 전체 15쪽 중 4쪽
s”
Implement these measures to support a smooth MKR to SKY transition:
List the SKY token
with identical lending parameters as MKR
Update MKR Debt Ceiling
to 0 to limit new positions with MKR.
Notify MKR borrowers
about the upcoming conversion deadline and fee schedule
Provide clear documentation
for closing MKR positions efficiently
As MKR holders convert to SKY, the diminishing MKR supply creates two significant risks:
Liquidity Risk
: Thinning MKR markets will make it increasingly difficult for borrowers to source tokens for loan repayment
Price Volatility Risk
: Reduced market depth may trigger severe price fluctuations, potentially leading to unexpected liquidations
The one-directional conversion mechanism (MKR → SKY only) creates a progressively challenging environment for borrowers who delay transition. Additionally, once the Late Conversion Phase begins in mid-September.
For your lending interface, add a prominent alert informing users of the conversion timeline and directing them to the SKY Portal at
sky.money
.
Oracles
Section titled “Oracles”
Avoid implementing automatic price conversions between MKR and SKY tokens. After the governance upgrade, the tokens will trade independently with MKR becoming increasingly illiquid as trading volume and market availability decrease. Due to the one-directional conversion mechanism, accurate price extrapolation between the tokens will not be reliable, even with the defined conversion ratio between MKR to SKY.
The MKR to SKY conversion ratio, initially set at 1:24000, is subject to reduction by governance through the
fee
parameter in the Converter V2 contract. This fee parameter acts as a mechanism to decrease the effective conversion rate, making the fixed-ratio relationship between the tokens subject to change.
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/sky/token-governance-upgrade/codebase-change-analysis
Codebase Change Analysis
Chief
Section titled “Chief”
V3 Codebase:
https://github.com/sky-ecosystem/chief/blob/newchief/src/Chief.sol
V2 Codebase:
https://github.com/sky-ecosystem/chief/blob/d42f10fdf922bbc7636817961a85f540b285d0e6/src/chief.sol
Functional Interface Changes
Section titled “Functional Interface Changes”
There have been NO changes to external user-facing function interfaces in the Chief contract upgrade. These functions can continue to be used as before.
lock(uint256)
: Deposits governance tokens into the Chief contract to gain voting power
free(uint256)
: Withdraws governance tokens from the Chief contract, removing associated voting power
etch(address[])
: Creates a new slate of candidates (a unique address set to vote for)
vote(address[])
: Votes for a slate of addresses with your full voting weight
lift(address)
: Elevates an address to authority status if it has sufficient votes
External Considerations
Section titled “External Considerations”
Flash Loan Protection Changed
Flash loan protections remain in the upgraded Chief contract, but now use a new mechanism to prevent manipulation of the voting process with flash-loaned MKR or SKY tokens.
Previous Implementation:
lock
and
free
could not be executed within the same block.
lift
could be performed at any time, including in the same block as
lock
.
This allowed a flash loan transaction to perform
lock
and
lift
in a single block, but not
free
.
New Implementation:
lift
and
free
cannot occur in the same block.
Flash loan transactions can still perform
lock
and
lift
together, but cannot execute
free
in that block due to new restrictions between
free
and
lift
.
lock
and
free
can now occur together in the same block.
Lift Cooldown Period
lift
operations now have a cooldown: after a successful
lift
, further
lift
actions are blocked until the cooldown period expires, even if attempted within the same block.
The
lock
function does not update the last timestamp when tokens are deposited. This behavior differs from previous versions, where the timestamp was updated on each lock operation.
The
lift
function now updates the last timestamp. This change ensures that the timestamp accurately reflects the most recent lift operation, which is important for enforcing the cooldown period.
IOU Token Removed
IOU tokens are no longer issued for deposited SKY. As a result, actions involving IOU tokens—such as approving IOU transfers before calling
free
on Chief—are no longer required.
The
lock
function no longer mints IOU token balances when governance tokens are deposited.
The
free
function no longer burns IOU token balances when governance tokens are withdrawn. Since IOU tokens are no longer issued, there is no need to handle their burning during withdrawals.
Vote Delegate V3
Section titled “Vote Delegate V3”
V3 Codebase:
https://github.com/sky-ecosystem/vote-delegate/tree/v3/src
V2 Codebase:
https://github.com/sky-ecosystem/vote-delegate/tree/v2/src
Functional Interface Changes
Section titled “Functional Interface Changes”
There have been NO changes to external user-facing function interfaces in the Vote Delegate contract upgrade.
External Considerations
Section titled “External Considerations”
Hatch Trigger and Cooldown Removed
The hatch trigger and cooldown mechanisms have been removed from the Vote Delegate contract. As a result, you no longer need to check for previous Vote Delegate V2 restrictions related to hatch triggers or cooldown periods when determining if the
lock()
function is available for other users within the same Vote Delegate contract. Participants are no longer restricted by others’ actions, as removing the hatch reserve and cooldown eliminates previous user interaction limitations.
IOU Tokens No Longer Held
Vote Delegate no longer manages IOU token balances.
In version 3, the Chief contract has removed IOU tokens entirely, so neither governance participants nor Vote Delegate need to manage IOU tokens.
In version 2, IOU tokens were held within the Vote Delegate contract, removing the need for user approval, but they were still present.
In version 1, IOU tokens were returned to the user’s wallet, requiring MKR holders to approve the contract for their IOU balance before withdrawing.
Getter Function Change
The Chief contract’s
GOV()
function has been renamed to
gov()
. The function signature and its usage within Vote Delegate have changed accordingly. For backward compatibility, the
GOV()
getter remains available in the new Chief contract.
MKR-SKY Converter V2
Section titled “MKR-SKY Converter V2”
V2 Codebase:
https://github.com/sky-ecosystem/sky/blob/one-direction/src/MkrSky.sol
V1 Codebase:
https://github.com/sky-ecosystem/sky/blob/3ddfa5ee55d10b8192f239235bf83e46744314b8/src/MkrSky.sol
Functional Interface Changes
Section titled “Functional Interface Changes”
Only the
mkrToSky(uint256 mkrAmount)
function from version 1 remains available in version 2. The
skyToMkr(uint256 skyAmount)
function and all related logic have been completely removed. The interface for
mkrToSky
is unchanged; however, the conversion rate is now affected by a governance-set
fee
parameter. Users can no longer convert SKY to MKR using this contract.
External Considerations
Section titled “External Considerations”
Pre-minted SKY Token Balance
The Converter V2 contract no longer has permission to mint new SKY tokens. Instead, the full SKY token balance needed to convert all outstanding MKR is pre-minted and deposited into Converter V2. When an upgrade is executed, the SKY tokens held by Converter V2 are distributed to MKR holders.
Governance Control
Converter V2 introduces governance-controlled functionality. Previously, governance could not modify any settings in the contract. Now, governance can update the
fee
parameter, which determines the fee charged during MKR-to-SKY conversions. All fees collected are tracked in the
take
variable.
Governance can call the
collect
function to transfer the accumulated SKY fees from the Converter V2 contract to a designated address.
LockStake Engine (Seal Engine)
Section titled “LockStake Engine (Seal Engine)”
V2 Codebase:
https://github.com/sky-ecosystem/lockstake/blob/v2/src
V1 Codebase:
https://github.com/sky-ecosystem/lockstake/tree/7c71318623f5d6732457fd0c247a1f1760960011/src
Functional Interface Changes
Section titled “Functional Interface Changes”
The following changes impact the external functional interface which integrations have to account for:
lock(uint256 amount)
and
free(uint256 amount)
now operate solely on SKY; the
lockSky
/
freeSky
methods are removed.
Collateral renamed from MKR → SKY and the liquid‑staked wrapper from lsMKR → lsSKY (identical ABI, downstream compatibility).
Added
migrate(address from, address to, uint256[] positionIds)
in the new
LockstakeMigrator
contract to move positions from V1 → V2 in one transaction.
External Considerations
Section titled “External Considerations”
Conversion Logic Removed
All
MkrSkyLike
interfaces and MKR↔SKY conversion calls are deleted. The engine now accepts raw SKY and mints/burns lsSKY directly, removing an external call and oracle dependency.
Fixed Exit Fee
Exit fee is locked at deployment — governance cannot adjust it post‑deployment. Exit Fee will be set to 0 at deployment.
Migration Path
Users should invoke the
LockstakeMigrator
(flash‑loan–assisted) to migrate V1 positions containing debt to V2.
Proxy / Storage Compatibility
No storage‑layout changes in
LockstakeUrn
; existing proxy clones remain valid.
Internal Changes
Section titled “Internal Changes”
Accounting Model Simplified
Single mapping tracks SKY locks; separate MKR/SKY balances are removed.
LockstakeMigrator Module
Stateless contract enabling vault migration with or without USDS debt:
Unlock old MKR, convert via external
mkrSky
, relock as SKY.
If debt exists, take a USDS flash‑loan, wipe debt, migrate collateral, then draw USDS to repay.
Manages approvals and relies on Sky Protocol’s flash‑loan callback checks (
initiator == self
) for safety.
IOU Logic Removed
No more IOU token minting/burning; deposits and withdrawals adjust only raw locked balances.
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/sky/token-governance-upgrade/chief-cutover-checks
Chief Cutover Checks
Token holders, Protocol participants, and Integrators can monitor the cutover process once the spell is live on the Old Chief contract. Token holders are not blocked from upgrading their MKR to SKY at any point. This is geared towards Protocol Participants and Integrators who need to sync their change process based on the status of the Chief cutover process. The cutover process happens in the following three stages and these checks can be used to monitor the progress.
Cutover Monitoring Checklist
Section titled “Cutover Monitoring Checklist”
Pre-Cutover
Section titled “Pre-Cutover”
Monitor spell deployment status on Old Chief.
Track governance security module (GSM) delay.
Record activation time after spell execution.
Cutover Execution
Section titled “Cutover Execution”
Confirm New Chief is live.
Verify Old Chief is inactive.
Observe empty vote slate threshold for launch.
Post-Cutover
Section titled “Post-Cutover”
Ensure new Chief launch restrictions are lifted.
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/sky/token-governance-upgrade/vote-data-api
Vote Data API
Migration Notice
Starting
19 May 2025
, Sky Ecosystem’s governance-data API will split into two endpoints:
Pre-upgrade Data (before 19 May 2025)
:
API Endpoint:
https://vote.makerdao.com/api
Swagger Documentation:
https://vote.makerdao.com/api-docs
Post-upgrade Data (19 May 2025 onward)
:
API Endpoint:
https://vote.sky.money/api
Swagger Documentation:
https://vote.sky.money/api-docs
The underlying OpenAPI specifications, endpoints, and response schemas remain unchanged. The only required code change is updating the base URL for queries involving data from
19 May 2025
onward.
API Overview
Section titled “API Overview”
The Sky Ecosystem Governance Portal exposes a public, read-only REST and ES-Module API, suitable for front-end applications. It returns JSON-formatted data and requires no authentication for
GET
requests.
The API documentation is available via Swagger UI, based on an OpenAPI specification.
Endpoint Details
Section titled “Endpoint Details”
Base URLs
:
Pre-upgrade:
https://vote.makerdao.com/api
Post-upgrade:
https://vote.sky.money/api
Swagger UI
:
Pre-upgrade:
https://vote.makerdao.com/api-docs
Post-upgrade:
https://vote.sky.money/api-docs
Resource Groups
Section titled “Resource Groups”
Polling
Provides current and historical governance poll data, including proposal metadata, vote totals, outcome status, and full proposal text (via IPFS or GitHub markdown).
Executive
Exposes information on executive “spells,” such as queue status, estimated activation times (ETA), vote tallies, and defined office-hour windows.
Delegates
Returns delegate details—addresses, display names, pledged SKY or MKR, voting-power share, platform links, and self-reported mandate statements.
Voter Address
Surfaces voter-specific activity: individual voting history, delegated SKY or MKR amounts, current voting weight, and delegation relationships for a given Ethereum address.
ES Module
Offers a tree-shakable JavaScript module that exports the same governance objects used by the front-end, enabling zero-configuration integration in dApps.
Integration Notes
Section titled “Integration Notes”
MKR and SKY tokens are not 1:1 equivalent. Values returned from the pre- and post-upgrade APIs will differ accordingly; ensure appropriate handling when comparing data across endpoints.
All endpoints remain publicly accessible without authentication.
JavaScript applications can directly import governance data via the provided ES-Module endpoints.
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/sky/token-governance-upgrade/troubleshooting
Troubleshooting
Depositing into the Chief V2 (Old) After Upgrade
Section titled “Depositing into the Chief V2 (Old) After Upgrade”
Deposits into the Old Chief will revert after the governance upgrade. The upgrade spell disables new deposits.
Checking a Vote Delegate Contract Linkage
Section titled “Checking a Vote Delegate Contract Linkage”
Query the
gov()
method on the Vote Delegate Factory address of the Vote Delegate contract and ensure it matches Chief V3 contract address.
Released into the public domain (CC0 1.0 Universal)
– trademarks remain with their owners; no warranty. See
full license
.
## /guides/upgrades/migrate-old-mkr-to-mkr
Migrate OLD_MKR Balance to MKR Balance
Level:
Intermediate
Estimated Time:
15 minutes
Last Updated:
2025-08-19
In April 2016, MakerDAO deployed the first version of the MKR token (“OLD_MKR”). In December 2017, a new MKR token contract was deployed alongside the launch of Single-Collateral Dai and Maker Governance contracts.
This guide walks holders of the original OLD_MKR tokens through migrating their balance to the current MKR token. The original migration UI at
makerdao.com/redeem
has been sunset, but the process remains fully available via Etherscan by interacting directly with the relevant contracts.
Learning Objectives
Section titled “Learning Objectives”
Understand the historical context of the MKR token migration
Check your OLD_MKR balance using Etherscan
Successfully redeem OLD_MKR tokens for current MKR tokens
Verify the completion of your token migration
Prerequisites
Section titled “Prerequisites”
Basic familiarity with calling contract functions on Etherscan
A wallet containing OLD_MKR tokens (deployed April 2016)
ETH for gas fees on Ethereum mainnet (typically 0.01–0.02 ETH is sufficient)
Access to your wallet on Etherscan (e.g., MetaMask, WalletConnect)
Guide
Section titled “Guide”
Contract Addresses
Section titled “Contract Addresses”
Before starting, review these contract addresses. Always verify addresses from multiple trusted sources before interacting:
OLD_MKR Token:
0xc66ea802717bfb9833400264dd12c2bceaa34a6d
MKR Token:
0x9f8f72aa9304c8b593d555f12ef6589cc3a579a2
Redeemer (OLD_MKR to MKR):
0x642ae78fafbb8032da552d619ad43f1d81e4dd7c
SKY Token:
0x56072C95FAA701256059aa122697B133aDEd9279
Converter (MKR to SKY):
0xA1Ea1bA18E88C381C724a75F23a130420C403f9a
Important Information
Section titled “Important Information”
What is an ABI?
Section titled “What is an ABI?”
An Application Binary Interface (ABI) tells tools like Etherscan how to encode and decode function calls for a smart contract. Because the OLD_MKR token contract is not verified on Etherscan (the token predates Etherscan’s contract-verification feature!), you must supply an ABI so Etherscan can render the contract’s functions and enable reads/writes to the OLD_MKR token and the Redeemer contracts.
Technical Context
Section titled “Technical Context”
The OLD_MKR token was built using an early MakerDAO token library. While the original source code is not publicly verified on Etherscan, the
Redeemer UI source code
on GitHub documents the same contract addresses and can be used for cross-verification.
Security Reminders
Section titled “Security Reminders”
Only interact with contracts on Ethereum mainnet that you have independently verified.
Never paste sensitive keys or seed phrases into any website. Etherscan only requires wallet signatures via your wallet provider.
Double‑check that allowances and amounts match your intended full balance before submitting transactions.
Only approve the official Redeemer as the
spender
:
0x642ae78fafbb8032da552d619ad43f1d81e4dd7c
. Approving any other contract can grant it permission to transfer your OLD_MKR and lead to irreversible loss. Verify the spender address character‑by‑character before signing. If you made a mistake, promptly revoke the approval using Etherscan’s Token Approval Checker:
https://etherscan.io/tokenapprovalchecker
Step 1: Setup Custom ABI on Etherscan
Section titled “Step 1: Setup Custom ABI on Etherscan”
Because the OLD_MKR contract is not verified on Etherscan, you must add its ABI manually so Etherscan can render its functions.
Sign in to Etherscan and open
Contract Custom ABI
.
Select Add.
In the Add a new custom ABI modal, enter:
Title:
OLD_MKR Token
Address:
0xc66ea802717bfb9833400264dd12c2bceaa34a6d
Custom ABI: paste the standard ERC‑20 ABI below (defines
transfer
,
approve
,
balanceOf
, etc.)
[
{
"constant"
:
false
,
"inputs"
: [
{
"name"
:
"
_spender
"
,
"type"
:
"
address
"
},
{
"name"
:
"
_value
"
,
"type"
:
"
uint256
"
}
],
"name"
:
"
approve
"
,
"outputs"
: [{
"name"
:
""
,
"type"
:
"
bool
"
}],
"payable"
:
false
,
"stateMutability"
:
"
nonpayable
"
,
"type"
:
"
function
"
},
{
"constant"
:
true
,
"inputs"
: [],
"name"
:
"
totalSupply
"
,
"outputs"
: [{
"name"
:
""
,
"type"
:
"
uint256
"
}],
"payable"
:
false
,
"stateMutability"
:
"
view
"
,
"type"
:
"
function
"
},
{
"constant"
:
false
,
"inputs"
: [
{
"name"
:
"
_from
"
,
"type"
:
"
address
"
},
{
"name"
:
"
_to
"
,
"type"
:
"
address
"
},
{
"name"
:
"
_value
"
,
"type"
:
"
uint256
"
}
],
"name"
:
"
transferFrom
"
,
"outputs"
: [{
"name"
:
""
,
"type"
:
"
bool
"
}],
"payable"
:
false
,
"stateMutability"
:
"
nonpayable
"
,
"type"
:
"
function
"
},
{
"constant"
:
true
,
"inputs"
: [{
"name"
:
"
_owner
"
,
"type"
:
"
address
"
}],
"name"
:
"
balanceOf
"
,
"outputs"
: [{
"name"
:
"
balance
"
,
"type"
:
"
uint256
"
}],
"payable"
:
false프로젝트로 돌아가기