HostDeFi › Library › Is SKY safe on Ethereum?

Is SKY safe on Ethereum? Mint by design

SKY on Ethereum grades B (75) on our September 27, 2026 read — one bad flag, a live mint, on the MakerDAO successor's governance token.

Snapshot 2026-09-27 · Ethereum · ~$10.8M liquidity · ~15,830 holders · 333 days live · ~$1.8M daily volume

SKY — the governance token of the Sky protocol, the MakerDAO successor — on Ethereum grades B (75) on our September 27, 2026 read. One bad flag: the contract can mint new supply. Everything else is clean: freeze disabled, source verified, creator under 0.01% of supply. The market: ~$1.75B reported cap, ~$10.8M of tracked liquidity, ~15,830 holders, 333 days live, ~$1.8M of daily volume.

This is the page where the mint flag stops being an accusation and starts being a design description — and where the B still isn't an A, because "by design" is still "possible."

The rebrand that kept the mint

SKY is the renamed governance token of the system formerly branded Maker — MKR upgraded and redenominated in the Sky rebrand (~333 days old on-chain, consistent with the rebrand's timing). The critical fact for this page: the migration didn't renounce the mint. Where MKR burned to rebalance and minted via governance, SKY ships with the mint authority intact — the protocol kept the lever rather than retiring it.

That's a governance choice, not an oversight: a token that funds buybacks, incentives, and treasury operations wants issuance capability. The checklist doesn't grade the policy — it grades the capability, and prints it as a bad flag because "holders can be diluted at will" is literally true regardless of who's holding the lever.

Why a mintable governance token isn't a scam-shaped risk

Worth drawing the distinction the letter can't: on a meme coin, a live mint means "the deployer can print and dump on the pool." On Sky, the mint is exercised through the protocol's governance machinery — visible, voted, slow. The risk channel is real but its shape is different: dilution here is a governance proposal away, not a private key away.

The checklist knows only the first half of that sentence. The bad flag is calibrated to the worst case — arbitrary dilution — and the B-75 rather than a D reflects the rest of the surface being clean (no freeze, no owner-write flag, verified source). The grade is fair; the texture around it is what this page adds.

~$10.8M of pool against a $1.75B protocol token

The one warn is the familiar thin-for-cap ratio: ~0.6% of reported cap in tracked depth. For SKY that ratio understates the real exit — the token trades heavily on centralized venues and the protocol's own rails — but the checklist only counts the on-chain door it can see. ~$1.8M of daily volume through that pool makes it a working venue for retail size.

~15,830 holders at 333 days is the rebrand-era holder base: the protocol's long-tail constituency plus whoever bought the renamed token since. It's a modest count for a $1.75B asset — a reminder that most of SKY's holder graph lives in exchange custody the index can't enumerate.

What a B-75 means next to the batch's D's and E's

The value of this page inside the batch is calibration: SKY carries a live mint and nothing else bad — no freeze, no balance-rewrite, no hidden owner. Compare sUSDe-Ethereum's E-29 (mint + freeze + rewrite + hidden owner) or CRV-OP's D-47 (mint + rewrite): the mint is the flag every powered token shares; what separates the letters is which other verbs are still attached. SKY has exactly one powered verb, and its B-75 is the floor of what a single live mint costs on a clean contract.

333 days: the rebrand cohort's track record

Under a year old in this form — old enough to have accumulated ~15.8K holders and a working market, young enough that the mint's exercise history in SKY form is short. The honest read of the track record: the protocol's conduct with issuance goes back much further than 333 days (in MKR form), and the snapshot only sees the new deployment. The B records what the new contract permits; the reputation that makes the permission palatable lives off-chain.

The supply story the snapshot implies

The supply fields tell their own side-story: ~23.4B circulating out of ~23.5B total — nearly all issuance already distributed, with a thin mintable remainder held back. That's the profile of a governance token whose supply schedule is mostly spent rather than mostly ahead — the mint's theoretical dilution weight is bounded by what's left to emit, not unbounded in practice.

It doesn't retire the flag — the capability is still there for the remainder and whatever governance adds later — but it calibrates it: the dilution risk on this deployment is a protocol with a schedule, not a deployer with a printer.

Why the freeze being off matters more than it looks

On the rebrand generation of tokens, the freeze question is the one that separates "governance-powered" from "operator-powered": a contract that can mint but can't freeze answers to governance over supply and nothing else; one with both answers to whoever holds the keys over your balance specifically. SKY-ETH has the first shape — the powered verb affects the denominator (supply), not the numerator (your cell).

That's the difference between a token whose rules can change and a token whose rules can change you. The B-75 says the first is live; the clean freeze flag says the second isn't.

Where SKY sits on the mint spectrum

The batch's mint spectrum, ordered by how bounded the lever is: sDAI (mint bounded to deposits — function defines the product), SKY (mint bounded to governance — function defines the policy), CRV-OP/rETH-OP (mint held by bridge reconciliation — function defines the custody), sUSDe pair (mint plus everything else — function defines the risk). SKY's slot is the second-most-defensible: the mint exists for reasons tokenomics requires, exercised through machinery that publishes its work.

A reader keeping one lesson from the batch could do worse than this ordering — the same flag means different things depending on who can call it and what it's scoped to.

The rebrand's actual lesson

One takeaway worth keeping beyond this page: token migrations are the moment protocols choose whether to narrow their powers. Sky kept the mint — a defensible choice given the tokenomics — but the snapshot's job is recording that the choice was made at all. When the next big token rebrands, the checklist's first question is exactly this one: did the new contract keep the old powers, or did the migration retire them? SKY's B-75 is what "kept them, justifiably" looks like — the flag stays, the reason is documented, and the holder decides what a bounded lever is worth.

Holding it, honestly

If you hold SKY on Ethereum you hold a governance token whose contract retains the mint lever it inherited from Maker — one bad flag on an otherwise clean, verified, non-freezing surface. The B-75 is the checklist's calibration for "powered by design": dilution is possible because issuance is a feature, and the grade keeps the two statements joined instead of resolving either one.

Frequently asked