HostHostDeFi › Library › Is sUSDe safe on Monad?
Is sUSDe safe on Monad? The ten-score row
sUSDe on Monad grades E (10) on our September 26, 2026 read — the lowest score this series has published: mintable, pausable, balance-rewritable, thin, small holder base.
Ethena's sUSDe on Monad is the lowest-scored page this series has ever published: E (10) on our September 26, 2026 snapshot. Three bad flags on the contract — it can mint new supply, it can pause or blacklist transfers, and the owner can change balances — plus a bad flag on the market — thin liquidity, fragile and easy to move — and a warn for a small holder base. The numbers behind it: ~$1.31B reported cap, ~$742 of tracked liquidity, ~168 holders, 68 days live, ~$91 of daily volume.
That liquidity figure is not a typo. Seven hundred forty-two dollars of tracked pool depth, on a token whose reported market cap rounds to $1.3 billion.
The ten-score, decomposed
Every prior D and E in the series had something working for it — a renounced freeze, a real pool, an identifiable operator. sUSDe-Monad has none of those on this read. The contract surface is the full powered stack (mint, freeze, balance-writes — all the verbs that let a contract act on you rather than for you), and the market surface is functionally absent: a $742 pool on a billion-dollar cap is a ratio of about 0.00006%, the thinnest we've ever printed.
~168 holders after 68 days and ~$91 of daily volume complete the picture: this is a deployment that exists on the chain almost as a placeholder — the instrument is real, the market isn't. On a normal token a thin pool is a liquidity footnote; here it's a bad flag because below some threshold, "pool" stops describing a market and starts describing a rounding error.
Why the market cap is the misleading number
The $1.31B figure is the asset's reported cap — sUSDe's size across the system — not the value sitting on Monad. The deployment's own circulating supply is ~16.9M units at ~$1.23, which is about $20.8M of actual Monad-side float. Even that honest number dwarfs the $742 pool by four orders of magnitude: essentially none of the on-chain float could exit through the on-chain door.
This is the same mirage-cap discipline the series applies to PYPLX and XL — read the reported cap as a claim about the asset, read the deployment numbers as the truth about the chain, and never let one stand in for the other.
Same wrapper, different planet
The comparison that makes this page legible is its sibling: sUSDe-Ethereum at E (29) shares the identical powered contract surface — same mint, same freeze, same owner-write stack — but sits on $24.5M of liquidity and ~12.1K holders. Two E's, and the 19-point gap between them is entirely the market: the checklist graded the same contract twice and separated them by what the chain actually did with it.
That's the pair's real lesson. A powered contract on a chain where nobody trades it is not "safer" — it's the same risk with a smaller audience. The Monad deployment earns the lower score because thin markets compound contract risk: an owner who can mint on a chain with no depth can manufacture exits that a deep market would absorb.
What Monad deployment means for a yield wrapper
Worth asking why sUSDe is on Monad at all: new chains court DeFi primitives early, and a yield-bearing dollar is exactly the kind of collateral primitive a fresh ecosystem wants. A 68-day-old, ~168-holder deployment is what "planted a flag" looks like — real contract, real powers, negligible adoption so far.
The honest forward statement this page can make: if Monad's DeFi graph grows, sUSDe-Monad's holder count and pool will follow, and the market-side bad flags will retire mechanically. The contract-side stack won't — that part is architectural, and it's the part the E is really about.
Reading an E-10 correctly
The score needs the right frame: a 10 is not "ten times worse than a 50." The checklist's bad flags are roughly independent statements — this page simply has all of them firing at once: powered contract, invisible depth, tiny holder base. It's a saturated read, the record of a deployment where nothing the checklist measures is going right.
And the symmetric honesty applies: nothing in the snapshot claims the powers were used. 68 days of existence with all verbs live is 68 days of "could." That's what the number records — capability and absence of market, dated.
The $91 a day, in context
Daily volume of ~$91 deserves its own stare: on this page it isn't a thin market — it's the absence of one. Roughly what a single wallet moves in a transaction, printing as the entire venue's throughput. For comparison the series' other "quiet" markets post hundreds of thousands; $91 is the lowest volume figure we've printed on a page whose reported cap tops a billion.
Pair it with the pool number and the shape completes: $742 of depth, $91 of flow, 168 wallets. It's the deployment equivalent of a store with the sign up but no shelves — formally open, practically not. The snapshot records exactly that, dated.
Why deployments like this exist at all
Worth a fair paragraph for the non-sinister explanation: new-chain deployments are routinely planted ahead of demand — a protocol wants its primitive available when the ecosystem's DeFi arrives, not after. Monad's sUSDe may simply be early. The checklist doesn't grade intent, but the reader can hold both facts: the deployment is probably strategic, and it is currently empty. Both are true at once, and the E-10 doesn't need the strategy to fail to be accurate.
The forward test is mechanical: watch the holder count and the pool. If Monad's DeFi arrives, this row becomes a B-or-better deployment wearing its history; if it doesn't, the row stays a powered contract on an empty venue — which is what it is today.
Why the batch pairs them
The two sUSDe pages exist as a pair for one reason: they prove the checklist grades markets and contracts independently. Same powers, 19 points apart — the entire difference is $24.5M of liquidity and 12K holders versus $742 and 168. It's the cleanest evidence in the series that a powered contract on a dead venue is scored as worse than the same contract on a live one — the market's condition is part of the safety read, not just the code's.
The worst number on the page
If one figure carries the whole read, it's the $742 — not because it's the smallest liquidity we've seen (PYPLX posts zero), but because it's attached to a contract that can mint. On PYPLX the zero-pool shape pairs with a fixed supply; here the pair is "infinite mint plus no market" — the single most dangerous combination the checklist sees, because a print event on this venue wouldn't even need to dump on a pool to matter. That's the argument the E-10 makes in one number.
Holding it, honestly
If you hold sUSDe on Monad you hold ~$1.23 of a yield share whose contract can mint, freeze, and rewrite balances — on a chain where the tracked exit is $742 deep and ~$91 trades a day. The E-10 is the checklist's most complete warning: the contract can hurt you and the market can't help you. Whatever Ethena's reputation is worth on Ethereum, on Monad it's carrying the entire deployment.
Frequently asked
Is sUSDe safe on Monad?
E (10) on our Sept 26, 2026 read — the lowest grade we've published. Powered contract (mint, freeze, balance-writes) plus bad thin-liquidity and small-holder flags.
Why is the liquidity only $742?
The tracked DEX pool for sUSDe on Monad held ~$742 at snapshot — the deployment's real market hasn't formed; holders route via bridge or off-chain venues.
Is sUSDe on Monad the same token as on Ethereum?
Same staking wrapper, different deployment — identical powered contract surface, but a market that is functionally absent (168 holders, ~$91/day volume vs Ethereum's 12.1K holders and $24.5M pool).
Can sUSDe on Monad be minted?
Yes — the mint flag is live on this read, as are freeze and owner balance-writes. All three powers are the design of the deployment.
Is the $1.3B market cap real?
It's the asset's reported global cap, not Monad-side float — the deployment's own circulating supply is ~16.9M units (~$21M). The checklist separates the two; the cap figure describes the asset, not this chain's market.