CoinYQ Dossier

Wrapped M: the static-balance bridge between M0's rebasing $M and DeFi

Wrapped M is easy to mistake for a separately collateralized dollar token. It is better understood as an accounting wrapper: M0's $M supplies the underlying asset, while wM converts rebasing behavior into a conventional ERC-20 balance and exposes yield through explicit claims. That convenience makes the exact earning permissions, claim-recipient rules, solvency assumptions and upgrade authority central to what a holder actually owns.

From M0's system launch to a dedicated wrapper

M0 announced its core protocol and Two-Token Governor deployment on Ethereum Mainnet on May 7, 2024, with permissioned minter and validator roles and limited-availability $M minting and redemption. That announcement describes the underlying monetary network, not a wM holder's direct ownership of its Treasury collateral.

M0's deployment registry records Wrapped M's Ethereum deployment on August 14, 2024. The wrapper was introduced to solve an integration problem created by $M's rebasing balance: DeFi applications often need a static ERC-20 balance even when the underlying asset has an index-based yield mechanism.

What is live versus what remains a protocol assumption

The live product documented by M0 is a deployed wrapper with wrap, unwrap, transfer, earning, yield-query, claim and excess-management functions. The technical specification gives concrete signatures and accounting variables, while Etherscan identifies the Ethereum address as a verified proxy.

M0 documents a solvency invariant requiring the wrapper's $M balance to cover non-earning supply plus projected earning supply. This is the contract design and stated invariant; it should not be rewritten as an independent reserve audit or as a promise that wM itself confers a legal claim on short-term Treasury assets. The broader M0 platform's issuance, validator and redemption process is a related layer and may involve permissioning.

Holder rights, yield routing and delegated administration

A holder can use the wrapper's on-chain wrap and unwrap paths, transfer wM as an ERC-20, and—if approved for earning—claim yield calculated from the underlying $M index. A user-set recipient has priority over a governance override, with the account itself as the default. An EarnerManager admin can set earning status and a fee rate; M0 documents fees of up to 10,000 basis points on claimed yield for managed accounts.

These mechanics are not the same as governance voting rights, equity, reserve ownership or a contractual redemption right against M0's collateral. The cited materials describe governance and Registrar controls over system parameters and recipient overrides, but do not grant wM holders a vote merely because they hold wM.

The control plane is part of the asset's identity

The Ethereum token page shows a verified proxy pointing to an implementation contract, and M0's security section labels MigrationAdmin as fully trusted to change that implementation. M0 also says the Registrar is the source of system parameters, MToken is assumed to function correctly, and admins are trusted to manage earning status. These controls make upgrade, parameter, eligibility and recipient governance material risks rather than implementation footnotes.

M0 lists three Wrapped M reviews from summer 2024—ChainSecurity, Three Sigma and Kirill Fedoseev. Those reviews provide useful historical security evidence, but they do not eliminate proxy, bridge, underlying-$M, administrator, or market-liquidity risks after deployment and subsequent upgrades.

How the project changed

  1. 2024-05-07
    M0 core and TTG deployed on Ethereum

    M0's deployment registry dates the platform and Two-Token Governor deployment to this date; the historical launch notice describes permissioned minter/validator roles and limited-availability $M minting and redemption.

  2. 2024-07 to 2024-08
    Wrapped M underwent independent security reviews

    M0's audit index records ChainSecurity, Three Sigma and Kirill Fedoseev Wrapped M reviews during July-August 2024.

  3. 2024-08-14
    Wrapped M deployed on Ethereum Mainnet

    M0's deployment registry records the canonical Ethereum wM deployment date and links it to the WrappedMToken v2 source.

  4. 2024 onward
    wM operates as a static-balance ERC-20 wrapper

    The current documentation describes live wrap/unwrap, earning-mode, explicit-yield-claim, recipient and excess functions; later V2 documentation adds delegated EarnerManager administration and a proxy-upgrade path.

  5. 2026-08-25
    Current reviewed state

    The current M0 docs and Etherscan page identify wM as a six-decimal verified proxy at 0x437cc33344a0B27A429f795ff6B469C72698B291, with supply shown as contract state rather than a documented vesting allocation.

Evidence and primary sources

Last evidence review: 2026-08-25

What is WrappedM by M0?

wM is the standard-ERC-20 representation of M0's $M. Native $M rebases as yield accrues, but wM keeps balances static and exposes separate earning, accrued-yield, and claim operations. Users can wrap $M into wM and unwrap wM back into $M through the contract; the holder's on-chain claim is to the token mechanics and underlying $M delivered by that contract, subject to contract solvency and protocol rules. Nothing in the cited technical documentation establishes that wM holders own M0's reserves, receive equity, or have a direct legal claim on Treasury collateral.

What problem does WrappedM by M0 solve?

Rebasing balances are awkward for integrations that expect conventional ERC-20 accounting, including lending markets, AMMs, and other DeFi systems. wM addresses that software problem by preserving a fixed stored balance while calculating yield from the underlying $M index and allowing an explicit claim. The current product is this wrapper and its on-chain accounting; M0's broader stablecoin issuance and redemption network is a related underlying protocol, not a promise that every wM holder can directly redeem against Treasury assets.

How does WrappedM by M0 work?

A holder calls wrap to deposit $M and receive wM, or unwrap to burn wM and receive $M. wM uses six decimals and a non-rebasing ERC-20 balance model. Accounts are non-earning by default; an approved governance or EarnerManager path can place an account in earning mode. For an earner, a principal is derived from the balance and the wM index is derived from the $M index; accrued yield is calculated from principal × current index minus the stored balance and is claimed explicitly. A user can set a claim recipient, while governance can provide an override; an EarnerManager admin may set a fee rate on managed earning accounts. The contract documentation says the wM contract's $M balance must cover non-earning supply plus projected earning supply. The Ethereum deployment is a proxy, so Etherscan's verified page shows an implementation address and M0 documentation identifies MigrationAdmin as a fully trusted role able to change implementation.

Key facts

  • M0's deployment registry dates the Ethereum Wrapped M deployment to August 14, 2024; the Ethereum token address is 0x437cc33344a0B27A429f795ff6B469C72698B291.
  • wM has six decimals and is a non-rebasing ERC-20 wrapper; $M is the rebasing underlying token.
  • Wrapping deposits $M and creates wM; unwrapping burns wM and returns $M through the wrapper contract.
  • Earning is not automatic for every holder: accounts must be approved and explicitly placed in earning mode; non-earning balances do not accrue wM yield entitlement.
  • Yield is claimable explicitly rather than appearing as an automatic balance rebase, and claim recipients can be configured.
  • M0's technical docs describe a solvency invariant in which the wrapper's $M balance covers non-earning supply plus projected earning supply; this is a protocol design assertion, not independent reserve insurance.
  • EarnerManager admins can approve earners and set fee rates; governance can override claim recipients through the Registrar.
  • Etherscan identifies the Ethereum deployment as a verified ERC-20 proxy with six decimals and reports a max-total-supply snapshot of 84,714,976.673859 wM; supply is not a fixed cap in the cited materials.
  • M0 lists ChainSecurity, Three Sigma, and Kirill Fedoseev Wrapped M audits dated July-August 2024, but an audit is not a guarantee against later upgrades or economic loss.

Official links

Categories

Related coins

Frequently asked questions

Is wM the same token as M0's $M?

No. wM is a non-rebasing ERC-20 wrapper around $M. $M's balance rebases automatically; wM keeps a static stored balance and handles eligible yield separately.

Can every wM holder claim yield?

No. M0's documentation says accounts are non-earning by default and must be approved through governance or an EarnerManager path before earning mode is enabled. Non-earning holders do not accrue the documented wM yield entitlement.

Does holding wM give me a legal redemption right to M0's Treasury collateral?

The cited sources document an on-chain unwrap operation that returns $M, but they do not establish a direct legal claim by every wM holder on Treasury bills, M0 equity, or reserve assets. Treat the practical right as the smart-contract wrap/unwrap and solvency model, not as a separately documented collateral redemption contract.

How is wM yield paid?

An earning account accumulates yield from a principal and the index derived from $M. claimFor calculates the accrued amount and sends it to the configured recipient; a managed account can have an administrator fee deducted from claimed yield.

Is wM supply fixed, vested, or capped?

The cited sources do not document a vesting schedule or a fixed maximum cap. Etherscan reported a max-total-supply snapshot of 84,714,976.673859 wM when opened; because wM is minted by wrapping $M and burned by unwrapping, supply should be read as contract/accounting state rather than a token-allocation schedule.

Can the wM contract be upgraded or administratively changed?

Yes, the Ethereum deployment is a proxy and M0's current technical documentation says MigrationAdmin is a fully trusted role that can change the contract implementation. Governance and EarnerManager also influence earning eligibility and claim-recipient administration.

External trackers

Choose a tracking site for WrappedM by M0: