Record sog_st_m0m
M/M
Also recorded as M, M0 M, M Token
- Lifecycle
- Active
- Issuance
- Restricted
- Reference target
- US dollar
- Primary organization
- M0 ProtocolNo additional recorded relationship
- Launch
- 2024-07-28
- Redemption
- Protocol Based
- Backing
- Tokenized asset-backed
- Stabilization
- Hybrid
- Last review
- 2026-06-21
- Evidence
- 4 source records
Reviewed assessment
Identity and current state
This summary reports reviewed facts and uncertainty. It is not a rating or recommendation.M0 base token minted by approved Minters against eligible offchain collateral, with validator oversight and selective earning balances.
| Name | M |
|---|---|
| Symbol | M |
| Aliases | M, M0 M, M Token |
| Asset class | Stablecoin |
| Lifecycle status | Active |
| Issuance status | Restricted |
| Canonical record ID | sog_st_m0m |
| Route slug | m0-m |
| Record confidence | High |
| Last reviewed | 2026-06-21 |
- Name
- M
- Symbol
- M
- Aliases
- M, M0 M, M Token
- Asset class
- Stablecoin
- Lifecycle status
- Active
- Issuance status
- Restricted
- Canonical record ID
sog_st_m0m- Route slug
m0-m- Record confidence
- High
- Last reviewed
- 2026-06-21
Record coverage
| Section | Entries |
|---|---|
| Organizations | 1 |
| Sources | 4 |
| Reserve reports | 1 |
| Reserve components | 1 |
| Model-history events | 0 |
| Regulatory notes | 0 |
| Deployments | 1 |
| Issuer-control actions | 0 |
| Open questions | 4 |
| Events | 1 |
Primary display is a navigation and summary choice only. It does not replace other organizations or imply sole legal responsibility, operational control, reserve custody, or historical continuity.
- Governance
- Protocol Governed
- Primary display organization
- M0 Protocol
- Primary display role
- Protocol operator
- Display selection mode
- Deterministic Policy
- Current relationships
- 1
- Ended relationships
- 0
- Unknown relationship state
- 0
- Freeze capability
- 0 recorded yes · 0 recorded no · 1 not recorded
- Blacklist capability
- 0 recorded yes · 0 recorded no · 1 not recorded
- Deployment control-event references
- 0
- Observed issuer-control events
- 0
- Relationship coverage
- 1 recorded relationship
| Organization | Organization category | Regulatory character | Jurisdiction | Role | Display priority | From | Until | Relationship status |
|---|---|---|---|---|---|---|---|---|
| M0 Protocol | Protocol or software system | Protocol or decentralized system | Decentralized / multi-entity | Protocol operator | Primary display | Not yet recorded | Not yet recorded | Active relationship |
M0 Protocol
- Functional role
- Protocol operator
- Relationship status
- Active relationship
- Regulatory character
- Protocol or decentralized system
- Jurisdiction
- Decentralized / multi-entity
- From
- Not recorded
- Until
- Not recorded
Mechanism
How the asset works
Reference, backing, stabilization, exit, valuation, and yield remain separate facts.- Reference target
- US dollar
- Reference kind
- Fiat
- Comparison category
- US dollar
- Target value
- Not yet recorded
- Reference methodology
- M targets one U.S. dollar through approved collateral and controlled Minter issuance.
- Public backing model
- Tokenized asset-backed
- Canonical backing types
- Other
- Reserve component categories
- Other
- Primary stabilization mechanism
- Hybrid
- Recorded model description
- Approved Offchain Collateral Under Minter Validator Framework
- Redemption / exit model
- Protocol Based
- Valuation source
- Public information is incomplete
- Yield / rebase profile
- None recorded
- Classification notes
- Protocol-issued base stable token with selective earning balances and an offchain collateral framework.
Reserve and redemption
Reserve and redemption
Recorded components, disclosures, reports, and redemption conditions remain explicit.Reserve components
- Approved offchain collateral under Minter and validator controlsOther · Component category remains broad until per-Minter collateral schedules are normalized.
| Disclosure status | Protocol Collateral and Validator Disclosures |
|---|---|
| Backing types | Other |
| Summary | M is issued by approved Minters against eligible collateral under validator and governance controls. |
| As of | 2026-06-21 |
| Profile confidence | High |
- Disclosure status
- Protocol Collateral and Validator Disclosures
- Backing types
- Other
- Summary
- M is issued by approved Minters against eligible collateral under validator and governance controls.
- As of
- 2026-06-21
- Profile confidence
- High
| Current status | Protocol Based |
|---|---|
| Settlement asset | Approved Minter Collateral or Protocol Settlement |
| Eligible parties | Approved Minters and supported protocol participants. |
| Retail access | Market or Protocol Route Dependent |
| Institutional access | Approved Minter Protocol Route |
| Minimum amount | Protocol and Minter dependent. |
| Fee | Route and network terms may apply. |
| Settlement time | Route and liquidity dependent. |
| Regional limits | Minter, interface, and compliance restrictions may apply. |
- Current status
- Protocol Based
- Settlement asset
- Approved Minter Collateral or Protocol Settlement
- Eligible parties
- Approved Minters and supported protocol participants.
- Retail access
- Market or Protocol Route Dependent
- Institutional access
- Approved Minter Protocol Route
- Minimum amount
- Protocol and Minter dependent.
- Fee
- Route and network terms may apply.
- Settlement time
- Route and liquidity dependent.
- Regional limits
- Minter, interface, and compliance restrictions may apply.
| Date | Publisher | Type | Assets covered | Record confidence |
|---|---|---|---|---|
| Not yet recorded | M0 | Protocol Collateral and Validator Framework | Other | High |
M0
Not yet recorded- Type
- Protocol Collateral and Validator Framework
- Assets covered
- Other
- Record confidence
- High
Deployments and legal context
Deployments and legal context
Network state, contract identity, legal notices, and value states remain separate.| Network | Network record state | Standard | Public deployment category | Canonical deployment type | Operational state | Recorded status | Change or proposal state | Canonicality | Canonicality record state | Verification state | Contract identity state | Contract or identifier | Freeze | Blacklist | Control events | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Ethereum | Specific network recorded | ERC-20 | Protocol-native or protocol-supported deployment | Protocol Native Token | Active | Active | No separate change state recorded | Native deployment | Canonicality recorded | Source-linked record; identifier not recorded | Identifier not recorded | Identifier not recorded | Not yet recorded | Not yet recorded | 0 | Primary M architecture; exact contract and cross-chain representation map remains a open question. |
| Date | Title | Authority / publisher | Type | Summary |
|---|---|---|---|---|
| No regulatory notes have been added yet. | ||||
No regulatory notes have been added yet.
Evidence
Evidence
Publisher, provenance, supported claims, archive state, reliability, and publication date remain separate.| Source | Publisher | Source category | Provenance | Primary or secondary | Supported claims | Archive | Reliability |
|---|---|---|---|---|---|---|---|
| M token Published Not yet recorded | M0 | Official documentation or product page Canonical: Official Documentation | Subject-controlled source | Primary source | Identity, USD Reference, Earning Balances, Non Earning Balances, Entity Model and Income | Archive index or wildcard | High |
| Minter Gateway Published Not yet recorded | M0 | Official documentation or product page Canonical: Official Documentation | Subject-controlled source | Primary source | Minter Framework, Collateral, Mint, Burn, Issuance and Collateral | Archive index or wildcard | High |
| The first M mint Published 2024-07-28 | M0 | Official statement or announcement Canonical: Official Blog | Subject-controlled source | Primary source | Launch Date, First Mint, MXON, Launch | Archive index or wildcard | High |
| Wrapped M token Published Not yet recorded | M0 | Official documentation or product page Canonical: Official Documentation | Subject-controlled source | Primary source | Wrapped M, Non Rebasing Representation, Related Representation | Archive index or wildcard | High |
Known unknowns
Known unknowns and coverage
Missing or disputed facts remain visible instead of being converted into certainty.| Topic | What remains unclear | Value state | Priority | Last checked |
|---|---|---|---|---|
| Legal and Collateral Entity Map | The reviewed protocol material establishes the Minter and validator framework but does not normalize every legal entity, collateral SPV, reserve holder, and service provider involved across Minters. | Unknown after review | High | 2026-06-21 |
| Canonical Deployment and Extension Map | The complete current map of canonical M contracts, wrapped M, cross-chain representations, and M0 Extensions is not normalized. | Unknown after review | Medium | 2026-06-21 |
| Holder Redemption Boundary | Minter mint and burn mechanics are documented, but a universal holder right to redeem M directly into a specified collateral pool is not established. | Unknown after review | High | 2026-06-21 |
| Reserve Reporting Normalization | Per-Minter collateral schedules, validator reports, and reserve disclosures are not yet normalized into one comparable current reserve view. | Unknown after review | Medium | 2026-06-21 |
Legal and Collateral Entity Map
The reviewed protocol material establishes the Minter and validator framework but does not normalize every legal entity, collateral SPV, reserve holder, and service provider involved across Minters.
- Value state
- Unknown after review
- Priority
- High
- Last checked
- 2026-06-21
Canonical Deployment and Extension Map
The complete current map of canonical M contracts, wrapped M, cross-chain representations, and M0 Extensions is not normalized.
- Value state
- Unknown after review
- Priority
- Medium
- Last checked
- 2026-06-21
Holder Redemption Boundary
Minter mint and burn mechanics are documented, but a universal holder right to redeem M directly into a specified collateral pool is not established.
- Value state
- Unknown after review
- Priority
- High
- Last checked
- 2026-06-21
Reserve Reporting Normalization
Per-Minter collateral schedules, validator reports, and reserve disclosures are not yet normalized into one comparable current reserve view.
- Value state
- Unknown after review
- Priority
- Medium
- Last checked
- 2026-06-21
Lifecycle
History
Current classification remains separate from dated changes and incidents.Model and lifecycle changes
No separate model-change event is currently recorded.
| Date | Event | Category | Subtype | Status effect | Recovery |
|---|---|---|---|---|---|
| 2024-07-28 | The first live M mint occurs | Launch and introduction | Launch | Remained active | Not applicable |
Related records and corrections
Corrections and further reading
Open connected records, methodology, machine-readable data, or report a correction.- All stablecoinsCompare this record with the rest of the archive.
- M0 ProtocolDecentralized / multi-entity
- Event registry1 connected event recorded.
- MethodologyRead classification, evidence, and value-state rules.
- CorrectionsReport a source, relationship, or record problem.
- Data manifestInspect the machine-readable public layer.