FAQs
Yes. All the EVM-compatible Web3 libraries, IDEs, developments frameworks can be used to deploy on and connect to Mantle Network. This includes, but isn't limited to, popular tools such as:
Mantle Network uses the same signature algorithm as Ethereum. (ECDSA on the secp256k1 curve)
The block gas limit is currently set to 30,000,000, or 30M units.
New blocks are generated on L2 every time a new transaction is received, and each block contains a single transaction. Thus, the block time on Mantle Network depends on the transaction volume at any given time.
- Transaction/block finality on L2 is instantaneous
- Transaction/block finality on L1 connects to the challenge period, which is currently set at 7 days
As of mainnet alpha release, fraud proofs are in development. For more details on Mantle Network's implementation, check out the page on Fraud Proofs
The majority of L2 gas costs (>70%) are incurred as the cost to publish data on L1 Ethereum. With Mantle DA powered by EigenDA technology, only state root data (along with very limited transaction data) is posted to L1 contracts, while the rollup data is posted to Mantle DA, which helps bring down the overall cost significantly.
Currently, the only way see DA transaction history is via the Explorer frontend. Here's the link: https://explorer.mantle.xyz/eigenda-batches
Yes. All updated state roots are verified by Rollup Verifiers before they are submitted to L1 as a part of the rollup process.
No. Rollup Verifiers sync rollup data from Mantle DA, which they use to generate state roots and verify the updated state roots generated by the Sequencer before they are published to L1.
If Rollup Verifiers detect a discrepancy when verifying the updated state roots, the rollup mechanism on L2 is temporarily halted. You can learn more about failure handling here: Failure Handling.
- Testnet multicall address:
0xA70bD0f369C776B2774FD3C0949DCb5251fC3b79 - Mainnet multicall address:
0x9155FcC40E05616EBFf068446136308e757e43dA
We currently support CREATE2, and are working on supporting CREATE3 in a future update. Check out the section on opcode differences to learn more.
- 1.A wallet or dApp initiates a transaction
- 2.Sequencer executes transaction
- 3.TSS network signs state roots guaranteeing correctness
- 4.State root data is posted to L1 Ethereum, transaction data is posted to Mante DA
Our gas oracle API currently only supports fetching L2 gas fee. The extra fee being deducted is the L1 rollup fee. This will be fixed soon in a future update!
A transaction sent with the "Max" amount fails with an error stating that the transaction is underpriced because our gas oracle currently only supports fetching L2 gas fee estimation, which is why the wallet undercalculates the actual gas fee that needs to paid since it is not including the L1 rollup fee. This issue will be addressed with a future network update. In the meantime, we recommend leaving at least 0.5 $MNT in your wallet to pay for L1 rollup fees.
For example, if you have 10 $MNT in your wallet, please limit the transaction amount to a maximum of 9.5 $MNT for a single transaction.
The maximum batch transaction size is derived from the target gas configuration. Mantle Network is the same as Ethereum in this regard.
Currently, the gas range has been set to 0.05 - 200 Gwei in order to protect users from overpaying gas fees. This limit is active on Mantle Mainnet, and will soon be applied to testnet as well.
Currently, Mantle Network does NOT support EIP-1559, so we recommend using legacy structuring for your transactions. The order of transactions is FIFO, and it will be executed based on the sequence (time of receiving) they are received in.
Yes. Once the RPC rate limit is reached, access to Explorer API will also be limited.
You can find details on this subject here:
Last modified 20d ago