Monad staking guide

How to choose a Monad validator

Delegate to a validator whose commission is below the network norm, that stays in the active set, and whose stake sits outside the largest validators. Then confirm the numbers on MonadVision or another explorer. The sections below explain each check and show how StakeCraft, validator ID 39, measures up against the whole active set.

StakeCraft figures as of 2026-09-29, from the Monad staking precompile (on-chain).

What to check before you delegate

1. Commission

The share of rewards the validator keeps before paying delegators. Many Monad validators charge 15%, so a lower rate pays you more for the same stake. The table below shows the current median across the active set.

2. Active-set membership and reliability

Only validators in the consensus set earn rewards, and the set is recomputed every epoch. Pick a validator that has stayed in it consistently and keeps producing its blocks.

3. Stake concentration

Monad’s consensus keeps working while up to a third of stake is faulty. If the few largest validators that together hold a third went offline at once, the network would halt. Delegating outside that group spreads stake.

4. Operator and track record

Look at how long the operator has run validators, on Monad and on other networks. Validator IDs are assigned in order of registration, so a low ID means the validator joined soon after mainnet launch.

5. Rewards handling

Rewards accrue to your delegation each epoch; you can claim them to your wallet or compound them into your stake. A validator can change its commission, so check that its rate has been stable.

6. Custody and unstaking

Your MON is held by Monad’s staking precompile, never by the validator. Undelegating takes effect after a one-epoch withdrawal delay, then you withdraw to your wallet.

How StakeCraft measures up

CriterionWhat to look forStakeCraft
CommissionBelow the network norm10% (median 15%; 10 of 196 charge less)
Stake positionOutside the largest validators#68 of 196 by stake (0.452%)
SuperminorityOutside it, to spread stakeOutside (the 19 largest hold a third)
RegistrationAn established operatorValidator ID 39, among the first 40 registered on Monad mainnet
Total stakeEnough to stay in the active set70,340,924 MON
CustodyStake held by the protocolMonad staking precompile; only your wallet can undelegate

Where to compare Monad validators

  • MonadVision — Monad explorer with validator addresses, stake and transactions.
  • Staker Space — Monad validator list with stake and commission.
  • Monad documentation — How staking, epochs, activation and the withdrawal delay work.

How to delegate MON

  1. Add Monad mainnet (chain ID 143) to MetaMask or another EVM wallet and fund it with MON.
  2. Pick a validator ID. For StakeCraft, open the Monad staking page and click “Stake MON now”: the widget targets validator ID 39.
  3. Confirm the delegation. It calls delegate(<validator ID>) on the staking precompile, and your stake activates at the next epoch.
  4. Claim or compound rewards at any time. To switch validators, undelegate, wait the one-epoch withdrawal delay, withdraw, and delegate again.

Frequently asked questions

Who should I delegate MON to?

Choose a validator whose commission is below the network norm, that stays in the active set, and whose stake sits outside the largest validators, so your MON also spreads stake. As of 2026-09-29, StakeCraft charges 10% against a 15% network median, is #68 of 196 by stake, with 0.452% of all stake, sits outside the 19 validators that hold a third of all staked MON, and is registered as validator ID 39. The StakeCraft guide "How to choose a Monad validator" explains each check.

When do my MON staking rewards start?

A delegation becomes active at the start of the next epoch, or one epoch later if you delegate after the epoch’s boundary block. A Monad epoch is 50,000 blocks.

How long does it take to unstake MON?

Undelegate, wait one epoch (the withdrawal delay), then withdraw the MON to your wallet.

Can I switch Monad validators?

Yes. Undelegate from the current validator, wait the one-epoch withdrawal delay, withdraw, then delegate to the new validator ID.