Layer 1 blockchain
MANTRA Chain ticker MANTRA
Summary
Cosmos SDK chain (chain ID mantra-1, EVM chain ID 5888) using CometBFT consensus, with an embedded EVM and CosmWasm. MANTRA holders delegate to validators; the active set is capped at 38 and 38 were bonded on 2026-09-27. A block commits once validators holding more than 2/3 of voting power precommit it, assuming less than 1/3 is byzantine. Five validators named Association 1 to 5 (website mantrachain.io) held about 49% of bonded stake, and the three largest about 35%, enough on their own to stop new blocks. Unbonding takes 8 days and double-signing costs 5% of stake. Mainnet ran v8.7.0-pre.1, a security release shipped as signed binaries with source withheld until a disclosure window closes. 112131422232439
Design
- System
- Layer 1 blockchainIts own proof-of-stake chain (chain ID mantra-1) secured by its own bonded validators. It is not a rollup and does not borrow Cosmos Hub security; it is itself a provider of shared security to one other chain, NVNM Chain. The native coin was renamed from OM to MANTRA on 2 March 2026 (1 OM became 4 MANTRA), so the display name uses the new ticker.
- Settlement family
- Cosmos SDK
- Scarce resource
- Stake (proof of stake)
- State model
- Accounts
- Finality
- Economic finality
- Who makes blocks
- Validators selected round-robin in proportion to voting power, per the CometBFT consensus specification. Entry to the active set is by stake ranking under a cap of 38 set by governance.
- Fork choice
- No fork choice in the Nakamoto sense: a height is decided by +2/3 precommits. Conflicting commits would need at least 1/3 of voting power to double-sign, which is attributable and slashable. In August 2026 validators stopped the chain for about 30 hours after an exploit and restarted on a patched release without rolling back any blocks.
Qualifications
- Ibc · Applies. IBC links MANTRA to Osmosis, Noble, Injective, Cosmos Hub, Stargaze, Elys, Axelar and Neutron through on-chain light clients (open transfer channels on 2026-09-27). It is messaging between separately secured chains, not a rollup, and is recorded under bridge support.
- Settlement family · Partial. MANTRA is built with the Cosmos SDK, CometBFT and IBC, so it is grouped with Cosmos chains, but it also runs an embedded EVM (chain ID 5888) in the same chain, and MANTRA's docs advise the key type its EVM uses, which gives one account both a mantra1 and a 0x address, so EVM users see 0x addresses, EVM wallets and EVM contracts. It does not settle to Ethereum.
- Shared security · Applies. As a provider only: MANTRA runs its own Interchain Security module and lends validators to NVNM Chain. MANTRA itself is secured by its own bonded validators and does not use Cosmos Hub security, so Hub security properties do not carry over.
- Validator independence · Partial. On 2026-09-27 the five Association-named validators held about 49% of bonded stake and the three largest about 35%, above the one-third that can halt blocks; the eight largest validators held about 71%, above the two-thirds that can commit blocks. Validators named Inveniam, the announced acquirer of MANTRA, held another 6.5%. Ownership is inferred from names and websites.
- Source availability · Partial. Mandatory upgrades v8.3.0, v8.5.0-pre.1, v8.6.0-pre.1 and v8.7.0-pre.1 were distributed as signed binaries with source withheld until a disclosure window closed. Source for v8.3.0 and v8.5.0 was later tagged on GitHub; on 2026-09-27 there was no public source tag for v8.6 or v8.7, including v8.7.0-pre.1, the version running on mainnet.
- Admin controls · Applies. Governance can blacklist accounts so their transactions are rejected and can switch off message types with a circuit breaker. On 2026-09-27 the switched-off list included CosmWasm code upload and instantiation, vesting-account creation and group creation. The v8.4.0 emergency release also blocked the August 2026 attacker's account.
- Throughput · Unknown. Only a vendor-page theoretical figure was found. MANTRA's docs give about 3-second blocks, and a 10,936-block sample on 2026-09-27 averaged about 3.35 seconds; that is block spacing, not transaction capacity.
Tradeoffs
- Emphasizes
- Security and Scalability Contested
- Gives up
- Decentralization of control: 38 validator slots with about half of voting power on five validators named for the MANTRA Chain Association, governance that can blacklist accounts and switch off message types, and mandatory security releases shipped as binaries whose source is withheld for a period, so operators cannot audit what they run. Liveness also depends on more than 2/3 of voting power staying online.The security reading is contested. Security here means single-round BFT finality under a one-third fault assumption, with 5% of stake at risk for double-signing. It did not prevent the August 2026 exploit of an inherited EVM accounting bug, which moved about 721 million MANTRA from accounts that never signed, and recovery depended on validators halting the chain for about 30 hours and restarting on a patched release. Scalability means roughly 3-second blocks on modest node hardware, not a measured capacity. Linking validators to the Association rests on their names and websites.
- Full node at home
- Practical at home 41122MANTRA's node guide lists a minimum of 4 CPU cores, 16 GB RAM, a 500 GB SSD with 5,000 or more IOPS and 25 Mbps; validators are advised to use 32 GB RAM, 2 TB NVMe and 100 Mbps on bare metal. Since July 2026 several mandatory upgrades shipped as signed binaries only, with source published later, so home operators must trust prebuilt binaries during those windows.
- Throughput claims
- Theoretical peak: 10,000 tx/s 33Theoretical peak; not comparable across chains or with observed load.The figure appears in the chain description on Ledger's MANTRA coin page, an undated page that still calls the coin OM, not in MANTRA's current documentation reviewed here. No method, test window, transaction type, hardware or bandwidth is stated. It ignores block propagation, state growth and validator count, and the page's wording predates the 2026 redenomination. Not comparable with any other chain's figure unless the same class of claim is shown for each.
Scaling layers
- NVNM Chain (shared-security consumer chain) · Sidechain, beta 18192526
A separate CometBFT chain (nvnm-1) that MANTRA and NVNM call a Layer 2. It borrows MANTRA validators through MANTRA's own Interchain Security: on 2026-09-27 seven had opted in (four named Association, three named Inveniam). Double-signing there can cost 5% of MANTRA stake; downtime is not slashed. It posts no data or proofs to MANTRA, so it is not a rollup. Its own site describes an invitation-only closed beta.
Capabilities
| Capability | How it is provided | Notes and sources |
|---|---|---|
| Account abstraction | Structured assessment pending | Not yet assessed for any chain. |
| Atomic swaps | Unknown | No hash-locked or equivalent cross-party swap mechanism was reviewed. IBC and Hyperlane transfers are not atomic swaps, and AMM swaps settle within one chain. |
| Authenticated data publication | Unknown | Not yet assessed under the current definitions; no feature on MANTRA itself was found through which a publisher makes data available against a chain-recorded commitment. NVNM Chain, a separate chain, anchors hashes and links to permissioned data, which is NVNM Chain's feature, and SEDA supplies price feeds as an oracle. Absence was not exhaustively verified, so the rule that absence needs a source makes this unknown rather than not present. 825 |
| Light clients | Built into the protocolLimited scope | CometBFT consensus produces the validator-signed commits that IBC light clients check. IBC relies on on-chain light clients that verify counterparty consensus; ten IBC channels were open on 2026-09-27, including the provider channel to NVNM Chain. Limited: this light verification serves IBC, where counterparty chains' on-chain light clients check MANTRA's commits; no light-client wallet or other user-facing light client for MANTRA itself was reviewed. 2040 |
| Native staking or delegation | Structured assessment pending | Not yet assessed for any chain. |
| On-chain governance | Structured assessment pending | Not yet assessed for any chain. |
| Parallel execution | Structured assessment pending | Not yet assessed for any chain. |
| Payment or state channels | Unknown | No payment or state channel layer anchored to MANTRA was reviewed. IBC channels are messaging paths, not payment channels. |
| Programmable spending | Native (protocol or core-team software) Earlier definition | Two contract environments share one chain: an EVM whose live settings let anyone create and call contracts, and CosmWasm, where code upload is limited to four governance-approved addresses and, on 2026-09-27, new uploads and instantiations were switched off entirely. Existing CosmWasm contracts keep running. 8151617 |
| Protocol-verified messaging | Structured assessment pending | Not yet assessed for any chain. |
| Reversible transfers or recovery | Unknown | Not yet assessed under the current definitions; no feature for cancelling, delaying or reclaiming a payment or for recovering an account was found, and recovery features of contract wallets on the EVM were not reviewed. Governance can blacklist an account so its transactions are rejected, and the v8.4.0 release blocked the attacker's account; these act on holders and freeze funds rather than return them, so they do not count. 9102324 |
| Rollups | Unknown | The review did not verify absence, so the rule that absence needs a source makes this unknown rather than not present. Earlier finding: no rollup settling to MANTRA was found. NVNM Chain is marketed as a MANTRA Layer 2 but runs its own consensus under shared security and posts no proofs or data to MANTRA, so it is listed as a separate chain. 1825 |
| Shielded transfers | Structured assessment pending | Not yet assessed for any chain. |
| Signed partial offers | Unknown | Not yet assessed under this row's current definition. |
Reading these values
- How this feature is provided
- Built into the protocol, core-team software or independent software says where a feature lives and who can change it. These are implementation layers, not quality: core-team software is not closer to the protocol than independent software.
- Structured assessment pending
- The shared review has not assessed this feature for any chain yet (Account abstraction, Native staking or delegation, On-chain governance, Parallel execution, Protocol-verified messaging and Shielded transfers). That does not mean it is absent, and a chain’s profile may already describe it.
- Unknown
- The review has not established this for this chain under the current definition; the note beside it says why. Unknown is not absent and not a low score. A feature reads “Not present” only when a source shows it is absent.
- Earlier definition
- Payment or state channels, Programmable spending and Rollups keep the earlier definition until the next fact-check. There, “Native” does not separate the protocol from core-team software, “Ecosystem software” does not say who publishes it, and “Partial” does not say which layer.
- Reading across rows
- The list of capabilities is incomplete. Do not read these rows as a chain leading or lagging overall.
Ecosystem & custody
| Product type | Status | Notes and sources |
|---|---|---|
| Automated market makers | ThinMANTRA Swap (MANTRA DEX, CosmWasm), QuickSwap (Algebra v4, EVM) | MANTRA's docs list a CosmWasm pool manager based on White Whale v2 and QuickSwap Algebra v4 contracts on the EVM. On 2026-09-27 the CosmWasm pool manager held seven pools; the six paired with USDC each held under 1,000 USDC, and two still held the pre-redenomination OM denomination. QuickSwap liquidity was not measured. 821 |
| Issuer-native stablecoins | First-partymantraUSD (issued by MANTRA through M0) | mantraUSD is MANTRA's own stablecoin, minted on the EVM against M0 Wrapped M that arrives over a Hyperlane route; the whitepaper says reserves are short-term US Treasury bills held through special-purpose vehicles under M0's framework. About 435,000 were outstanding on 2026-09-27. Circle and Tether do not list MANTRA; USDC there is bridged (a Hyperlane token on the EVM or USDC.n from Noble over IBC). 272728293031 |
| Algorithmic stablecoins | Unknown | Algorithmic or hybrid stablecoins on MANTRA were not reviewed. |
| Bridges | Native to the protocolIBC, Hyperlane (lock and mint), Squid (liquidity routing), Lucid, mantraUSD deposit bridge | IBC is built into the chain; MANTRA's bridging page also lists Hyperlane, Squid, Lucid and a USDC-to-mantraUSD deposit bridge from Ethereum, Arbitrum, Base and Polygon. Supported routes change and must be checked in each bridge's interface. Risk: IBC assets depend on the counterparty chain and correct light clients. Hyperlane tokens depend on Hyperlane security modules; its SDK default for messages leaving MANTRA is two of two validators (Abacus Works and Mitosis), and routes may set their own. Liquidity bridges add counterparty risk. The August 2026 halt stopped all transfers for about 30 hours. 6202324293240 |
| Block explorers | Established in the ecosystemMantrascan, Mantrascan Blockscout (EVM), Mintscan, ITRocket, STAVR explorer | MANTRA's network page names mantrascan.io and a Blockscout instance for the EVM; the Cosmos chain registry adds Mintscan and community explorers. Listing is not a quality check; explorer data is provider-indexed. 13 |
| Hardware wallets | Established in the ecosystemLedger, Trezor (through MetaMask or Rabby) | See custody rows: Ledger lists MANTRA with staking in Ledger Wallet (formerly Ledger Live), using an older Cosmos key path that does not reach the EVM side; Trezor lists only MANTRA's EVM network through third-party wallets. 33343538 |
Hardware-wallet custody
| Device maker | Status | What users can and cannot do |
|---|---|---|
| Ledger | Native supportSame as native: Unknown | Can: Add a MANTRA account in Ledger Wallet (formerly Ledger Live), which Ledger's code defines as a Cosmos-family chain using the Cosmos device app and ticker MANTRA with 18 decimals Can: Stake MANTRA from Ledger Wallet, per Ledger's MANTRA wallet and staking pages Cannot: Use the Ledger Wallet MANTRA account directly on MANTRA's EVM: Ledger's code derives it with Cosmos coin type 118, and MANTRA's docs say only the key type its EVM uses maps to an EVM addressLedger's wallet page is undated and still says OM; its staking page names Ledger Wallet. In Ledger's code the MANTRA integration sits behind a feature switch that is off by default and turned on remotely; its production setting, and whether signing still works after MANTRA moved new accounts to EVM-type keys, were not verified. 53334353637 |
| Trezor | Through an intermediaryMetaMask or Rabby (MANTRA EVM network only)Same as native: No | Can: Hold MANTRA on its EVM network with a Trezor Safe 3, 5 or 7 connected to MetaMask or Rabby, per Trezor's MANTRA page Cannot: Manage MANTRA in Trezor Suite Cannot: Use a Cosmos-side MANTRA account through the path Trezor lists, which names only the MANTRA EVM network 38 |
Public data
iKnow Blockchain has no public-data lookups for MANTRA Chain yet. This is a limit of the service, not a statement about the network.
| Lookup | Status | What it covers and its limits |
|---|---|---|
| Address or account | Not available yet | Public-data lookups for this chain are not built yet. |
| Tokens and assets | Not available yet | Public-data lookups for this chain are not built yet. |
| NFTs | Not available yet | Public-data lookups for this chain are not built yet. |
| Transactions | Not available yet | Public-data lookups for this chain are not built yet. |
Sourced developments
Developments: Review overdue Reviewed Sep 27, 2026; next review was due Oct 7, 2026, 12:00 UTC.
Publication date · newest first
-
MANTRA published its post-mortem of the 20 August 2026 exploit and 30-hour halt
MANTRA reported that an integer-underflow bug in the shared cosmos/evm component let an attacker move about 721 million MANTRA from the burn address and an old multisig. Validators halted the chain for 30 hours and 13 minutes and restarted on v8.4.0 without a rollback; about 38 million MANTRA stayed frozen in the attacker's account.
- Implementation:fix shipped in v8.4.0
- Release:released 21 August 2026
- Activation:chain restarted 22 August 2026; the post-mortem set out no fund recovery plan
Sources: MANTRA — 20th August 2026 Full Incident Post Mortem (external site) · CryptoSlate — Cosmos misjudged a critical bug for 4 months before hackers stole nearly $6 million across 6 chains (external site) · MANTRA Chain Status — Security vulnerability in Cosmos-EVM module (incident log) (external site) · The Block — Cosmos Labs says it wrongly cleared the bug behind a $5.7 million six-chain hack (external site) · MANTRA-Chain/mantrachain on GitHub — MANTRA Chain v8.4.0 release notes (external site)
-
NVNM Chain launched as a shared-security consumer of MANTRA
Inveniam Labs announced that NVNM Chain, built with MANTRA and described as a MANTRA Layer 2, had launched in May 2026. On-chain records show it as an Interchain Security consumer chain (nvnm-1) run by seven opted-in MANTRA validators; NVNM's site describes an invitation-only closed beta while its docs call the mainnet live.
- Implementation:consumer chain registered and launched on MANTRA's provider module
- Release:closed beta per NVNM's site
- Activation:seven validators active on 27 September 2026
Sources: Inveniam Labs (GlobeNewswire) — NVNM Chain Announces Upcoming Launch of $NVNM Token and MANTRA Community Early Access Initiative (external site) · Inveniam — Inveniam to Acquire MANTRA (external site) · MANTRA (public API node) — Interchain Security consumer chain 0 (nvnm-1) record (mantra-1 public REST endpoint) (external site) · MANTRA (public API node) — Interchain Security consumer 0 validator set (mantra-1 public REST endpoint) (external site) · NVNM Chain — NVNM Chain (external site) · MANTRA — NVNM Chain Launches as MANTRA L2 to Power Verifiable AI Data (external site)
-
Governance raised MANTRA inflation to 16% and the Association's share of issuance
Proposal 33, which also scheduled the v8.2.0 upgrade, raised the fixed yearly inflation rate from 8% to 16% and the share of new issuance going to the MANTRA Chain Association from 40% to 60%, citing a staked share of about 25% and rising security costs.
- Proposal:passed as proposal 33
- Implementation:mint settings updated
- Release:v8.2.0 released
- Activation:16% shown in live settings on 27 September 2026
Sources: MANTRA (on-chain governance record) — Governance proposal 33: v8.2.0 upgrade, inflation recalibration and emissions update (external site) · Polkachu (governance proposal mirror) — Mantra proposal 33: v8.2.0 mainnet upgrade (external site) · MANTRA (public API node) — Mint parameters (mantra-1 public REST endpoint) (external site) · MANTRA (public API node) — Annual provisions (mantra-1 public REST endpoint) (external site) · MANTRA Chain Docs — Inflation and Vesting Schedule (external site)
-
OM became MANTRA in a 1:4 redenomination at block 13,000,000
The v7.0.0 upgrade carried out the governance-approved change of the native coin from OM to MANTRA. Balances and staking positions were multiplied by four, the base unit moved from uom (6 decimals) to amantra (18 decimals), and the supply cap became 10 billion MANTRA.
- Proposal:approved as proposals 26 and 29
- Implementation:shipped in mantrachain v7.0.0
- Release:Released
- Activation:active since block 13,000,000 on 2 March 2026
Sources: MANTRA Chain Docs — MANTRA Token Background (external site) · MANTRA (on-chain governance record) — Governance proposal 29: v7.0.0 upgrade (OM to MANTRA redenomination) (external site) · Polkachu (governance proposal mirror) — Mantra proposal 29: v7.0.0 mainnet upgrade (external site) · MANTRA (on-chain governance record) — Governance proposal 26: Redenominating OM to MANTRA (external site) · MANTRA — MANTRA Chain Coin Upgrade: Timeline and Key Details (external site)
Topics your AI can explain
Your AI can explain these topics for MANTRA Chain through the connection, with sources.
Known gaps
What this profile's review did not establish:
- MANTRA's inflation page still says 8%; the chain's live settings and the June 2026 governance record show 16%, with a larger share of new issuance going to the MANTRA Chain Association. Where transaction fees end up (burned or paid to stakers) was not verified.
- Which legal entity runs each Association-named validator was not confirmed. An August 2025 governance plan to cut them from five to two had not been carried out: five were still bonded on 2026-09-27.
- Whether the announced Inveniam acquisition of MANTRA has closed was not verified; the announcement gives both 30 June 2026 and the third quarter of 2026 as expected closing times, and press reports in August 2026 still described it as pending.
- Source code for the release running on mainnet (v8.7.0-pre.1) had not been published at review time, so its changes could not be audited.
- QuickSwap liquidity on MANTRA's EVM was not measured, and Lotus DEX, announced in November 2025 as the chain's flagship exchange, returned HTTP 404 at review time.
- mantraUSD reserve reporting on M0's dashboard was not checked; backing is recorded as stated in the whitepaper.
- Hyperlane security settings for each MANTRA token route were not checked; only the SDK default for messages leaving MANTRA was read.
- Whether Ledger Wallet signing still works after MANTRA's move to EVM-type keys, and the production setting of Ledger's MANTRA feature switch (off by default in code), were not verified.
- MANTRA's 28 August 2026 post-mortem referred the stolen funds to exchanges and law enforcement without a recovery plan; no later recovery step, or governance action on about 38 million MANTRA frozen in the attacker's account, was found.
- No throughput figure from MANTRA's own documentation was found; only a theoretical figure on Ledger's page.
- Algorithmic stablecoins, payment or state channels and cross-chain hash-locked swaps were not reviewed.
- About 211,000 OM in the old denomination still existed on chain on 2026-09-27, partly inside DEX pools; how it is treated was not reviewed.
- The public API node keeps only recent history, so older states such as the redenomination block could not be read directly.
- Staking, slashing, circuit-breaker, contract-permission, IBC channel, DEX pool and NVNM validator figures come from the author's reads of MANTRA's public API node on 2026-09-27. The independent check re-confirmed validator stakes, the 38-validator set and the node version from Polkachu's directory, but did not re-read the API node itself.
Sources
Oldest dated source check: Source checked Sep 27, 2026 Next check due Oct 27, 2026.
- MANTRA chain registry record (external site)
- MANTRA chain registry asset list (external site)
- Network Details (external site)
- Node Setup & Deployment (external site)
- Address Conversion (external site)
- Bridging Overview (external site)
- Canonical ERC-20 Contracts (external site)
- Mainnet Contracts (external site)
- x/sanction module README (external site)
- MANTRA Chain v8.4.0 release notes (external site)
- MANTRA Chain v8.3.0 Coordinated Security Upgrade (tag v8.2.0-hotfix.0) (external site)
- Staking parameters (mantra-1 public REST endpoint) (external site)
- Slashing parameters (mantra-1 public REST endpoint) (external site)
- Mantra Chain Validator Directory (38 bonded validators, stakes and node version v8.7.0-pre.1) (external site)
- EVM module parameters (mantra-1 public REST endpoint) (external site)
- CosmWasm code parameters (mantra-1 public REST endpoint) (external site)
- Circuit breaker disabled message list (mantra-1 public REST endpoint) (external site)
- Interchain Security consumer chain 0 (nvnm-1) record (mantra-1 public REST endpoint) (external site)
- Interchain Security consumer 0 validator set (mantra-1 public REST endpoint) (external site)
- IBC channels (mantra-1 public REST endpoint) (external site)
- MANTRA DEX pool manager pools query (mantra-1 public REST endpoint) (external site)
- Mantra proposal 38: v8.7.0 (-pre.1) mainnet upgrade, binary package only (external site)
- 20th August 2026 Full Incident Post Mortem (external site)
- Cosmos misjudged a critical bug for 4 months before hackers stole nearly $6 million across 6 chains (external site)
- NVNM Chain Launches as MANTRA L2 to Power Verifiable AI Data (external site)
- NVNM Chain (external site)
- mantraUSD Whitepaper v1 (external site)
- mantraUSD token record (Mantrascan Blockscout API) (external site)
- Hyperlane registry: USDC warp route to MANTRA (mantra-config.yaml) (external site)
- USDC contract addresses (external site)
- Supported Protocols (external site)
- Default multisig security module configuration (multisigIsm.ts) (external site)
- MANTRA (OM) wallet (external site)
- MANTRA staking (external site)
- Ledger Live currency definition: mantra.ts (external site)
- Ledger Wallet feature switch: currencyMantra.ts (external site)
- Ledger Wallet feature switch defaults: define.ts (off unless set) (external site)
- MANTRA wallet (external site)
- Byzantine Consensus Algorithm (external site)
- IBC overview (external site)
Report an error
Found something wrong or out of date? Reporting is free, and every chain goes through the same process. Published corrections appear in the public log.
Funding disclosure
Funding disclosures appear here when an upkeep arrangement exists, in the form “Upkeep funded by [name]; verdicts unaffected.” The funder ledger has not been published yet. Neutrality & funding