Overviews
Mantle Network is an EVM-compatible scaling solution for Ethereum built as a ZK Validity Rollup. All contracts and tools that run on Ethereum can be used on Mantle with minimal modification. Leveraging its modular architecture, Mantle separates execution, data availability, proof generation, and settlement into independent modules. Mantle now uses ZK validity proofs together with innovative data availability solutions to provide lower-cost and more accessible data availability while fully inheriting Ethereum’s security guarantees.
Our protocol design philosophy aims to offer users a less costly and more user-friendly experience, provide developers with a simpler and more flexible development environment, and deliver a comprehensive set of infrastructure for the next wave of mass-adopted dApps.
Key Features of Mantle Network
Built as a Rollup
Utilizes Ethereum validators and consensus protocols to significantly reduce gas fees, decrease latency, and increase throughput. Users can customize transaction confirmation requirements to provide near real-time confirmation latency with minimal security settings.
Modular Architecture
Unlike traditional monolithic chains that execute transaction execution, consensus, settlement, and storage at the same network layer, Mantle separates these functions into individual modules as a modular chain. These include an EVM-compatible execution layer developed by Mantle for transaction execution, a consensus layer and settlement layer completed on Ethereum, and an external DA component.
Secured by Ethereum
All Rollup state transitions must pass through Ethereum’s verification process via ZK validity proofs, ensuring that only mathematically correct state roots are finalized. Once verified by the Ethereum settlement contract, the batch achieves immediate finality without requiring any challenge period.
Modular Data Availability
Independent DA modules, such as EigenDA technology. According to internal assessments, this translates to potential cost savings of more than 90% compared to on-chain L1.
Last updated
Was this helpful?

