Mantle is a DAO-funded Ethereum L2 where MNT behaves less like “equity” and more like a treasury-managed budget token

Mantle Network is an Ethereum Layer 2 that went live on July 17, 2023, built to be EVM-compatible while leaning into a modular architecture for execution and data availability choices over time, as outlined in the mainnet launch notes.

The $MNT token is positioned as both (1) the Mantle Governance vote-weight token and (2) the network’s gas token. Mantle’s governance documentation describes this dual role (gas fees on Mantle Network plus governance voting weight) in its dual-role tokenomics.

That design choice matters. It means “value accrual” is not only about fee generation. It is also about treasury policy: how the DAO releases, sells, incentives, or potentially burns the large treasury-held portion of supply. Mantle makes this explicit by treating Treasury-held MNT as “not in circulation” and routing distribution through governance and budgets. For a modular data-availability comparison point, see our Celestia tokenomics review.

Supply and allocations: a one-time optics burn, plus an always-on governance overhang

MNT’s origin story is not a typical multi-bucket launch allocation. It is a governance-approved migration from BitDAO’s BIT into Mantle’s unified token, with a 1 BIT : 1 MNT conversion set in MIP-22 and repeated in Mantle’s migration guide.

The key supply-shaping decision came right before launch. In MIP-23, Mantle governance approved not converting 3 billion BIT held by the treasury and instead sending those non-converted BIT tokens to a nominated burn address, specifically to reduce the fully diluted supply at MNT launch via the MIP-23 supply vote.

Post-optimization, Mantle’s tokenomics documentation points to an on-chain total supply of 6,219,316,768 MNT, with an initial split between circulating supply and the Mantle Treasury based on a July 7, 2023 snapshot.

For a “current” market view (not a protocol parameter), CoinGecko currently lists MNT with 6,219,316,794 as total/max supply and an estimated circulating supply around 3,277,944,055. Treat this as an aggregator read, not the governance source of truth.

Emissions: no scheduled inflation, but a governance-controlled mint hook exists

Mantle deliberately added “future flexibility” into the token contract surface area. MIP-22 states that MNT “shall incorporate” upgradability and a mint function analogous to ARB and OP in the upgradability and mint terms.

More importantly for modeling, MIP-22’s supporting text recommends that MNT permits minting once per year with a default setting of 0%, and that minting would be governed.

So the “emissions schedule” is effectively: none, unless governance turns it on. That is better than a constant drip if you want predictability. It is worse than a hard cap if your valuation depends on credible commitment. The risk is not mechanical inflation today. The risk is optionality sitting in governance hands. If you want a definitions baseline for these levers, start with our tokenomics FAQ.

Even audits and third-party reviews of the migration plan highlight that the token owner is responsible for minting, with limits around frequency and a modifiable cap, and recommend multisig protections for privileged control.

Utility and fiscal flows: gas demand is real, but “burn narratives” are mostly discretionary

Mantle’s tokenomics docs state MNT is used for gas fees on Mantle Network, and Mantle’s bridge UX reminds users they need MNT on L2 to transact.

On explorers, fees are visibly denominated in MNT units, with gas fee units commonly presented in gwei-sized MNT fractions and transaction fee fields displayed in MNT.

The other major “utility” is governance. Mantle’s governance parameters define 1 delegated MNT = 1 vote weight under the Snapshot strategy.

And then there is what I would call Mantle’s fiscal policy layer: Rewards Station and broader incentive programs. Mantle’s tokenomics docs call MNT “a principal asset within Mantle Rewards Station,” and the Mantle Treasury site frames treasury assets as being distributed to MNT holders via Rewards Station, which is a reminder that a chunk of “holder yield” here is not endogenous fee yield. It is treasury-directed distribution of third-party rewards and campaigns.

From a burn-skeptic lens, this is the tension: incentives can bootstrap activity, but they do not automatically create durable fee revenue. If the chain’s economic surplus is thin, tokenholder returns can drift into a subsidy loop funded by the treasury’s balance sheet.

Fees, vaults, and why “burn” is not the default setting on OP-style L2 economics

Mantle’s on-chain fee plumbing looks consistent with OP Stack conventions. MantleScan labels 0x4200000000000000000000000000000000000011 as the chain’s Sequencer Vault address.

That matters for tokenomics because on OP-style systems, fees are typically collected into distinct vaults and later withdrawn to designated recipients rather than automatically burned like Ethereum L1 EIP-1559. For an OP Stack baseline, our Optimism tokenomics review covers the canonical fee-vault model.

On MantleScan, the Sequencer Vault history includes admin actions labeled “Set Burner” on July 4, 2023. This is the kind of detail that fuels burn narratives. A “burner” address exists at the vault layer. That does not mean fees are being burned in steady state. It means the system can be configured to route funds to a burn sink.

More concretely, MantleScan also shows “Withdraw” events and internal transfers out of the Sequencer Vault to 0x4200000000000000000000000000000000000010 (a neighboring predeploy address) in multiple instances, including January 1, 2026.

So if you are looking for an automatic, credibly-neutral, EIP-1559-style burn that scales with activity, Mantle’s observable structure pushes you the other way. It looks like accounting vaults and discretionary routing, not “always burn.” That is normal for OP-family chains. It is also why burn-based valuation stories tend to be fragile unless you can point to a policy-enforced, measurable sink.

MIP-22 even makes this philosophy explicit. It argues that adding a mint function can make the community more comfortable burning treasury MNT because future needs could be met by governance-approved inflation later. As a burn skeptic, I read that as: burns are treated as a treasury-management tool, not as a protocol-level monetary policy backed by recurring cash flows.

Governance and parameter control: Snapshot-first, off-chain execution, and a big surface area for policy drift

Mantle Governance is described as primarily off-chain: forum discussions can progress to formal proposals (MIPs) voted on Snapshot, and then core contributors support implementation. Mantle notes that results do not automatically trigger code updates or treasury actions.

Key live governance parameters (these are not vibes, they are published knobs):

Forum discussion period: minimum 7 days.
Vote duration: minimum 7 days.
Proposal threshold: 200,000 MNT.
Quorum (vote threshold): 100,000,000 MNT.
Delegation required: token holders must delegate before voting.

On treasury, Mantle’s docs say all treasury actions are authorized by governance proposals, and the “best estimate” of assets is maintained via a dedicated Treasury Monitor that is manually updated for major changes and positions.

That combination is powerful and risky. Powerful because the DAO has a large balance sheet and can fund growth. Risky because tokenholder value becomes a function of (1) governance participation and (2) execution integrity, not only protocol economics. If the governance process becomes apathetic or captured, “tokenomics” becomes “budget politics.” If you want a framework for mapping these moving parts, use this design components checklist.

Risk analysis: the dominant issue is not burn mechanics, it is policy credibility around a 49% treasury

Mantle has a clean headline: roughly half circulating, roughly half treasury at inception, and no vesting in the initial distribution snapshot. The hard part is not describing that. The hard part is modeling what the treasury does over years, especially in a system where governance is off-chain and execution is operational.

Dominant risk: Treasury overhang plus off-chain execution creates a long-lived, hard-to-hedge policy premium.

The treasury is not a passive “foundation allocation.” It is a live pool that funds core budgets, incentives, liquidity support, and product strategy. Mantle’s tokenomics page is explicit that distribution from the Mantle Treasury requires authorization, “most importantly via Budget Proposals.” The treasury docs also note that not all positions are easily machine-verifiable on-chain, and that centralized services may be used for custody and trading, with public exposure not recommended for risk reasons.

Mechanically, this means:

1) Token supply pressure is governed less by “emissions” and more by budget cadence.
2) Any “deflation” from burns is only value-accretive if it is paired with sustainable surplus or at least credible restraint on future net issuance.
3) Governance being off-chain means there is an implementation layer where tokenholders are trusting processes, multisigs, committees, and service providers.

MIP-22’s inclusion of both upgradability and mint hooks reinforces this. Mantle intentionally kept the option to change token functionality and authorize future inflation. That flexibility can be rational. It also increases the discount rate investors apply to long-term “scarcity” claims.

The one-time BIT burn in MIP-23 made FDV optics cleaner going into launch. But it did not create recurring economic value. Sustainable value comes from net fee generation and credible retention of that value for tokenholders, not from a one-off supply presentation fix.

Top 3 risks

  1. Treasury release risk, Trigger: large budget proposals, incentive programs, or liquidity operations that move meaningful MNT from treasury into the market. Mechanism: treasury-held supply becomes circulating supply, increasing sellable float without a matching increase in fee-driven demand. Who bears it: spot holders and LPs who absorb incremental supply. Measurable indicators: Treasury Monitor changes, growth in circulating supply vs treasury holdings, and repeated large budget authorizations.

  2. Governance execution and trust surface risk, Trigger: a passed Snapshot vote requires upgrades, treasury moves, or parameter updates that are executed off-chain by core contributors or operational multisigs. Mechanism: mismatch between vote outcomes and implementation timing or fidelity, plus general key-management and committee risk. Who bears it: tokenholders relying on governance, and users relying on protocol continuity. Measurable indicators: delays between vote passage and execution, concentration of execution keys, and audit findings tied to privileged operations.

  3. Fee value-capture fragility, Trigger: low-fee policy persists while L1 settlement and operations costs rise, or fee routing primarily benefits operators rather than MNT holders. Mechanism: even if MNT is the gas token, very low fees can mean limited aggregate fee capture, and vault-based routing does not imply burning. Who bears it: MNT holders expecting fee-linked scarcity, and potentially the treasury if it subsidizes operations. Measurable indicators: Sequencer Vault withdrawals and routing patterns, and the gap between on-chain activity metrics and retained value in fee vaults.

If you’re evaluating MNT for allocation or building governance-sensitive models, the work is mostly about scenario design around treasury policy and execution guarantees. This is where disciplined token economy design matters more than headline “deflation.” If you need a second set of eyes, a short consulting review via our tokenomics design services can focus on net issuance conditions, budget cadence, and fee-retention pathways rather than burn marketing.



This article is part of our Tokenomics Deep Dive series.