Between July 9 and July 10, 2026, the circulating supply of MegaUSD (USDM), the native stablecoin of the MegaETH network, fell from about 293 million dollars to about 116 million dollars. That is a drop of roughly 47 percent in 24 hours, and close to 60 percent down from the level of two days earlier. Over the same window the token barely moved off a dollar. It traded inside a range of about a fifth of a cent, with a 24 hour low near 0.9972 and a high near 1.004. We read the current supply directly off MegaETH mainnet before writing this, and it matched the public trackers to within a fraction of a percent.
The combination matters, because it decides which word is honest. A stablecoin whose price collapses has depegged. A stablecoin whose supply collapses while the price holds has been redeemed or unwound at par. USDM is the second case, not the first. This is a supply contraction, most likely an orderly deleverage, not a depeg and not, on any evidence we can find, an exploit. Getting that distinction right is the whole point of reading the chain instead of the headline.
This is a companion to two pieces we have already published on the same theme: our walk through Ethena's USDe, whose stack USDM is built on, and the broader case for reserves you can verify rather than take on faith. The closest cousin is our earlier read of a different shrinking synthetic dollar, Neutrl's NUSD.
What actually happened
MegaUSD is MegaETH's native dollar. MegaETH is an Ethereum layer 2 built by MegaLabs, live on mainnet since February 2026, chain id 4326. USDM is not a standalone design. Per MegaETH's own description and DefiLlama's records, it is issued through Ethena's stablecoin stack, with mint and redeem facilitated on Ethereum mainnet in USDC and the token then bridged to MegaETH. Its reserves are described by the team as tokenized treasuries, primarily BlackRock's BUIDL held through Securitize. We did not independently audit that reserve claim, and we flag it as the team's description, not our finding.
The shape of the last four days is a run up followed by a fast exit. Per DefiLlama's daily on-chain snapshots, USDM supply on MegaETH rose from about 223 million dollars on July 7 to about 244 million on July 8 to about 293 million on July 9, a gain of roughly 31 percent in two days. It then fell back to about 116 million by midday July 10. The intraday path of that fall, reconstructed from market capitalization data because the price stayed at a dollar, ran in steps through the early UTC hours of July 10, from roughly 292 million down through 191 million and 149 million to a trough near 85 million, before recovering to the current 116 million. The exact intraday figures are market capitalization derived and we treat them as approximate. The current number is a direct chain read and we treat it as exact.
What the on-chain data shows
Here is the number we can stand behind without attribution, because we read it ourselves. The live USDM token on MegaETH is the contract at 0xfafddbb3fc7688494971a79cc65dca3ef82079e7. Its symbol is USDm, it carries 18 decimals, and at MegaETH mainnet block 20,902,915 its totalSupply was 116,150,125.51 USDm. Anyone can reproduce that with a single call against the public MegaETH RPC:
cast call 0xfafddbb3fc7688494971a79cc65dca3ef82079e7 "totalSupply()(uint256)" --rpc-url https://mainnet.megaeth.com/rpc
Divide that by ten to the eighteenth for the human figure. The public MegaETH explorer shows the same total and about 27,760 holders.
One detail is worth surfacing, because it explains why almost no one has written about this yet. DefiLlama's live balance field already reflects the collapse, about 116.1 million dollars across MegaETH and a small remainder on Ethereum. But DefiLlama's daily historical chart still reads about 283.7 million for July 10, because that chart snapshots once at 00:00 UTC and the supply left after the snapshot, between roughly 03:00 and 09:00 UTC. So a dashboard reading the daily series sees a 3 percent dip, while a dashboard reading the live contract sees more than half the float gone. That gap between the snapshot and the chain is exactly the kind of thing a live check catches and a once a day aggregator does not.
The most likely cause, and what the data does not prove
We will name a likely mechanism and then be explicit about the limit of our confidence. In the weeks before this, MegaETH hosted a heavily incentivized loop that analysts had described in detail: deposit Ethena's USDe, borrow rate subsidized USDM against it, swap the USDM back to USDe, and repeat, for a leveraged yield reported around 25 percent at the top. That loop had inflated USDM's supply by several hundred percent and made Ethena related positions the majority of MegaETH's total value locked. The same commentators warned, in plain terms, that a loop like that unwinds quickly once the incentive compresses. A 31 percent supply run up into July 9 followed by a same day exit is the on-chain signature you would expect from an incentive farm reaching its crescendo and then leaving.
What we cannot prove from the chain alone is the precise trigger, whether an incentive was cut, a borrow rate flipped, or one large participant unwound first, and we are not going to assert one. We also want to correct a likely mix up in advance. There is an older, widely indexed story about MegaETH refunding a predeposit bridge amid multisig confusion. That is from late 2024 and concerns a different event. It is not the cause of this week's supply drop. The honest summary is narrow: the float that incentives brought in has left at par, the peg held while it did, and the specific catalyst is not something we can source cleanly yet.
Why a live check would have caught the exit early, and what it could not
This is the part where verification actually helps, and the part where it does not, stated honestly. A continuous read of the token's totalSupply would have shown the float leaving in real time, hours before the daily trackers updated. If you held USDM, or lent against it, or ran a strategy that assumed a deep and stable float, that live signal was available to you on-chain the entire time, for the cost of one RPC call on a loop. Watching supply is a real, cheap, early warning for exactly this failure mode, a fast redemption or deleverage, in a way that reading a once a day chart is not.
What that same check could not tell you is why, or whether the backing was ever at risk. A supply read is not a reserve audit. The peg holding through the exit is consistent with redemptions clearing at par, which is the reassuring reading, but a held peg is not proof that reserves are sound. It is only proof that, so far, everyone who wanted out got out at a dollar. For USDM specifically, the reserve claim, tokenized treasuries via a named manager, is the team's statement, and we could not independently recompute it from the chain, because that backing lives off the MegaETH chain in the Ethena and mainnet legs. That is the ceiling on what any holder side check can do here, and pretending otherwise would be the same overclaim we are trying to avoid.
Where Kerne stands
The honest comparison is about method, not size, and we need to say the size part plainly so the method part is credible. Kerne is tiny. There are about 1,115 dollars of our kUSD outstanding today, roughly five orders of magnitude smaller than USDM before this week. We are not holding ourselves up as a safer alternative at scale, because we are not at scale. What we can say is that the specific discipline this event rewards, being able to watch the float and recompute the backing yourself, is one we build on rather than ask you to trust.
Concretely: the kUSD in circulation is backed one to one by USDC in an on-chain peg module, currently about 1,116 dollars of USDC against about 1,115 dollars of kUSD, a backing ratio you can read off the chain and that we also publish, signed hourly, at our proof of reserves endpoint. That signature is our own key, not a third party's. Our first external audit, by Hexens, begins in mid July and is not yet done, and we will not call the attestation independent until it is. The margin is thin at this size, and the delta neutral leg of the design is currently flat rather than actively hedged, both of which we disclose rather than dress up. None of this is an offer or a solicitation, and nothing here is advice. It is a description of what is on-chain and what is not.
What a holder should do, on any dollar
Not as an accusation, but as a checklist you can run on anything you hold, including us. First, separate the two questions the word depeg blurs together: is the price at a dollar, and is the float stable. Read the price and the token's totalSupply as two different numbers, because this week they told two different stories. Second, ask where the backing lives and whether you can recompute it, or only read someone's statement of it. Third, if the float can move fast, watch it fast, because a daily chart is a photograph and redemptions do not wait for the next photo. We built a free tool to run these reads on any token or vault, at kerne.fi/verify, and we would rather you point it at us than take our word.
Sources and as-of times. Current USDM supply: our own direct read of totalSupply on the MegaETH mainnet contract 0xfafddbb3fc7688494971a79cc65dca3ef82079e7 at block 20,902,915, 116,150,125.51 USDm, July 10, 2026 around 16:10 UTC, cross-checked against the MegaETH explorer and DefiLlama's live balance field of about 116.1 million dollars. Price and 24 hour range: CoinGecko, about 0.9992 dollars with a low near 0.9972, July 10, 2026. Supply history and the daily versus live snapshot gap: DefiLlama stablecoin id 342. Design and reserve description: MegaETH and DefiLlama, attributed to them and not independently verified by us. Likely cause: our reading of publicly described incentive loop mechanics together with the on-chain supply signature, offered as the most probable mechanism and not a confirmed trigger. Kerne figures: our own proof of reserves endpoints, July 10, 2026. Figures are point in time, and on-chain supply and reported losses are often revised, so recompute before relying on any number here.
Verify it yourself
Run the same check on any reserve, or have it run for you.
Paste any issuer's signed attestation into the free verify tool and recover the signer, rehash the figures, and check freshness in your own browser. For a machine-signed, point-in-time read of an address you name, delivered on the page in about two minutes, the instant self-serve read is $29; a human-reviewed read is $149. A teardown like this one, commissioned on any target you name, is $499. An independent read of a counterparty you hold or allocate to is $2,500. Attestation tooling, not an audit, and not a solvency opinion.