Mantle
$1.27 B
0.43%
| Website | mantle.xyz |
|---|---|
| App | bridge.mantle.xyz |
| Docs | docs-v2.mantle.xyz |
| Explorer | explorer.mantle.xyzmantlescan.info |
| Repository | github.com/mantlenetworkio |
| Social | Discord@0xMantle0xmantlemantlenetwork |
...
Choose token
USDe (USDe)
Staked USDe (sUSDe)
mETH (mETH)
Mantle (MNT)
Ether (ETH)
Puff (Puff)
Tether USD (USDT)
USD Coin (USDC)
Wrapped BTC (WBTC)
Pendle (PENDLE)
ApeX Token (APEX)
LUSD Stablecoin (LUSD)
SHIBA INU (SHIB)
Wrapped liquid staked Ether 2.0 (wstETH)
Pepe (PEPE)
BitDAO (BIT)
Curve DAO Token (CRV)...
Funds can be stolen if
Funds can be lost if
Funds can be frozen if
MEV can be extracted if
State validation
In developmentCurrently the system permits invalid state roots. More details in project overview.
Data availability
ExternalProof construction and state derivation rely fully on data that is NOT published on chain. MantleDA contracts are forked from EigenDA with significant modifications, most importantly removal of slashing conditions. DA fraud proof mechanism is not live yet.
Exit window
NoneThere is no window for users to exit in case of an unwanted upgrade since contracts are instantly upgradable.
Sequencer failure
Self sequenceIn the event of a sequencer failure, users can force transactions to be included in the project’s chain by sending them to L1. There is a 12h delay on this operation.
Proposer failure
Cannot withdrawOnly the whitelisted proposers can publish state roots on L1, so in the event of failure the withdrawals are frozen.
Fraud proofs are in development
Ultimately, OP stack chains will use interactive fraud proofs to enforce state correctness. This feature is currently in development and the system permits invalid state roots.
Funds can be stolen if an invalid state root is submitted to the system (CRITICAL).
Data is not stored on chain
The transaction data is not recorded on the Ethereum main chain. The sequencer posts the transactions data batch root, and then propagates the data to off-chain permissioned nodes to sign. It subsequently posts the nodes signatures on chain to verify they belong to the specified members of the quorum, and that the minimum stake threshold is met.
Funds can be lost if the external data becomes unavailable (CRITICAL).
- DataLayrServiceManager.sol#L389 - Etherscan source code, confirmDataStore function
- DataLayrServiceManager.sol#L404 - Etherscan source code, signature verification check
- Derivation: Batch submission - OP Mainnet specs
- BatchInbox - Etherscan address
- OptimismPortal.sol - Etherscan source code, depositTransaction function
The system has a centralized operator
The operator is the only entity that can propose blocks. A live and trustworthy operator is vital to the health of the system.
MEV can be extracted if the operator exploits their centralized position and frontruns user transactions.
Users can force any transaction
Because the state of the system is based on transactions submitted on-chain and anyone can submit their transactions there it allows the users to circumvent censorship by interacting with the smart contract directly.
Regular exit
The user initiates the withdrawal by submitting a regular transaction on this chain. When the block containing that transaction is finalized the funds become available for withdrawal on L1. The process of block finalization takes a challenge period of 7d to complete. Finally the user submits an L1 transaction to claim the funds. This transaction requires a merkle proof.
Funds can be frozen if the centralized validator goes down. Users cannot produce blocks themselves and exiting the system requires new block production (CRITICAL).
Forced exit
If the user experiences censorship from the operator with regular exit they can submit their withdrawal requests directly on L1. The system is then obliged to service this request or halt all withdrawals, including forced withdrawals from L1 and regular withdrawals initiated on L2. Once the force operation is submitted and if the request is serviced, the operation follows the flow of a regular exit.
EVM compatible smart contracts are supported
OP stack chains are pursuing the EVM Equivalence model. No changes to smart contracts are required regardless of the language they are written in, i.e. anything deployed on L1 can be deployed on L2.
The system uses the following set of permissioned addresses:
Owner of AddressManager. Admin of OptimismPortal, SystemConfig, L2OutputOracle, L1StandardBridge.
Central actor allowed to commit L2 transactions to L1.
Central actor allowed to post new L2 state roots to L1.
Central actor allowed to delete L2 state roots proposed by a Proposer.
Central actor allowed to pause deposits and withdrawals.
This address can upgrade the following contracts: L1CrossDomainMessenger, L1StandardBridge, AddressManager, L1MantleToken, EigenDataLayerChain, SystemConfig. This is a Gnosis Safe with 6 / 13 threshold.
Those are the participants of the OwnerMultisig.
This address is the owner of the following contracts: EigenDataLayerChain, DataLayrServiceManager, BLSRegistry, Delegation. It is also designated as a Challenger and Guardian of the OptimismPortal, meaning it can halt withdrawals and change incorrect state roots. This is a Gnosis Safe with 3 / 7 threshold.
Those are the participants of the Owner2Multisig.
The system consists of the following smart contracts:
The L2OutputOracle contract contains a list of proposed state roots which Proposers assert to be a result of block execution. Currently only the PROPOSER address can submit new state roots.
Can be upgraded by: ProxyAdmin
Upgrade delay: No delay
The OptimismPortal contract is the main entry point to deposit funds from L1 to L2. It also allows to prove and finalize withdrawals. This contract stores the following tokens: ETH, MNT.
Can be upgraded by: ProxyAdmin
Upgrade delay: No delay
It contains configuration parameters such as the Sequencer address, the L2 gas limit and the unsafe block signer address.
Can be upgraded by: ProxyAdmin
Upgrade delay: No delay
The L1CrossDomainMessenger (L1xDM) contract sends messages from L1 to L2, and relays messages from L2 onto L1. In the event that a message sent from L1 to L2 is rejected for exceeding the L2 epoch gas limit, it can be resubmitted via this contract’s replay function.
Can be upgraded by: ProxyAdmin
Upgrade delay: No delay
The L1StandardBridge contract is the main entry point to deposit ERC20 tokens from L1 to L2. This contract can store any token.
Can be upgraded by: ProxyAdmin
Upgrade delay: No delay
This contract is the main entry point for data availability. It is responsible for storing transaction data headers and confirming the data store by verifying operators signatures.
This contract strores the number of Mantle DA operators and their public keys. It also store the quorum threshold and the minimum stake required to be part of the quorum.
Contract managing different investment strategies, forked from EigenLayer StrategyManager.
Basic do-nothing investment strategy.
Basic do-nothing investment strategy.
This is a library that stores the mappings between names and their addresses. Changing the values effectively upgrades the system. It is controlled by the OwnerMultisig.
Can be upgraded by: OwnerMultisig
Upgrade delay: No delay
Mantle uses Mantle (MNT) as the designated gas token, allowing users to utilize MNT to pay for blockspace.
Value Locked is calculated based on these smart contracts and tokens:
Main entry point for users depositing ERC20 token that do not require custom gateway.
Can be upgraded by: ProxyAdmin
Upgrade delay: No delay
Main entry point for users depositing ETH, MNT.
Can be upgraded by: ProxyAdmin
Upgrade delay: No delay
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).
