Mantra

Mantra is a Validator-Secured Layer 1 for Tokenized Assets

Mantra is a blockchain for recording ownership claims as tokens and running applications on its own network, an EVM-compatible Layer 1 for real-world assets. Built with Cosmos SDK, it uses delegated proof of stake: validators finalize transactions while MANTRA holders delegate coins to strengthen voting power. The chain pairs Solidity support with native staking, governance and Inter-Blockchain Communication, making it most relevant to issuers and users who need programmable assets plus controlled application access.

In this guide
In short: It is an EVM-compatible Layer 1 that tokenizes real-world assets, with delegated proof-of-stake allowing MANTRA holders to help secure its network.

Mantra Chain and Ethereum for tokenized assets

The Mantra network prioritizes asset issuance and permissioned application controls, while Ethereum provides a broad, general-purpose settlement ecosystem. Both environments execute Solidity contracts and support the ERC-20 token standard. This is revisited in practice.

Ethereum gives issuers widely integrated custody, oracle and decentralized finance infrastructure. MANTRA Chain chooses a sovereign Cosmos SDK architecture with its own validators, governance parameters and native Inter-Blockchain Communication, or IBC. Its EVM allows established tools such as OpenZeppelin, Hardhat and Foundry to follow familiar deployment patterns. That compatibility does not import Ethereum liquidity or applications automatically. It reduces development changes while placing execution, gas and validator security on MANTRA Chain.


Transaction fees and the MANTRA gas unit

MANTRA Chain charges transaction fees in its native MANTRA coin, using gas to price computation and storage.

The native denomination has 18 decimal places, and 1 MANTRA equals 10^18 amantra. The minimum gas price is 40 000 000 000 amantra per gas unit, equivalent to 0.00000004 MANTRA before multiplication by gas use. A transaction fee therefore equals the gas consumed multiplied by the selected gas price. Contract complexity sets consumption, while wallet settings and network demand influence the offered price. Block production targets about 3 seconds, although application indexing and cross-chain relaying introduce separate delays.


Validator staking and block security

Validator staking on MANTRA Chain converts delegated coin balances into voting power that secures block production.

Delegation and voting power

Validators propose and confirm blocks through CometBFT consensus. The staking module ranks candidates by bonded MANTRA, including coins that holders delegate to them. Delegators retain an on-chain claim on their coins while assigning consensus weight. A larger delegation increases that validator's influence within the active set, so distributing stake across capable operators supports a less concentrated security model.

Rewards and validator commission

Block provisions and transaction fees fund staking rewards through the Cosmos SDK distribution module. Proposal 18 implemented a fixed 8% inflation rate on 27 August 2025, with 60% allocated to staking rewards and 40% assigned to community rewards. Those percentages do not equal a delegator's yield. Total bonded stake, validator commission, validator performance and claim timing determine the amount credited to each position.

Unbonding and validator exposure

The staking lock duration is 691 200 seconds, equal to eight days. An undelegating balance stops earning rewards and remains unavailable for transfers until that period ends. Delegated balances also share protocol penalties applied to their validator for recognized consensus failures. Redelegation moves bonded stake to another validator without first returning it to a liquid wallet balance.

Asset issuance through Solidity and TokenFactory

Asset issuance on MANTRA Chain follows either standard Solidity deployment or the Cosmos-native TokenFactory path for integrated tokens.

Solidity and ERC-20 contracts

An external developer can deploy an ERC-20 contract through the EVM using OpenZeppelin libraries, Hardhat, Foundry or Remix. The contract defines supply, minting authority and transfer behavior. Permission checks can restrict transfers to approved addresses when an asset requires eligibility controls. The EVM mainnet uses chain ID 5888, so existing Ethereum tooling needs a MANTRA network configuration rather than a new programming language.

TokenFactory and native module access

TokenFactory creates a Cosmos-native denomination and supplies a deterministic ERC-20 precompile for EVM use. This route connects the token directly with the Bank module, IBC and MANTRA-specific controls without requiring a separate wrapped representation. EVM precompiles also expose staking, distribution, governance and bank functions to Solidity contracts. Issuers therefore choose between an independent smart contract and deeper native-module integration.

Permissionless settlement and permissioned applications

That thread continues in Mantra requirements step by step. Permissionless settlement on MANTRA Chain coexists with applications that restrict asset access through identity and transfer rules. Anyone can inspect the base ledger and submit valid public-chain transactions, while an issuer can require Know Your Customer or Know Your Business checks inside its application. Token code records balances and enforces programmed transfers. The issuer's documents, custody arrangements and redemption process establish what each token represents beyond the ledger.

How do you start using MANTRA Chain?

Starting on MANTRA Chain requires a compatible wallet, native MANTRA for fees and the correct network context.

Wallet and network checklist

  • Use Keplr for native staking, governance or IBC activity.
  • Use MetaMask when an application presents an EVM contract flow.
  • Match mainnet ID mantra-1 for Cosmos or 5888 for EVM.
  • Keep native MANTRA outside delegation to cover transaction gas.
  • Save the transaction hash and inspect its status in Blockscout.

First transaction and confirmation

On a first pass, MANTRA Zone provides the user-facing staking workflow, including validator selection, delegation and reward claims. MetaMask handles EVM transactions, while Keplr exposes Cosmos-native messages. DuKong testnet uses EVM chain ID 5887 for testing application behavior without mainnet assets. Before signing, match the displayed chain, address type, amount and validator or contract. A confirmed hash proves inclusion, while the resulting wallet balance or staking position confirms the intended state change.

The MANTRA denomination and on-chain governance

The MANTRA coin combines gas payment, staking and governance roles under one 18-decimal native denomination on the chain. Wallet interfaces display MANTRA while low-level messages calculate amounts in amantra.

At block 13000000, 1 OM became 4 MANTRA and the maximum hard cap became 10 billion MANTRA. The non-dilutive split changed unit denomination rather than each holder's proportional ownership.

On-chain governance gives voters 4 ballot choices: Yes, No, NoWithVeto and Abstain. A text proposal requires a minimum deposit of 355 552 MANTRA before it proceeds through the governance process. Bonded voting power determines each participating account's influence, connecting the staking distribution directly with protocol decisions.

This shared coin design links network use with security demand. Transaction senders need MANTRA for gas, delegators assign it to validators and governance participants use staked weight to vote. A token holder should therefore distinguish liquid gas reserves, bonded positions and claimable rewards when reading a wallet balance.

Trade-offs for holders and asset issuers

Crucially, Mantra exposes holders and issuers to validator, liquidity, application and legal-enforcement constraints that operate through different mechanisms.

Delegation exchanges immediate liquidity for consensus participation during the eight-day unbonding period. Validator commission reduces rewards, and protocol penalties pass through to associated delegations. Concentrated voting power gives a smaller group of validators greater influence over block production and governance. The MANTRA market price moves independently from staking accrual, so a positive coin-denominated reward does not establish a positive result in another currency. Keeping every coin bonded also leaves no liquid balance for gas.

Tokenized assets introduce a separate layer of constraints. A permissioned contract rejects transfers that fail its eligibility rules, even when the base chain remains open. Redemption also depends on the issuer's process and the off-chain asset arrangement. IBC, EVM contracts and external bridges add distinct trust and execution paths, so an asset's route matters alongside its ticker.


Cartoon train beneath text about staying on track every day

Ethereum, Polygon PoS, Avalanche and Provenance as alternatives

Ethereum, Polygon PoS, Avalanche and Provenance Blockchain address tokenized assets with different settlement and interoperability priorities.

Ethereum supplies the native environment for ERC-20 contracts and extensive application composability. Polygon PoS offers EVM execution through its own validator set and periodically submits checkpoints to Ethereum. Avalanche combines an EVM-compatible C-Chain with customizable Avalanche Layer 1 networks. Provenance Blockchain uses a Cosmos-based architecture focused on financial assets. Each alternative separates execution, validator security and cross-chain movement differently.

On the operational side, MANTRA Chain has the clearest fit when an issuer wants EVM tooling, Cosmos-native modules and permissioned application controls within one Layer 1. Ethereum emphasizes established composability, Polygon PoS emphasizes EVM execution connected to Ethereum and Avalanche emphasizes customizable networks. Provenance presents the closest Cosmos-oriented comparison for financial asset workflows.

From OM to the MANTRA mainnet

During normal operation, MANTRA evolved from a 2020 Ethereum token project into a sovereign chain whose native coin now carries network security. The original OM token generation event occurred in August 2020 with a hard cap of 888 888 888 OM.

Development of the Layer 1 began in September 2022. A February 2024 unification proposal made OM the intended native staking coin, receiving support from 82.17% of participating ERC-20 OM holders and 49.17% of mainnet validators. MANTRA Chain launched on 10 October 2024 with 1 777 777 776 OM at genesis. Half mirrored the legacy Ethereum supply, while the other 888 888 888 OM covered ecosystem, contributor, investor and incentive allocations.

The Ethereum OM migration window ended on 15 January 2026, and the chain later adopted the MANTRA ticker through the 1:4 split. Older material therefore uses OM for the asset that now appears as MANTRA on mainnet. The network remains live as a Cosmos SDK chain with an EVM execution environment.

A fit decision for tokenized-asset users

For a regular user, Mantra fits users who value Cosmos interoperability, EVM tooling and application-level controls around tokenized real-world assets.

A prospective delegator should compare validator commission, operational performance and stake concentration before bonding coins. An issuer needs a firmer design exercise: define the represented right, eligible holders, transfer rules and redemption process before selecting Solidity or TokenFactory. Users seeking only broad EVM application access have stronger alternatives on Ethereum or Polygon PoS. Those prioritizing a vertically aligned RWA environment can examine MANTRA Finance, mantraUSD and its M^0-backed reserve structure as concrete ecosystem implementations.

Frequently asked questions

Can MetaMask hold native MANTRA without wrapping it?

MetaMask can hold native MANTRA in the chain's EVM account space without wrapping it. Add the network with chain ID 5888 and use MANTRA as the gas currency. wMANTRA is an ERC-20 representation for contract workflows, while native MANTRA pays transaction fees and remains the staking coin.

Does MANTRA Zone take custody of delegated MANTRA?

MANTRA Zone does not take custody of delegated MANTRA. The portal prepares an on-chain staking transaction, and your wallet signs it. Cosmos SDK staking then records the delegation against your address and chosen validator. Rewards accrue separately, while the underlying coins remain subject to the protocol's eight-day unbonding rule.

What address format should I use for a MANTRA transfer?

Use a mantra-prefixed Bech32 address for Cosmos-native transfers and a 0x address for EVM transactions. Some wallets derive both forms from the same key, but the receiving application determines which form it accepts. Copy the address from that application instead of converting it by sight.

How long does a normal MANTRA Chain transfer take?

The chain targets a block about every three seconds, so a basic native transfer normally appears after the next committed block. Wallet refresh time, application indexing and IBC relaying add separate delays. CometBFT gives each committed block finality, while cross-chain arrival also requires the destination chain to process its packet.

Are MANTRA staking rewards added to the delegated balance automatically?

MANTRA staking rewards accrue as a claimable balance rather than automatically increasing every delegation. MANTRA Zone offers a Claim action and a Claim and Stake path, with each choice requiring a signed transaction and gas. Compounding occurs only after rewards move into a new delegation, and validator commission reduces the credited amount.