Mantra is a Proof-of-Stake Blockchain with Validator Delegation Options

Mantra is a validator-choice workflow on MANTRA Chain: hold native MANTRA in a Cosmos wallet, select an active validator, sign one delegation and confirm the resulting position before managing rewards or starting an eight-day undelegation. The decisive constraint is liquidity. Delegated coins leave the spendable balance, and an undelegation restores them only after its completion time.

This brief follows that single position from prerequisite checks to final withdrawal. It focuses on network selection, validator fields, transaction confirmation, redelegation and the visible states that prove each action settled.

Unbonding creates an eight-day liquidity gap

Eight days separate an accepted MANTRA undelegation from the return of spendable principal to the wallet.

Delegated MANTRA does not sit in the spendable balance. When MANTRA Chain accepts an undelegation, the chain creates an unbonding entry with a completion time and stops new staking rewards on that amount. The entry persists through wallet disconnections and browser closures because CometBFT records it in consensus state. Plan the withdrawal before the funds are needed: submitting the exit begins the wait rather than restoring liquidity. A remaining partial delegation stays bonded and continues as its own validator position. The dashboard can display both states simultaneously.

Redelegation instead changes validators while keeping principal bonded, leaving the liquid balance unchanged.

Native balance and network selection come first

Two execution environments share the MANTRA name, but native delegation starts on the Cosmos side of MANTRA Chain.

Match the chain and address

Native staking uses Cosmos chain ID mantra-1 and account addresses with the mantra prefix. Keplr connects to that environment. MANTRA EVM uses numeric chain ID 5888, where MetaMask and Rabby manage EVM accounts and wMANTRA follows ERC-20 mechanics. Moving an asset into the EVM environment changes the representation controlled by the wallet; it does not create native Cosmos staking balance. Before opening MANTRA Zone, confirm that the spendable coin appears in the Keplr account selected for delegation. The validator destination later carries a mantravaloper prefix. For a worked version, see Mantra requirements step by step.

Read the native unit correctly

Native MANTRA has 18 decimal places, and 1 MANTRA equals 10^18 amantra base units. The 1:4 mainnet token upgrade at block 13000000 changed the staking coin's displayed denomination from OM to MANTRA. Older records therefore contain OM terminology, while the upgraded interface displays MANTRA. Keep some native balance outside the delegation so later signed actions settle from the same account.

Validator selection sets the reward split

Three visible validator fields - active status, commission and delegated stake - shape the first delegation decision.

Active status

An active validator participates in consensus and receives the reward allocation associated with its voting power. An inactive operator remains visible in chain records, but new delegations should target the bonded validator set. MANTRA Zone identifies active positions before the wallet constructs the transaction.

Commission controls

Cosmos SDK records three commission controls for each validator: the present rate, the absolute maximum rate and the maximum change allowed during 24 hours. The validator deducts its present commission from allocated rewards before the delegator share accrues. Its maximum rate establishes a fixed ceiling, while the change limit governs how quickly the present rate moves toward that ceiling. These fields affect future rewards rather than the amount recorded as principal.

Delegated stake

One delegation record connects one delegator account with one validator operator. Bonded stake influences the operator's voting power, so distributing an allocation across two validators produces two distinct positions. Each position carries its own commission setting, rewards and management actions. Choose the split before signing because changing validators later requires a separate redelegation transaction.

One signed delegation creates the position

One signed MsgDelegate transaction binds a chosen MANTRA amount to one validator operator address.

MANTRA Zone turns that message into a short sequence: connect Keplr, select an active validator, enter the amount and review the wallet request. The confirmation screen should identify chain ID mantra-1, the delegating account, the mantravaloper destination and the MANTRA amount. Signing authorizes the staking-module action; it does not transfer control to a receiving wallet. Cosmos SDK reduces the account's spendable balance and records delegation shares against the chosen operator when execution succeeds. The wallet remains the account that manages the position.

Adding funds later uses another MsgDelegate. The chain combines those shares under the same delegator-validator pairing while retaining a separate transaction record for each signed increase.

How do I confirm a Mantra delegation?

One successful transaction hash should reconcile the wallet approval, explorer record and new staking position.

On a first pass, MANTRA Chain confirmation combines block inclusion with a successful execution code. Open the transaction hash in Mintscan and inspect code 0, the mantra -prefixed delegator address, the mantravaloper destination and the base-unit amount. The corresponding human-readable amount should appear under that validator in MANTRA Zone after the interface refreshes. Keplr then shows less spendable MANTRA because the principal sits in the staking module. These three views describe one state transition from liquid balance to bonded delegation.

A pending broadcast or missing hash is not a confirmed position, even when the wallet closes without displaying an error.

Crucially, MANTRA Chain configures a 3-second timeout_commit, but that parameter schedules block rounds rather than guaranteeing a three-second interface update. Treat block inclusion and code 0 as the confirmation threshold. The resulting position should match the validator, amount and account approved in Keplr.

Reward handling stays separate from principal

Two balances matter after confirmation: delegated principal and separately claimable staking rewards.

Cosmos SDK calculates rewards from network issuance, validator performance and the validator commission applied to its allocation. Those rewards accumulate as a claimable balance rather than automatically increasing the original delegation. MANTRA Zone offers Claim All across eligible positions and Claim Rewards for a selected validator. A claim requires another wallet confirmation and moves the distributed amount into spendable balance. Claim & Stake adds a second action that delegates the claimed amount, increasing the position after execution.

Leaving rewards unclaimed does not change the recorded principal. Position confirmation and reward withdrawal therefore remain separate state transitions with separate transaction hashes.

Redelegation changes the validator without unbonding

Four interface steps move delegated principal between validators without starting the eight-day undelegation clock.

In MANTRA Zone, select the existing staking position, choose redelegation, pick a different active validator and enter the amount. Keplr then signs a MsgBeginRedelegate message naming the source validator, destination validator and MANTRA quantity. Successful execution reduces the source position and increases the destination position without adding principal to the spendable balance. The destination begins carrying the selected stake after the transaction settles.

Cosmos SDK also creates a redelegation entry that tracks the source, destination and completion time. Recently redelegated stake remains subject to redelegation-entry restrictions until that record completes, which prevents repeated immediate movement through several validators. Inspect the destination position and the redelegation record before attempting another validator change.

Partial unstaking preserves the remaining delegation

Two exit sizes are available: undelegate part of the position or request the full delegated amount.

Partial undelegation

A partial exit starts with three interface inputs: the existing validator position, an amount below the displayed delegation and wallet confirmation. MANTRA Zone submits MsgUndelegate for that amount. The staking view then separates the position into a smaller bonded balance and an unbonding entry. Rewards continue accruing on the bonded remainder, while the exiting amount follows its recorded completion time.

Full undelegation

A full exit uses the complete delegated amount in the same message. The validator position falls to zero after successful execution, and the principal moves into the unbonding state rather than the liquid wallet balance. Eight days equals 691 200 seconds, during which undelegating MANTRA remains unavailable and earns no new staking rewards. At completion, the staking module releases the principal automatically to the same mantra -prefixed account.

A worked exit example reaches a spendable balance

Three hypothetical inputs define this worked example: position budget, liquid reserve and later undelegation amount.

The values are a 1 000 MANTRA position budget, a 20 MANTRA reserve and a later 400 MANTRA exit. All three are hypothetical, while the eight-day unbonding period is a fixed protocol input. Transaction charges sit outside this position-budget calculation.

The user delegates 980 MANTRA to one active validator and leaves 20 MANTRA liquid. Confirmation should show 980 MANTRA delegated and 20 MANTRA in the position budget's spendable portion. A later partial undelegation of 400 MANTRA creates an unbonding entry and leaves 580 MANTRA delegated. When the eight days finish, the 400 MANTRA joins the reserved 20 MANTRA. The concrete allocation becomes 420 MANTRA liquid and 580 MANTRA still delegated, preserving the original 1 000 MANTRA total.

A final position review closes the workflow

Four visible states close the workflow: spendable, delegated, claimable and unbonding balances.

Keplr shows the spendable MANTRA controlled by the account. MANTRA Zone shows principal grouped by validator, separate claimable rewards and every active unbonding entry with its completion time. Mintscan supplies the independent transaction and account record. Reconcile all three views against one mantra -prefixed address. A completed delegation appears under its selected validator; a redelegation appears at the destination; a partial exit leaves both bonded and unbonding amounts; a completed full exit returns principal to spendable balance.

The transaction hash anchors each transition even when a wallet or dashboard refreshes later than the chain state.

Once the final unbonding entry completes, the principal becomes available without another unstaking signature. The remaining task is accounting: confirm that the returned amount belongs to the intended address and that any deliberately retained delegation still names the selected validator. That review ends the Mantra first-position workflow with a reconciled wallet state.

Popular questions about Mantra