Magma Staking
Magma is a Monad-native liquid-staking protocol. It accepts MON and issues non-rebasing gMON, while validators chosen by governance receive the delegated stake. Redemptions take place later through Monad’s undelegation process, with a secondary instant route that depends on outside liquidity. The 2026-08-16 survey reported only about $1.08 million, all on Monad. That is far below the institutional size floor, so we do not open an individual validator, slashing, governance and exit review until it clears the floor. The unapproved Monad settlement layer is another barrier.
- TVL sustained above the retired TVL threshold for 30 days
Watched nightly: a warning on its venues or files, or a cited document that changes, reopens the memo. The first confirmation is due 2026-11-16.
The research file
Mechanism applicability
Magma accepts MON and issues gMON, a non-rebasing receipt whose exchange rate is meant to increase with delegated staking rewards. Its CoreVault assigns pooled stake across an active validator set and manages withdrawals and rebalancing. Optional gVaults allow users to target individual validators. These facts show a live liquid-staking product, but they do not clear the size floor.
Control, loss and exit applicability
Magma governance approves validator operators, so holders depend on controls for validator selection, delegation and rebalancing, as well as smart contracts, Monad consensus, slashing results and the gMON market. Deposits happen at once, while redemptions use a later ERC-7540-style process tied to Monad epochs. Magma also shows an instant route through 0x. That route depends on market liquidity and execution instead of native redemption.
Current observation and perimeter
The DefiLlama protocol API read on 2026-08-16 classified Magma as Liquid Staking and reported approximately $1.08M, entirely on Monad. Magma’s current site and documentation also limit gMON to Monad mainnet. This review does not count historical points participation or token circulation as protocol TVL.
Why the class rule decides
A representative $1M practice allocation would approach the entire measured venue, and the current scale cannot hold an $8M book. The shared version-1 rule for protocols below material size therefore decides the judgment before a full review of validators, slashing, governance, audits, incidents and stressed exits. Reopen the individual review after attributable Magma TVL remains above the size floor for 30 consecutive days and Monad receives an approved chain decision. Both conditions start diligence, not approval.
Research status
This is a capacity-unproven record for Magma Staking, not a quality rejection or approval. Reported TVL says how big the venue is, not what the client owns, who can change the rules, or how a position exits at a proposed size. The individual review opens when the protocol clears the size floor.
Sources
The claims above trace to these. Where a number could not be independently verified, the thesis says so.
- Magma docs — liquid staking and gMON · primary · accessed 2026-08-16
Supports: gMON, non-rebasing receipt, validator whitelist, Monad - Magma docs — protocol architecture · primary · accessed 2026-08-16
Supports: CoreVault, gVault, validator delegation, asynchronous redemptions - Magma — current staking interface · primary · accessed 2026-08-16
Supports: Monad mainnet, gMON, unstake wait, 0x instant route - Monad docs — staking withdrawal lifecycle · primary · accessed 2026-08-16
Supports: epochs, undelegation, withdrawal delay, validator delegation - DefiLlama — Magma Staking survey record · secondary · accessed 2026-08-16
Supports: current TVL, Monad, Liquid Staking category, survey observation
Inherited controls
The research above describes the protocol layer. Every position also inherits the asset it holds and the chain it settles on. The layer with the most administrative power sets the position’s effective control; that describes control, not quality or suitability.
| Chain | Verdict | Control | Control constraint |
|---|---|---|---|
| Monad | Approved with limits | Governed, no freeze | the L1 has a public validator path, but its short production record, single initial client lineage, and Foundation-directed delegation keep stake and operations concentrated. |