Frontier

Important Messages

Frontier is for developers to deploy and test their apps before public launch of the mainnet. Only whitelisted wallets held by developers can transact on Frontier.

This page is regularly updated.

Chain Parameters

Connecting to Frontier

RPC

MegaETH hosts a public RPC endpoint at https://mainnet.megaeth.com/rpc.

See Realtime API for a list of additional features on top of the standard Ethereum JSON-RPC. These features are available on RPC endpoints provided by MegaETH; availability varies on third-party endpoints.

Block Explorer

Blockscout is available.

Developing Smart Contracts

MegaETH’s execution environment is called MegaEVM. It is fully compatible with Ethereum smart contracts but introduces a few differences compared to Ethereum’s EVM especially around the gas model. See the MegaEVM manual page for a list of differences. Implementation of MegaEVM is opensource and can be found on GitHub.

Because of the said differences, toolchains not yet customized for MegaETH might incorrectly estimate the amount of gas a transaction needs if they use their own EVM implementations, as opposed to MegaEVM, to locally simulate the transaction. Sometimes, this issue causes the RPC to throw “intrinsic gas too low” errors or the transaction to run out of gas and revert. The solution is to either tell the toolchain to skip local gas estimation and use a hardcoded gas limit (for forge script, as an example, --gas-limit with a sufficiently large number plus --skip-simulation), or use MegaETH’s RPC servers to estimate gas.

The best tool for debugging MegaETH transactions is mega-evme. It uses the aforementioned opensource implementation of MegaEVM and can thus perfectly simulate any transaction’s behavior on MegaETH. Instructions on building and using mega-evme are available here.

Using the Canonical Bridge

As a reminder, Frontier is for developers to deploy their apps ahead of the public mainnet launch. For regular users, bridging tokens to Frontier is considered EXTREMELY RISKY AND RECKLESS and SHOULD NOT BE ATTEMPTED.

No guarantee of any kind is made for any token bridged to Frontier through any mechanism.

MegaETH’s canonical bridge is the preferred method to bridge Ether (ETH) and ERC20 tokens from Ethereum to MegaETH. The Ethereum side of the bridge is at 0x0CA3A2FBC3D770b578223FBB6b062fa875a2eE75 on Ethereum mainnet. Currently, it runs OP Stack’s Standard Bridge in its op-contracts/v3.0.0 release with a small patch adjusting a few parameters.

The easiest way to bridge Ether to MegaETH is sending Ether to the aforementioned address on Ethereum mainnet in a plain native transfer. The same amount of Ether sans gas fees will appear in sender’s address on MegaETH after the transfer is finalized on Ethereum mainnet.

For more control, use the depositETH method of the bridge contract. It allows for specifying the (approximate) amount of gas that should be charged by and forwarded from Ethereum mainnet to MegaETH for the deposit transaction to use, as well as adding extra data to the transaction. As an example, the following cast send command calls depositETH to bridge 0.001 Ether with 61000 gas and extra data bunny.

cast send 0x0CA3A2FBC3D770b578223FBB6b062fa875a2eE75 'depositETH(uint32, bytes)' 61000 "0x62756e6e79" --value 0.001ether

Contracts of Potential Interest

On MegaETH Mainnet (Frontier)

See OP Stack docs for a complete list of predeployed and preinstalled contracts.

On Ethereum Mainnet

MegaETH’s smart contracts are from OP Stack’s op-contracts/v3.0.0 release. See OP Stack docs for descriptions of these contracts.