mantra

Prop 29: v7.0.0 MAINNET MANTRA Chain Upgrade

MANTRA Chain v7.0.0 — $OM to $MANTRA Redenomination

Summary

This proposal triggers the MANTRA Chain v7.0.0 software upgrade at Block 13,000,000 (target: ~3 March 2026). The upgrade implements the previously approved governance proposal (Proposal #25) to redenominate the native token from $OM (uom) to $MANTRA (aMANTRA) and execute a non-dilutive 1:4 token split — increasing the hard-capped max supply from 2.5B to 10B tokens while preserving all economic value.

Release Details: https://github.com/MANTRA-Chain/mantrachain/releases/tag/v7.0.0


Motivation

With the ERC-20 OM deprecation complete as of January 15, 2026, this upgrade is the final step in MANTRA's brand harmonization. Aligning the chain's native ticker with the project name ($MANTRA) unifies the ecosystem — MANTRA Chain, MANTRA Finance, MANTRA Zone, and mantraUSD — under a single, globally recognizable identity. The 1:4 token split mirrors conventions used by comparable projects ($SUI, $ONDO, $ARB) and codifies the 10B max supply at the protocol layer.


What Changes

Parameter Before ($OM) After ($MANTRA)
Ticker OM MANTRA
Base denom uom amantra
Token decimals 6 (micro) 18 (atto)
Max supply 2,500,000,000 OM 10,000,000,000 MANTRA
Conversion ratio 1 OM = 4 MANTRA (1:4 × 10¹²)
BondDenom / Gas denom uom amantra
EVM denom (evm_denom) uom amantra

Unchanged: Chain ID (mantra-1 / EIP-155 5888), FDV, market cap, staking weights, governance weights, derivation path (44/60/0/0).


Technical Module Changes

All balances, parameters, and rewards are migrated automatically at the 1:4 × 10¹² ratio. No manual action is required from token holders, stakers, or delegators.

  • Bank: All uom balances converted to amantra.
  • PreciseBank: Fractional balances distributed to holder accounts (scaled 4×).
  • Staking: BondDenom updated; validator delegations, delegator shares, unbonding delegations, and initial balances scaled.
  • Distribution: Module account balances and outstanding validator rewards scaled.
  • Governance: MinDeposit and ExpeditedMinDeposit scaled.
  • Auth: All vesting account types (VestingPeriods, OriginalVesting, DelegatedFree, DelegatedVesting) migrated at defined ratio.
  • Authz / Feegrant: Authorization spend limits and fee allowances migrated at defined ratio.
  • EVM: evm_denom updated from uom to amantra.
  • TokenFactory: denom_creation_fee updated from uom to amantra.
  • Crisis: Constant fee scaled.
  • Mint: MintDenom updated to aMANTRA.
  • IBC Escrow (exception): IBC escrow accounts retain uom until funds return from destination chains (e.g., Osmosis), at which point they migrate to amantra. Post-upgrade, escrow accounts are the only entities that may hold uom.

Upgrade Mechanics

  • Target block: 13,000,000 (~3 March 2026)
  • Vanity block explorer: https://www.mintscan.io/mantra/block/13000000
  • At block height, the chain halts, v7 applies, and the redenomination executes atomically as a state migration.
  • Upgrade handler: https://github.com/MANTRA-Chain/mantrachain/blob/v7.0.0/app/upgrades/v7/upgrades.go

Governance Context

The token redenomination was approved by the community in Proposal #25 with 90.48% YES, 0.03% NO, and 9.49% ABSTAIN. This software upgrade proposal authorizes the technical execution of that mandate on mainnet (mantra-1).

Field
Data
info
https://raw.githubusercontent.com/MANTRA-Chain/net/refs/heads/main/mantra-1/upgrades/v7.0.0/cosmovisor.json
name
v7.0.0
time
0001-01-01T00:00:00Z
height
13000000
upgraded_client_state