Let me concede something upfront: Bybit listing cmETH is, at the listing-page level, a perfectly reasonable thing for an exchange to do. Liquid restaking tokens are a category, the category has demand, and Bybit — with around $9.2B in daily volume and roughly 970 trading pairs — has the order book to support a thin spot market in a token most CEX users will never touch on-chain. As a product decision, that is fine.
What is not fine is the framing.
cmETH gets listed and the crypto press treats it as "Bybit adds liquid restaking exposure." One ticker. One line in the listing announcement. The reader walks away with the impression that they are buying one thing, when what they are actually buying is three things glued together by smart contracts, each with its own trust assumption, each with its own failure mode. The packaging hides the stack.
I think this matters because the stack does not collapse linearly. Layer one is fine 99% of the time. Layer two is fine 99% of the time. Layer three is fine 99% of the time. The product of three 99%s is not 99%. And when one layer cracks, the others do not protect you — they propagate. Here is what is actually in the ticker.
The First Layer Is Just Ethereum, and Most People Forget That
Underneath cmETH is mETH. Underneath mETH is ETH. Underneath ETH is a validator set running consensus, attesting blocks, and subject to the slashing conditions in the Ethereum protocol. If you hold cmETH, you are — at the deepest layer — long Ethereum staking. That is the foundation, and it is the most boring layer, which is exactly why it gets skipped.
It gets skipped because Ethereum staking has performed well. Yield is what it is, slashing events are rare, and the validator set is large enough that idiosyncratic failure of any single operator is a non-event for any reasonable basket. The mental model "ETH staking is solved" is, for most practical purposes, correct.
But "mostly correct" is not the same as "irrelevant to risk pricing." A correlated event at the consensus layer — a client bug, a network partition that lasts long enough to trigger inactivity leak, a mass slashing of a popular client implementation — touches every staked ETH, including yours. And the way restaking tokens are constructed, you do not get to opt out of this risk by holding the wrapper. You inherit it.
This is the layer where I think most retail buyers of cmETH stop reading. They see liquid restaking, they see a yield number, they assume the yield is paying them for some abstract "DeFi risk", and they do not internalize that the floor under the entire stack is the same floor under every staked ETH on the network. Concede the floor is solid. Then keep going up.
The Second Layer Is mETH, Which Is Already a Trust Promise Before Restaking Enters the Picture
mETH is Mantle's liquid staked ETH. The way to think about it — and this is where I get genuinely excited about the mechanics, sorry — is as a tokenized claim on a basket of ETH validators operated by Mantle and partners. You deposit ETH, you receive mETH, the underlying ETH gets staked, the yield accrues to the exchange rate between mETH and ETH, and you can in principle redeem mETH back to ETH through the protocol's exit queue or sell it on a secondary market at whatever discount the market is pricing that day.
That second word matters. Discount. Liquid staked tokens trade at a discount to their underlying when redemption is slow, when sentiment is bad, or when there is a queue forming. The same dynamic applies to mETH, which has thinner secondary liquidity than the market leader, which means the discount in stress can be wider, and the depth on the bid side can disappear faster than the order book on a calm day would suggest.
So now you are not just long ETH staking. You are long ETH staking through a wrapper whose price can decouple from its NAV during exactly the moments you would want to exit it. That is a second risk, layered on top of the first.
And then, on top of that, there is the operational layer. mETH's validator set is operated by a specific set of node operators chosen by Mantle. Those operators are subject to the slashing conditions of Ethereum, which means slashing on the underlying flows back to mETH holders, which means it flows back to cmETH holders. Mantle's documentation discloses operator selection criteria, fee structure, and the address of the staking contract — that material is public, and anyone evaluating cmETH should pull the contract address and read the operator set before pulling the trigger. The receipt of who is staking your ETH is on-chain. The question is whether you have read it.
I have not been able to verify, from grounding I trust for this piece, whether mETH's smart contract has been formally audited at the version currently underpinning cmETH. I am going to flag that gap rather than fill it with a guess. It is the kind of thing that ought to be on the listing page of any exchange that adds the wrapped version, and almost certainly is not.
The Third Layer Is Where Restaking Stops Being Restaking and Becomes Something Harder to Price
Here is where it gets really interesting, and where I want to slow down.
cmETH is mETH that has been deposited into a restaking protocol — in cmETH's case, the Mantle-led restaking layer — to provide cryptoeconomic security to additional services. Those additional services are called AVSs in the EigenLayer vocabulary, but the structure is the same wherever it appears: your underlying ETH is being used to backstop services beyond Ethereum's own consensus, and in exchange for that, you earn additional yield, and in exchange for that additional yield, you accept additional slashing conditions.
That is the trade. It is, in principle, fair. The problem is that the slashing conditions for those additional services are defined by the services themselves, and the universe of possible slashing conditions is not bounded by Ethereum's protocol. A buggy AVS can specify slashing conditions that fire on ambiguous events. A well-designed AVS can specify conditions that fire correctly but in a way the depositor did not model when they signed off on a single-paragraph product description.
Let me run a small math teardown here, using the only fee structure I can cite cleanly: Bybit's. The maker fee on Bybit spot is 0.10% and the taker fee is also 0.10%. Suppose you buy 1 cmETH at the listing price as a taker — that is 0.10% paid on entry. Suppose, three months in, the AVS basket cmETH is restaking into has had a slashing event that wiped 2% of the underlying. You exit as a taker — another 0.10%. Round-trip transaction cost: 0.20%. The slashing event you absorbed: 2.00%. Ratio: ten to one. The fee math is the rounding error. The slashing math is the position. And in stress, the realized exit price is below NAV by another wedge — call it 1% on a normal stress day for a thin LRT — which brings your total realized drag to 3.20% against the 0.20% you priced going in. Sixteen to one. That is the layering effect.
That ratio — small fee, large slashing tail, secondary discount on top — is the thing that gets obscured when an exchange lists the token at a tight spread and a clean ticker. The spread is what you see. The slashing tail is what you don't, until you do.
And there is one more thing. When you buy cmETH on Bybit and hold it on Bybit, you are also adding a fourth layer to the stack — the exchange's custody — which I am not going to go into here because that is a separate piece. Bybit is licensed by Dubai's VARA and Cyprus's CySEC and runs a verified proof-of-reserves attestation last dated March 12, 2025, with a CER security score of 9.1. Those are real credentials. They are also the floor under the on-exchange holding period, which is the layer the prior three layers sit on top of when the buyer never withdraws.
This started as a short note about a Bybit listing announcement and turned into a four-layer risk decomposition that I think is the right way to read every liquid restaking listing from here forward. Tickers compress complexity. The job of the reader is to decompress it. cmETH happens to be the example sitting in front of me this week because of the Bybit listing, but the structural argument applies to every LRT that ends up on a CEX between now and the next cycle peak. This piece does not cover the specific composition of the AVS basket cmETH is currently exposed to — that shifts, and I would want fresh on-chain data before naming the specific protocols. It does not cover the tax treatment of restaking yield, which varies by jurisdiction and is not something I am qualified to advise on. And it does not cover the relative pricing of cmETH against other LRTs on competing venues — that is a comparison piece, and this is an analysis piece. Each of those is a separate argument worth its own day.
FAQ
What exactly is cmETH and how does it differ from mETH?
mETH is Mantle's liquid staked ETH — a tokenized claim on staked ETH validators run by Mantle and partners. cmETH is mETH that has been further deposited into a restaking protocol to provide cryptoeconomic security to additional services. The difference is one extra layer of slashing exposure: cmETH holders accept the slashing conditions of the restaking layer in exchange for additional yield beyond ETH staking yield. Same base asset, additional contractual obligations.
Does Bybit's proof of reserves cover the cmETH risk stack?
Bybit's most recent proof-of-reserves attestation is dated March 12, 2025, with a verified reserve status and a CER security score of 9.1. PoR attestations cover the exchange's custody of customer balances — they do not attest to the solvency of the issuer of the wrapped token, nor to the safety of the underlying restaking contracts, nor to the operator set running mETH validators. Reserves on Bybit are one of four risk layers and the only one the exchange's PoR speaks to directly.
What fees does Bybit charge for trading cmETH?
Bybit's standard maker fee is 0.10% and the standard taker fee is also 0.10%. A round-trip taker trade costs 0.20% in fees before any spread cost. Volume-tier discounts apply to high-volume accounts but the listed numbers are the default for retail-sized orders. The fee is paid in the quote currency of the pair, and it sits inside an exchange with around 970 listed pairs, which is a useful sense of where cmETH ranks in attention terms inside Bybit's catalog.
Can I deposit cmETH to Bybit without KYC?
Bybit's listed minimum deposit is $1 USD equivalent and KYC is not required for the deposit step itself per the exchange's published policy structure. KYC is generally required for withdrawal at meaningful size and for higher-tier features such as elevated futures limits. For the specific operational answer on a given day, the exchange's own help center is the authoritative source — policy in this space changes quarterly and what is true this week may not be true after the next regulator interaction.
What is the worst case for a cmETH holder during a slashing event?
The worst case is correlated slashing across the restaking layer that propagates back through mETH to cmETH and is realized in the secondary market price before the depositor can exit. Because liquid wrappers trade at variable discounts to NAV during stress, the realized loss can exceed the protocol-level slashing percentage by the amount of that discount widening. The depth of that gap depends on secondary liquidity at the moment of exit, which is exactly the moment liquidity tends to be thinnest.
Is cmETH suitable for high-leverage trading on Bybit?
Bybit's maximum leverage on futures is 100x, but that does not mean any spot asset should be held at that ratio of size. cmETH carries embedded yield-protocol risk that does not exist in plain BTC or ETH derivatives, so identical leverage figures carry materially different risk profiles. I would treat cmETH as a spot position first, model the four-layer risk stack against the expected yield, and only then ask whether a derivative wrapper is even necessary before pricing the leverage on top.
How does cmETH compare to other liquid restaking tokens?
This piece deliberately does not run that comparison because the relative composition of the underlying AVS baskets changes meaningfully across protocols and across weeks. A useful comparison requires fresh on-chain data on each LRT's current restaking exposure, the operator sets running each underlying validator basket, the fee structures of each restaking layer, and the secondary market depth on the exchanges where each token is listed. That is a separate analysis piece worth its own pull from primary sources rather than a paragraph appended here.