Code Monkey home page Code Monkey logo

mantlenetworkio / mantle Goto Github PK

View Code? Open in Web Editor NEW
218.0 22.0 98.0 112.47 MB

Mantle | Mass adoption of decentralized & token-governed technologies. With Mantle Network, Mantle Treasury, and token holder-governed products initiatives.

Home Page: https://www.mantle.xyz

License: MIT License

JavaScript 3.05% Shell 0.20% Makefile 0.16% Dockerfile 0.09% Go 75.38% TypeScript 8.46% Solidity 6.75% NSIS 0.16% Ruby 0.01% Python 0.05% HTML 0.08% Assembly 0.43% C 4.60% M4 0.18% Sage 0.21% Java 0.21%

mantle's Introduction

Website    |    Tech Docs




Introduction

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.

It is designed to bolster support for hyper-scaled throughput decentralized applications (dApps) — from derivatives decentralized exchanges (DEXs), to gaming, to operations of decentralized autonomous organizations (DAOs).


Goals

Layer 2 rollups are built to address the scaling limitations of Ethereum by taking transaction processing to a separate execution layer, but this inevitably exposes users to the high gas fees and limited throughput on Layer 1.

Mantle's modular architecture helps achieve greater network efficiency for resources at hand, while maintaining the same level of security for all network actors. Increased network performance also enables better fraud proof and ZK proof technology, essentially unlocking the true potential of L2 rollups.

Different parts of the Mantle tech stack are specialized to tackle specific issues.

  • Data Availability: Data Availability powered by EigenDA technology, an innovative re-staking solution that leverages Ethereum's validator network to bring the security of L1 to L2
  • EVM-level Fraud Proofs: Improved fraud proofs that are evaluated using EVM-level instructions

We encourage you to check out the Mantle tech docs to learn more about the inner workings of Mantle.


Quick Start

Useful Addresses

Name Mainnet Testnet
Token Faucet N/A https://faucet.testnet.mantle.xyz/
Mantle Bridge https://bridge.mantle.xyz/ https://bridge.testnet.mantle.xyz/
Mantle Explorer https://explorer.mantle.xyz/ https://explorer.testnet.mantle.xyz/
Mantle Node RPC URL https://rpc.mantle.xyz/ https://rpc.testnet.mantle.xyz/
Chain ID 5000 5001

DApps need to connect to nodes for fetching block data and sending transactions to the Mantle network. Our JSON-RPC API supports HTTPS and WebSocket connections.

Service Mainnet Testnet
RPC https://rpc.mantle.xyz/ https://rpc.testnet.mantle.xyz/
WebSocket wss://ws.mantle.xyz wss://ws.testnet.mantle.xyz

Using the Mantle SDK

You can use npm or yarn package managers to download and install the @mantleio/sdk package. We'll use yarn in this example.

  1. Set up a project directory.
mkdir MantleSDK
cd MantleSDK
npm init --yes
  1. Download and install the SDK package using this command.
yarn add -D @mantleio/sdk
  1. Create a <filename>.js script and get started by making a request, for instance, to fetch the current L1 gas price.
const ethers = require("ethers")
const mantle = require("@mantleio/sdk")

const l2RpcProvider = new ethers.providers.JsonRpcProvider("https://rpc.testnet.mantle.xyz")

async function main() {

    console.log(await mantle.getL1GasPrice(l2RpcProvider))
}

main();
  1. Run your script using the node <filename>.js command to see the output.

Feel free to browse through our compilation of tutorials that use the Mantle SDK to demonstrate common functionality such as bridging assets between Mantle and Ethereum, and more.

The SDK docs provide complete reference of all the methods available as part of the Mantle SDK to facilitate interaction between applications and Mantle network.


Spin up a Verifier Node

There are multiple roles associated with Mantle nodes. Rollup Verifiers mainly sync rollup data from Mantle's trusted Sequencer (to be decentralized in the future!). dApp builders who run their own verifier nodes have the benefit of being able to simulate L2 transactions, among other advantages, and have ready access to them without rate-limiting (as opposed to public RPCs).

Here's a tutorial describing the process of deploying a verifier node.


Directory Structure

root
├── packages
│   ├── common-ts: Common tools for building apps in TypeScript
│   ├── contracts: L1 and L2 smart 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
│   ├── 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
├── mt-batcher: Service for submitting batches of transactions to EigenDA
├── mt-challenger: EigenDA data fraud proof
├── 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  (deprecated for BEDROCK upgrade)
├── l2geth-exporter: A prometheus exporter to collect/serve metrics from an L2 geth node
├── proxyd: Configurable RPC request router and proxy

How to Contribute

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!


License

Code forked from optimism under the name optimism 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.

mantle's People

Contributors

agnarsong avatar aodhgan avatar bradyjoestar avatar byteflyfunny avatar chengwenxi avatar curryxbo avatar davionlabs-github-bot avatar ethandavionlabs avatar ethanncnm avatar fletcherman avatar grezle avatar guoshijiang avatar hxhke avatar kukoomomo avatar lagougou avatar libevm avatar lqs0317 avatar omahs avatar sha3ns avatar shellteo avatar shidaxi avatar tri-stone avatar tw5428561 avatar wukongcheng avatar xagnarx avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

mantle's Issues

re-deploy qa contracts

Started the two same sequencer service and sent the withdraw tx in the meantime polluted the contracts in goerli testnet.

So need to redeploy new contracts and changed the @bitdaoio/sdk.

SDK replace

Currently It seems that @bitdaoio/sdk not worked for bridging custom erc20 token between L1 and L2.

We will change it by the pre-version of @optimism/sdk.

CommitId:

940cfacb 作者 Matthew Slipper [email protected],2022/5/17 上午12:46

fix fault-detector

Currently the fault-detector can't work as expected because of queryFilter will search from 0 to latest block.

[dev] tss node

  • Websocket client

  • Tss Core
    p2p communication
    tss algorithm

  • Request Validation

Fatal bug: two same sequencer

I used two sequencer to send the withdraw tx in the meantime, and the tx is in the pending state.

One of batch-submitter report the following errors:

15|10:06:04.465] Sequencer unable to craft batch tx       err="execution reverted: Attempted to append more elements than are available in the queue."
INFO [08-15|10:06:12.714] Sequencer fetching current block range 
INFO [08-15|10:06:12.718] Proposer fetching current block range 
INFO [08-15|10:06:12.982] Sequencer block range                    start=142 end=151
INFO [08-15|10:06:13.238] Proposer no updates                      start=142 end=142
INFO [08-15|10:06:13.258] Sequencer crafting batch tx              start=142 end=151 nonce=469 type=ZLIB
INFO [08-15|10:06:13.288] Sequencer testing batch size             calldata_size=12408 min_tx_size=32 max_tx_size=90000
INFO [08-15|10:06:13.288] Sequencer batch constructed              num_txs=9  final_size=12408 batch_type=ZLIB
ERROR[08-

When I restart the l2-geth in one cluster, it showed the following bug:

ERROR[08-15|10:18:29.206] Timestamp monotonicity violation         hash=0xaebc2f6e28717e3134acadd8452b10ac52c48a995a4e1196d88ca443c545491b latest=1660558709 tx=1660545605
ERROR[08-15|10:18:29.206] Blocknumber monotonicity violation       hash=0xaebc2f6e28717e3134acadd8452b10ac52c48a995a4e1196d88ca443c545491b new=7407764 old=7408448
ERROR[08-15|10:18:29.207] Monotonicity violation                   index=32    parent=1660555041 tx=1660545605
ERROR[08-15|10:18:29.207] Problem committing transaction           msg="nonce too high"
ERROR[08-15|10:18:29.207] Got error waiting for transaction to be added to chain msg="nonce too high"
CRIT [08-15|10:18:29.207] Sequencer cannot sync transactions to tip err="Verifier cannot sync transactions with backend l1: Cannot sync transactions with backend l1: Cannot apply transaction: nonce too high"

And it seemed that it can't restore from the pre-state, and we need to re-deploy the contracts on L1.

In production env, it is unbearable.

This is illegal operation. How should we avoid this when we also want the high availabity in the production env?

!!! Implement decentralized sequencers

Summary

Implement decentralized sequencers, there are two main goals here:

  • Anyone can participate in the sequencer set as a L2 block producer.
  • Reduce MEV, each sequencer participating in the consensus process is able to determine transaction ordering.

Task List

Layer 1

  • Sequencer set selection on L1 ,#139
    • Register Sequencer with mintAddress(l2geth/miner/miner.go#Miner.coinbase) and nodeID(l2geth/p2p/encode/node.go#Node.id).
    • Set Scheduler with nodeID.

Layer 2

L2geth

  • Rotation mechanism
    • Weighted round-robin algorithm, #16
    • Get Sequencer set from L1's contract, and update mintpower each epoch #55
    • Scheduler broadcast producers #197
    • Switching sequencer for liveless issue
      • Heartbeat: Listen to the connection between Scheduler and Sequencer via l2/geth/p2p pingpong mechanism(Identity authentication by nodeID).
      • Timeout: Sequencer does not commit the block to the scheduler on time(Identity authentication by mintAddress).
  • Convert l1->l2 transactions and submit these transactions to L2 : TBD
  • Add scheduler consensus in l2geth/consensus:
    • Implement consensus interface to produce block, #59
    • Get the block producer from scheduler, #60
    • Get blocks from scheduler/l2geth (Identity authentication by nodeID), #61

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.