Search

Search for projects by name

Morph logo
Morph

Badges

About

Morph is an EVM compatible rollup. It operates as an optimistic rollup with ZK fault proofs and has plans for decentralizing the Sequencer. Their mission is to build the first blockchain for consumers, where user-friendly applications integrate seamlessly...


  • Total Value SecuredTVS
    $27.08 M3.65%
  • Past day UOPSDaily UOPS
    0.0456.1%
  • Stage
  • Gas token
    ETH

  • Type
    Optimistic Rollup
  • Purpose
    Universal
  • Chain ID
    2818

  • Tokens breakdown

    Value secured breakdown

    View TVS breakdown
    Sequencer failureState validationData availabilityExit windowProposer failure

    Badges

    About

    Morph is an EVM compatible rollup. It operates as an optimistic rollup with ZK fault proofs and has plans for decentralizing the Sequencer. Their mission is to build the first blockchain for consumers, where user-friendly applications integrate seamlessly...


    Total
    Canonically BridgedCanonically Bridged ValueCanonical
    Natively MintedNatively Minted TokensNative
    Externally BridgedExternally Bridged ValueExternal

    ETH & derivatives
    Stablecoins
    BTC & derivatives
    Other

    2025 Jan 04 — 2026 Jan 04

    Past Day UOPS
    0.04
    Past Day Ops count
    3.70 K
    Max. UOPS
    12.44
    2025 Aug 09
    Past day UOPS/TPS Ratio
    1.00

    This section shows how much data the project publishes to its data-availability (DA) layer over time. The project currently posts data toEthereumEthereum.


    2025 Jan 04 — 2026 Jan 04


    Data posted
    4.04 GiB
    Avg size per day
    11.30 MiB
    Avg size per L2 UOP
    117.41 B

    Sequencer failureState validationData availabilityExit windowProposer failure
    Sequencer failure
    No mechanism

    There is no mechanism to have transactions be included if the sequencer is down or censoring.

    State validation
    Fraud proofs (1R, ZK)

    Fraud proofs allow actors watching the chain to prove that the state is incorrect. Single round proofs (1R) only require a single transaction to resolve. ZK proofs are used to prove the correctness of the state transition. The system currently operates with at least 5 whitelisted challengers external to the team.

    Data availability
    Onchain

    All of the data needed for proof construction is published on Ethereum L1.

    Exit window
    None

    There is no window for users to exit in case of an unwanted regular upgrade since contracts are instantly upgradable.

    Proposer failure
    Cannot withdraw

    Only the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.

    Morph
    Morph is a
    Stage 0
    Optimistic Rollup.

    Learn more about Rollup stages
    Please keep in mind that these stages do not reflect rollup security, this is an opinionated assessment of rollup maturity based on subjective criteria, created with a goal of incentivizing projects to push toward better decentralization. Each team may have taken different paths to achieve this goal.

    All data required for proofs is published on chain

    All the data that is used to construct the system state is published on chain in the form of cheap blobs or calldata. This ensures that it will be available for enough time.

    1. Rollup.sol - Etherscan source code commitBatch() and commitBatchWithBlobProof() functions
    Learn more about the DA layer here: Ethereum logoEthereum
    Fraud proofs

    Morph uses a one round fault proof system where whitelisted Challengers, if they find a faulty state root within the 2d challenge window, can post a 1 WEI bond and request a ZK proof of the state transition. At least 5 Challengers are operated by entities external to the team. After the challenge, during a 3d proving window, a ZK proof must be delivered, otherwise the state root is considered invalid and the root proposer bond, which is currently set to 1 ETH, is slashed. The zkVM used is SP1 from Succinct. If the valid proof is delivered, the Challenger loses the challenge bond. The Morph Multisig can revert unfinalized batches.

    • Funds can be stolen if no whitelisted challenger posts a challenge for an incorrect state root.

    1. Whitelisted Challengers - Morph Docs
    2. Rollup.sol - Etherscan source code, commitBatch(), challengeState(), proveState() functions

    Program Hashes

    Name
    Hash
    Repository
    Verification
    Used in
    0x0059...8d7e
    Code unknown
    None

    Morph uses decentralised sequencer network

    The system uses a decentralised sequencer/proposer network. At the moment all sequencers are run by Morph and - from the point of Ethereum - they don’t need to reach consensus on a block as any one of them can propose a block with an L2 state root on Ethereum. There is a plan to use tendermint with BLS signatures to verify consensus after Petra upgrade.

    • MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.

    1. L1Staking.sol - Etherscan source code, verifySignature() function

    Regular messaging

    The user initiates L2->L1 messages by submitting a regular transaction on this chain. When the block containing that transaction is settled, the message becomes available for processing on L1. The process of block finalization takes a challenge period of 2d to complete.

    • Funds can be frozen if the operator censors withdrawal transaction.

    1. L1ETHGateway.sol - Etherscan source code, finalizeWithdrawETH function
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner

    Ethereum

    Actors:

    L1Staking 0x0Dc4…43F7

    Contract keeping track of stakers which act as sequencers/proposes. It is responsible for staker registration and withdrawals and for verifying BLS signatures of stakers (currently not implemented).

    • Can interact with Whitelist
      • can send gasless transactions to L2 (L2 gas fee waived)
    Morph Multisig 2 0xB822…4377

    A Multisig with 3/5 threshold.

    • Can interact with L1Staking
      • whitelist stakers (sequencer/proposer), remove stakers, manage staking and slashing amount and reward config
    • Can interact with MultipleVersionRollupVerifier
      • register new verifiers to be used starting from a given L2 batch index
    • Can interact with L1GatewayRouter
      • manage token to escrow mapping and (un-)register escrows
    • Can interact with Rollup
      • can pause and unpause, revert unfinalized batches, update proof window and finalization period, manage challengers, modify the verifier address
    • Can interact with EnforcedTxGateway
      • pause and unpause, update the fee vault
    • Can interact with Whitelist
      • manage the whitelist
    • A Challenger - acting directly
    Morph Multisig 1 0xF101…D887

    A Multisig with 4/6 threshold.

    • Can upgrade with no delay
      • L1Staking
      • L1ETHGateway
      • L1MessageQueueWithGasPriceOracle
      • L1StandardERC20Gateway
      • L1GatewayRouter
      • Rollup
      • EnforcedTxGateway
      • L1CrossDomainMessenger
    • A Challenger - acting directly
    EOA 7, EOA 12, EOA 17, EOA 29 and EOA 39 (5) 0x34E3…97960x6aB0…84A00x76F9…35f40xBBA3…1C800xf0e1…b7e4
    A dashboard to explore contracts and permissions
    Go to Disco
    Disco UI Banner
    A diagram of the smart contract architecture
    A diagram of the smart contract architecture

    Ethereum

    ZkEvmVerifierV1 0x045d…0423

    A snark verifier based on SP1 by Succinct. It verifies RISC-V execution in a PLONK proof. Used to verify the validity of L2 state transitions for single round fraud proofs.

    Contract used to bridge ETH from L1 to L2.

    • Roles:
      • admin: ProxyAdmin; ultimately Morph Multisig 1
    ProxyAdmin 0x3111…16A0
    • Roles:
      • owner: Morph Multisig 1
    L1MessageQueueWithGasPriceOracle 0x3931…C1EFImplementation (Upgradable)Admin

    Contains the array of queued L1 -> L2 messages, either appended using the L1Messenger or the EnforcedTxGateway.

    • Roles:
      • admin: ProxyAdmin; ultimately Morph Multisig 1

    Contract used to bridge ERC20 tokens from L1 to L2. It uses a fixed token list.

    • Roles:
      • admin: ProxyAdmin; ultimately Morph Multisig 1
    • This contract can store any token.
    MultipleVersionRollupVerifier 0x5d15…0EC1

    Used to update the verifier and keep track of current and old versions. Routes to a registered verifier by batch index, so that every batch is verified by the latest verifier that is enabled for this batch.

    • Roles:
      • owner: Morph Multisig 2

    Main entrypoint for depositing ETH and ERC20 tokens, which are then forwarded to the correct escrow.

    • Roles:
      • admin: ProxyAdmin; ultimately Morph Multisig 1
      • owner: Morph Multisig 2

    The main contract of the Morph rollup. Allows to post transaction data and state roots and implements the challenge mechanism along with the proof system. Sequencing and proposing are behind a whitelist.

    • Roles:
      • admin: ProxyAdmin; ultimately Morph Multisig 1
      • challengers: EOA 1, EOA 10, EOA 11, EOA 13, EOA 14, EOA 15, EOA 16, EOA 18, EOA 19, EOA 2, EOA 20, EOA 21, EOA 22, EOA 23, EOA 24, EOA 25, EOA 26, EOA 27, EOA 28, EOA 3, EOA 30, EOA 31, EOA 32, EOA 33, EOA 34, EOA 35, EOA 36, EOA 37, EOA 38, EOA 4, EOA 40, EOA 41, EOA 42, EOA 5, EOA 6, EOA 8, EOA 9, Morph Multisig 2
      • owner: Morph Multisig 2

    Contracts to force L1 -> L2 messages with the L1 sender. Currently paused: true.

    • Roles:
      • admin: ProxyAdmin; ultimately Morph Multisig 1
      • owner: Morph Multisig 2

    Contract used to send L1 -> L2 and relay messages from L2. It allows to replay failed messages and to drop skipped messages. L1 -> L2 messages sent using this contract pay for L2 gas on L1 and will have the aliased address of this contract as the sender.

    • Roles:
      • admin: ProxyAdmin; ultimately Morph Multisig 1
    • This contract stores the following tokens: ETH.
    Whitelist 0xFFaf…6984

    Generic whitelist. Currently used to whitelist addresses that can send or relay messages to/from L2 without paying for L2 gas.

    • Roles:
      • owner: Morph Multisig 2
      • whitelisted: L1Staking

    The current deployment carries some associated risks:

    • Funds can be stolen if a contract receives a malicious code upgrade. There is no delay on code upgrades (CRITICAL).

    Program Hashes

    Name
    Hash
    Repository
    Verification
    Used in
    0x0059...8d7e
    Code unknown
    None