Home/Monad

Monad

EVM-compatible Layer 1 with parallel execution, sub-second finality, and chain-specific execution rules. Explore how these capabilities change onboarding, transaction feedback, and everyday app interactions.

2 proposals7 chain guides2 Final MIPs
Monad catalog

Monad proposals

Numbered MIPs that apply to Monad, shown with their proposal lifecycle status.

Monad catalog

Monad chain guides

Editorial guides to Monad-specific behavior. Check each guide's review date and official documentation for current integration details.

Designing on Monad

What changes for UX on Monad

Connect the network's capabilities to the interactions you design, with practical examples and the constraints to keep in view.

Opportunities

Where the network can change the interactions you design.

Faster confirmation feedback

Monad documents 300 ms blocks and 600 ms consensus finality. Wallet approval, execution, and RPC delivery still affect how long a person waits.

Design for it

Confirm a payment or swap inline once its result and required commitment are observed. Keep a delayed state available; never mark success on a timer.

Frequent, small-value actions

Low network fees can make small, repeated actions practical. Costs still depend on the transaction and current network conditions.

Design for it

Explore tips, game actions, or frequent updates. Account for signing prompts and permissions, which can outweigh the wait for the chain.

More simultaneous activity

Parallel execution increases capacity while preserving ordered transaction results. The documented 10,000+ TPS figure is network capacity, not the speed of one action.

Design for it

Give each action its own progress and result in activity-heavy flows. Sort feeds by block order and transaction index, not by when updates arrive.

Design considerations

Chain-specific behavior to account for in feedback, fees, and recovery.

Live updates before settlement

Some feeds report speculatively executed blocks before finalization. These updates can change. Block finalization and later verification of execution outputs are also distinct.

Design for it

Label early trading or game updates as provisional and reconcile changes. Wait for the required commitment before crediting a deposit or releasing value.

Different fee estimation

Monad charges for the gas limit set on a transaction, not just the gas it consumes. An oversized safety buffer can increase the amount paid.

Design for it

Quote fees using current Monad estimates. Explain manual gas-limit changes and refresh stale simulations before signing, rather than reusing Ethereum defaults.

Balance and send eligibility

The reserve mechanism considers delegation and inflight transactions. Its 10 MON parameter is not a universal deposit or a fixed deduction from every balance.

Design for it

Calculate Send max for the specific action and account state. Explain when pending transactions or undelegation require a wait, and show a recovery path beside the balance.

Pending transactions and retries

A submission hash means an RPC node accepted the transaction, not that it was included. Pending transactions do not appear in standard transaction-by-hash lookups.

Design for it

Keep submitted actions visible locally and reconcile them with receipts and nonce state. Explain delayed inclusion before offering a retry that could duplicate an action.

Comparison

Coming from Ethereum L1?

A quick reference for adapting an Ethereum L1 experience. Layer 2 networks have their own timing, fee, and settlement behavior.

Scroll horizontally to compare both networks.

AspectEthereum L1Monad
Block timing12-second slots; inclusion is not finality300 ms blocks; 600 ms consensus finality, separate from execution-result availability
Gas chargedBased on gas usedBased on the gas limit set for the transaction
Pending visibilityPending lookups and subscriptions are available, depending on the providerNo global mempool view; track local submissions and use supported node-status methods
Balance rulesNo Monad reserve mechanismReserve eligibility depends on account state and inflight transactions
Tooling

Tools for building on Monad

Supporting libraries and products that can be used with Monad. They are separate from the Monad protocol and may also support other EVM chains.

Mera passkey accounts

Mera is Category Labs' preview TypeScript library for creating standard EVM accounts from passkeys. It works across chains and platforms, with authenticator support and account recovery determined by the provider and application.

EIP context

EIP context on Monad

Ethereum standards still inform cross-chain and account design on Monad.

EIP-4844Blob transactions
Context
On Ethereum

EIP-4844 gives rollups temporary blob data for lower-cost data availability on Ethereum.

Context on Monad

EIP-4844 is an Ethereum capability, not an available Monad feature. Products spanning Ethereum rollups and Monad still need network and bridge states.

Design Implication

Keep network selection, bridging, and data-availability states when the product spans chains. Do not infer them from Monad throughput.

EIP-7951P-256 signature verification
Context
On Ethereum

Ethereum activated EIP-7951 in Fusaka. It verifies P-256 signatures but does not choose a wallet, credential, backup, or recovery model.

Context on Monad

Monad exposes P-256 verification at 0x0100. Mera (in preview) offers a separate passkey account path using ordinary EOA signing keys.

Design Implication

Choose the account implementation, then design for its supported authenticators, signing sessions, and recovery paths.