History matters: MKR is no longer the center of gravity

MKR used to be the Maker Protocol’s “equity-like” control and backstop token. That description is still technically true in legacy documentation, but it is no longer the practical truth for the ecosystem’s forward path.

MakerDAO rebranded to Sky in 2024 and introduced USDS alongside a “converter contract” for free, liquid conversion between DAI and USDS. If you're planning a token migration, our token launch checklist is a useful starting point.

For governance, the big structural shift is that SKY has been voted in as the sole governance token, and MKR holders are pushed through a migration process that includes an explicit Delayed Upgrade Penalty that began in September 2025, as described in the upgrade hub.

On the technical side, official developer docs describe the converter mechanics with a fixed 1:24,000 ratio (with important caveats about minting permissions and later governance changes).

The migration also changed MKR’s supply footprint. As of March 6, 2026, Etherscan’s token page displays 95,425.590010589256170861 MKR as the token’s “Max Total Supply” for the MKR contract.

CoinGecko’s MKR page reflects the same operational reality: it does not report circulating supply and shows a total supply around 95k, while also listing a much higher “max supply” figure. Treat that as a signal of the migration complexity, not a clean cap table.

What MKR does inside the product (and what it used to do)

In Maker’s canonical model, MKR is (1) the governance key and (2) the recapitalization resource.

On governance, MKR voters can change core protocol parameters. Maker’s own whitepaper language is explicit that MKR holders can vote on collateral onboarding and risk parameters, the Dai Savings Rate, oracle choices, emergency oracles, emergency shutdown, and system upgrades.

On recapitalization, MKR is designed to be diluted if the system runs a deficit. Maker’s docs describe this as MKR supply increasing via debt auctions when system debt exceeds surplus, aligning governance incentives around prudent risk settings.

At the smart contract level, Maker’s technical docs describe the MKR token implementation as an ERC-20 with authorized minting and burning. That “authorized” qualifier is the governance and regulatory fulcrum. This is not a credibly neutral commodity token design.

Now the practical caveat: Sky governance has moved on-chain voting to SKY, and MKR’s role is increasingly a transitional claim on an upgrade process rather than an enduring governance instrument. The official Upgrade Hub states you can no longer vote with MKR and must upgrade to maintain governance participation.

Supply, emissions, and distribution: MKR is mutable by design

MKR supply was never meant to be a simple “fixed cap.” MakerDAO’s own early writing framed MKR as a token with supply mechanics that can contract via burning and expand via dilution under stress. For a broader framework, our token economy components overview is a good reference.

Maker’s community portal states that MakerDAO launched with 1,000,000 MKR at inception and points readers to Etherscan for the current fluctuating total.

That same early MakerDAO post adds useful specificity: at the launch of Dai, it describes 1,000,000 MKR total, with 530,000 MKR in market circulation and 470,000 MKR in the development fund as of November 5, 2017.

Fast forward to the Sky-era migration and you get the current end-state dynamic: MKR is being converted into SKY and effectively retired over time, which is consistent with today’s low on-chain MKR total supply figure.

Allocations / distribution (publicly documented)

Utility, fees, burns and mints: MKR as a balance-sheet lever

MKR’s “utility” story is cleanest when you describe it as a balance-sheet lever rather than a user token.

For a non-governance comparison, our take on fee-funded burns shows a different value-accrual pattern.

The protocol earns revenue in DAI terms, primarily through stability fees paid by vault users. In normal operation, those revenues accumulate as system surplus. When surplus exceeds a governance-defined buffer, Maker runs a surplus auction: surplus DAI is auctioned for MKR, and the received MKR is burned, reducing supply.

The Vow contract is the accounting nexus for this. Maker’s technical documentation describes Vow as the protocol’s balance sheet that receives system surplus and system debt, discharging surplus via flap auctions and covering deficits via flop auctions.

Two parameters matter for MKR value accrual under the classic model:

On the other side of the balance sheet is dilution. If collateral auctions fail to raise enough DAI to cover system debt, the protocol can initiate debt auctions in which newly minted MKR is sold for DAI to recapitalize the system. Maker’s auction docs describe this directly and explicitly tie it to MKR supply expansion.

One point that is easy to miss: MKR is not just “burned from fees.” The surplus burn is conditional on the buffer and the netting of surplus and debt, and the system can also route surplus into operational spending through governance decisions. The Maker whitepaper notes MKR holders can allocate funds from the Maker Buffer for infrastructure needs and services, funded by stability fees, liquidation fees, and other income streams.

In Sky’s later architecture, this “protocol treasury decides between reinvestment and tokenholder value” tension becomes more pronounced because governance explicitly designs upgrade penalties and reward rails around tokenholder participation. The Upgrade Hub states the Delayed Upgrade Penalty reduces SKY received per MKR by 1%, increasing by 1% every three months after it took effect in September 2025, until it reaches 100% in 25 years.

Governance rights (and the yield problem)

MKR governance is implemented through on-chain contracts that accept MKR deposits and weight votes by deposited balance. Maker’s technical docs describe DSChief as an approval voting contract where the leading proposal (“hat”) can gain administrative access to protocol variables via spells.

The system also contemplates a Governance Security Module delay. Maker’s whitepaper page states voter-approved modifications can be delayed by as much as 24 hours if governance activates GSM, allowing time to respond to malicious proposals by triggering shutdown.

Emergency Shutdown itself historically involved MKR in the ESM flow. Maker’s technical docs describe Emergency Shutdown as a last resort against serious threats, coordinated by the Emergency Shutdown Module.

Now the yield problem, from a regulatory pragmatist lens. For most of MKR’s life, the protocol avoided the most direct version of “dividends.” Value accrual was primarily a function of (a) governance rights and (b) supply contraction through buy-and-burn mechanisms.

Sky-era tooling changes that posture. Sky’s core docs describe a LockStake Engine (also called the “Seal Engine”) where users can deposit MKR in a vault position to borrow USDS, stake to earn rewards, and delegate voting power, with an exit fee applied on withdrawal that governance can change.

For comparison, our review of Mantle staked ether focuses on a yield-first token model.

Even if you treat this as “just DeFi incentives,” it moves MKR from a governance/backstop instrument toward a token that can be marketed, experienced, and regulated as a yield-bearing asset. That is not a theoretical compliance footnote. It affects how exchanges, wallets, and front ends present the token, and it raises the obvious question regulators care about: are holders reasonably expecting profits from the efforts of a managed system that routes revenue into tokenholder rewards?

Sky’s own upgrade documentation goes further by operationalizing stick-and-carrot tokenholder behavior. It explicitly instructs integrators to message users that MKR can no longer vote, and that a one-directional conversion plus a time-based penalty exists. It also notes the conversion ratio can be reduced by governance via a fee parameter in the converter contract.

That is a powerful governance mechanism. It is also, bluntly, a governance-imposed economic policy applied to tokenholders. The more MKR looks like an instrument whose economic outcomes are actively managed for tokenholder positioning, the less credible it is as a “pure utility” story.

Risk analysis (ranked), with dominant risk

Dominant risk: regulatory exposure from value accrual and managed yield

MKR’s classic framing already carries governance-token baggage because it combines (1) control rights over a system that looks like a balance sheet, (2) a recapitalization promise via potential dilution, and (3) an explicit mechanism that routes protocol revenues into tokenholder value through buy-and-burn. Maker’s own documentation makes these mechanics central, not incidental.

Sky’s later additions intensify the compliance surface area. The LockStake Engine explicitly supports “stake the deposit in the vault to earn rewards,” and governance can change exit fees. That is a highly legible “managed yield product” shape, even if implemented as smart contracts.

The migration regime adds another layer. A time-based penalty that reduces upgrade output, controlled by governance and described as amendable at any time through governance, is a governance-directed token policy with real economic consequences. It is also a mechanism that can be read as steering user behavior toward a new governance asset and away from the legacy token. That is not automatically illegal. It is automatically scrutinizable.

Net: MKR’s strongest design feature for sustainability, the ability to change economic policy through governance, is also its biggest legal vulnerability. Token flexibility and legal exposure are the same knob.

If you’re doing tokenomics consulting on governance-token migrations, the Maker→Sky transition is a useful case study in how protocol mechanics, UX, and legal risk all converge. It also shows why “just add yield” is rarely a free lunch for a governance asset.

Top 3 risks

  1. Regulatory reclassification risk (security / yield product), Trigger: distribution or expansion of tokenholder rewards (staking rewards, buybacks, or other value accrual programs) alongside active governance control. Mechanism: MKR/Sky token economics tie protocol revenues and governance-controlled parameters to tokenholder benefit, and Sky docs explicitly support staking rewards flows. Who bears it: tokenholders (liquidity shocks, listings), integrators (front ends, exchanges), and governance actors (enforcement focus). Measurable indicators: new or expanded rewards programs in official docs, integrator guidance emphasizing rewards and penalties, exchange delistings or geo-restrictions, and governance votes changing fee/penalty parameters.
  2. Migration and legacy-token liquidity risk, Trigger: one-directional conversion and time-based penalties reduce willingness to hold and market-make MKR. Mechanism: the protocol-defined MKR→SKY conversion path, paired with a Delayed Upgrade Penalty, structurally pushes MKR supply toward retirement and can thin secondary liquidity, while on-chain MKR supply declines through conversion. Who bears it: late migrators, borrowers or protocols still referencing MKR markets, and passive holders who treat MKR as “still the governance token.” Measurable indicators: falling MKR total supply on Etherscan, worsening DEX depth, widening spreads, and governance communications reiterating that MKR can no longer vote.
  3. Balance-sheet tail risk and recapitalization uncertainty, Trigger: a rapid collateral shock or auction failure that creates bad debt beyond buffers. Mechanism: Maker’s own documentation describes deficits leading to MKR minting via debt auctions, and surpluses leading to MKR burning via surplus auctions. If governance changes or disables parts of this machinery during migration, the backstop story can become harder to model for the legacy token. Who bears it: stablecoin users (peg stability), governance token holders (dilution or loss of value accrual), and integrators relying on predictable backstop behavior. Measurable indicators: rising protocol debt metrics, governance spells modifying auction modules or buffers, and documentation updates that retire or replace flop/flap-style mechanisms.

MKR’s token design has always been legible as governance equity with an emergency recapitalization mandate. The Sky transition keeps that lineage, but it also makes the regulatory trade-off sharper by blending governance authority, behavioral penalties, and explicit yield tooling into a single managed system. That may be operationally effective. It is not compliance-neutral.



This article is part of our Tokenomics Deep Dive series.