CoinYQ

What is Monad?

Monad is a high-performance, Ethereum-compatible Layer-1 blockchain built to reduce the usual trade-off between throughput, latency, and decentralization. Official documentation describes a network targeting 10,000 transactions per second, 300-millisecond block frequency, and 600-millisecond full finality. Public mainnet launched on November 24, 2025.

MON is Monad's native asset. It is used to pay transaction fees and to stake or delegate stake in support of the network's proof-of-stake security. Mainnet uses chain ID 143 and the currency symbol MON; users can connect familiar Ethereum wallets and tooling by changing the network RPC and chain ID.

Monad is designed as a plug-and-play environment for Ethereum applications. It preserves Ethereum address conventions, typed transaction formats, EVM bytecode compatibility, and broad Ethereum JSON-RPC compatibility, while also supporting Monad-specific facilities such as staking. The first client implementations are open source and split into a consensus repository and an execution repository maintained by Category Labs.

The project positions fast settlement as infrastructure for consumer applications, DeFi, games, payments, and online financial systems. Its architecture is intended to let applications keep Ethereum's development model while gaining shorter block intervals, faster finality, and lower-fee capacity.

What problem does Monad solve?

The design addresses Ethereum's scalability bottlenecks: a conventional EVM chain has limited execution throughput, relatively long block intervals, and a large delay between transaction submission and economic finality. Increasing performance by relying on unusually powerful hardware or a small validator set can, however, weaken accessibility and decentralization.

Monad's approach is to improve software utilization of commodity-oriented validator infrastructure rather than replace Ethereum compatibility with a new programming model. The protocol separates consensus from execution in a pipeline, executes independent transactions concurrently, optimizes state storage, and uses a BFT design intended to support high throughput and large validator sets. These changes introduce trade-offs that users and operators must understand: gas is charged on the transaction gas limit rather than actual gas used, execution is delayed relative to consensus, and reserve-balance rules can affect transactions from accounts with multiple pending operations.

How does Monad work?

MonadBFT is the protocol's proof-of-stake consensus mechanism. Official documentation describes it as a pipelined, tail-fork-resistant BFT design with linear messaging complexity in the common case, 300-millisecond blocks, 600-millisecond full finality, and support for a large validator set. Delegation is supported in protocol, allowing MON holders to participate through validators without operating a direct consensus node.

Consensus and execution are asynchronous and pipelined: nodes establish the official transaction ordering before the resulting state is executed. Monad's specification uses a delayed state root (the documented architecture uses a k=3 block execution gap) so consensus does not have to wait for the current block's execution result. A reserve-balance mechanism helps ensure that accounts can fund pending transactions despite this delayed knowledge of execution outcomes.

Execution retains linear transaction ordering and deterministic serial semantics, but runs many transaction executors in parallel. Each tentative result records storage inputs and outputs; results are committed in original order, and a transaction is rescheduled if its recorded inputs no longer match state. Monad also uses native/JIT compilation for EVM execution and MonadDb, a storage backend optimized for Ethereum-style Merkle-trie state and asynchronous SSD I/O.

MON economics combine transaction fees, staking, validator rewards, and fee burning. The official tokenomics overview states an initial supply of 100 billion MON, a 25 MON reward for each successful block, and base-fee burning. The protocol proposal specifies EIP-1559-style bidding with Monad-specific fee behavior; in particular, fees are charged against gas limits, while the base component is burned and priority fees reward the validator.

Key facts

  • Monad is an Ethereum-compatible proof-of-stake Layer 1.
  • Public mainnet launched November 24, 2025.
  • Mainnet chain ID is 143 and the native currency symbol is MON.
  • Official performance targets are 10,000 TPS, 300 ms block frequency, and 600 ms full finality.
  • Monad supports Ethereum-style addresses, typed transactions, EVM bytecode, and JSON-RPC tooling.
  • Core architecture includes MonadBFT, RaptorCast, asynchronous execution, parallel execution, native/JIT compilation, and MonadDb.
  • The official tokenomics overview states an initial MON supply of 100 billion.
  • The tokenomics overview states that MON is used for transaction fees and staking.
  • A 25 MON block reward is described as inflationary, while base transaction fees are burned.
  • Official source repositories are GPL-3.0 licensed Category Labs repositories for execution and consensus.

Official links

Categories

Related coins

Compare

Frequently asked questions

What is MON used for?

MON is Monad's native asset. It is primarily used to pay transaction fees and to stake or delegate stake to help secure the proof-of-stake network.

Is Monad compatible with Ethereum?

Yes. Monad documents full EVM bytecode compatibility and broad Ethereum RPC compatibility, so Solidity contracts, addresses, wallets, and many existing developer tools can be reused with the Monad network configuration.

What are Monad's mainnet network settings?

The official network page lists Monad Mainnet, chain ID 143, currency symbol MON, and public RPC endpoints such as https://rpc.monad.xyz. It lists MonadVision and Monadscan as block explorers.

How does Monad achieve high throughput?

It combines pipelined MonadBFT consensus, efficient block propagation, asynchronous execution, parallel execution with conflict checking, native/JIT compilation, and the MonadDb state backend. Transactions remain linearly ordered even when execution runs concurrently.

Are Monad fees charged on gas used?

Monad's developer documentation and protocol proposal state that transactions are charged based on gas limit rather than gas actually used. The base-fee component is burned, and the priority component goes to the validator under the documented fee rules.

Where can I read the technical specification or code?

The Monad Initial Specification Proposal is available at https://category-labs.github.io/category-research/monad-initial-spec-proposal.pdf. The execution client is at https://github.com/category-labs/monad and the consensus client is at https://github.com/category-labs/monad-bft.

External trackers

Choose a tracking site for Monad: