Mantle is a suite of Ethereum scaling solutions including an optimistic rollup and ZK rollup built using an iterative modular chain approach, and supported by Mantle’s native token $MNT.
Mantle V2 is an upgrade of Mantle V1, tailored with specific adaptations to work seamlessly within the BedRock infrastructure.
Through its adaptations to the BedRock upgraded infrastructure, Mantle V2 has realized significant enhancements, including support for reduced gas fees, shorter deposit times, optimized node performance, and improved Ethereum compatibility, among other benefits. For more detailed information, please refer to this documentation.
Furthermore, due to the modular design of the Mantle Network, it supports a diverse range of components at varying layers. In comparison to OP Stack-based Rollups adapted to complete BedRock upgrades, Mantle V2 offers support for a broader spectrum of technology stacks and modules, for example, Mantle Network will introduce a new DA scheme implemented using EigenDA technology called MantleDA.
Another significant enhancement involves the adoption of $MNT as the native token for Mantle Network, departing from the more common choice of $ETH in OP Stack implementations. This adjustment aligns the design more closely with Ethereum's native architecture, leading to reduced development and maintenance costs.
We encourage you to check out the Mantle tech docs to learn more about the inner workings of Mantle.
root ├── packages │ ├── balance-monitor: A forta agent which detects when a specified account balance is below the specified threshold │ ├── chain-mon: Chain monitoring services │ ├── common-ts: Common tools for building apps in TypeScript │ ├── contracts: L1 and L2 smart contracts for Mantle │ ├── contracts-bedrock: BedRock upgrade contracts for Mantle │ ├── contracts-periphery: Periphery contracts for Mantle │ ├── core-utils: Low-level utilities that make building Mantle easier │ ├── data-transport-layer: Service for indexing Mantle-related L1 data │ ├── fault-detector: Service for detecting Sequencer faults │ ├── hardhat-deploy-config: Hardhat deploy config │ ├── message-relayer: Tool for automatically relaying L1<>L2 messages in development │ ├── replica-healthcheck: Service for monitoring the health of a replica node │ └── sdk: provides a set of tools for interacting with Mantle ~~ Production ~~ ├── batch-submitter: Service for submitting batches of transactions and results to L1 ├── bss-core: Core batch-submitter logic and utilities ├── gas-oracle: Service for updating L1 gas prices on L2 ├── integration-tests: Various integration tests for the Mantle network ├── l2geth: Mantle client software, a fork of geth v1.9.10 ├── l2geth-exporter: A prometheus exporter to collect/serve metrics from an L2 geth node ├── op-batcher: L2-Batch Submitter, submits bundles of batches to L1 ├── op-bindings: Go bindings for Bedrock smart contracts ├── op-chain-ops: State surgery utilities ├── op-challenger: Dispute game challenge agent ├── op-e2e: End-to-End testing of all bedrock components in Go ├── op-heartbeat: Heartbeat monitor service ├── op-node: rollup consensus-layer client ├── op-program: Fault proof program ├── op-proposer: L2-Output Submitter, submits proposals to L1 ├── op-service: Common codebase utilities ├── op-signer: Signer service client ├── op-wheel: Database utilities ├── ops: A Docker compose project for running Mantle ├── ops-bedrock: Bedrock devnet work ├── proxyd: Configurable RPC request router and proxy ├── specs: Specs for Mantle network with BedRock upgrade ├── technical-documents: Audits and postmortem reports
Read through CONTRIBUTING.md for a general overview of our contribution process. Then check out our list of good first issues to find something fun to work on!
Code forked from go-ethereum under the name l2geth is licensed under the GNU GPLv3 in accordance with the original license.
All other files within this repository are licensed under the MIT License unless stated otherwise.