Quickstarts
Deploy Your Own Contract with Remix
NEXT WALKTHROUGH: Cross-Chain Flash Loan →
STEP 1 OF 3
ALL QUICKSTARTS →
STEP 1 OF 3 · ON L1, THEN ITS PROXY ON L2
ON L1
Storage
the contract you deploy
ON L2
proxy(Storage)
a stand-in at a CREATE2 address
IN REMIX AND METAMASK
  1. Environment Browser Extension, MetaMask on Gnosis Chiado
  2. Deploy contracts/1_Storage.sol
  3. Switch MetaMask to the L2 you added
  4. EEZ tab → Create Proxy: origin EEZ L1, your Storage address → Preview → Create

WHAT THIS PROVESA call you made on the L2 changed a contract you deployed on L1: retrieve() on L1 returns the number you stored from L2.

WHAT IT DOESN'TIt doesn't show a revert unwinding both chains. On mainnet each step spends real ETH, and Remix's EEZ tab is an alpha, so its screens may change.

DAPP DEVELOPERS

Deploy Your Own Contract with Remix

Deploy a contract on L1 with Remix, give it a proxy on L2, and call it from L2. Each step lists its clicks, and the panel shows the upstream code they run.

BEFORE YOU START
  1. Open Remix. Its EEZ tab is an alpha.
  2. MetaMask on Gnosis Chiado, with free test xDAI from the Gnosis faucet.
  3. Add the L2 to MetaMask: RPC https://eez.dev/composer/l2, chain ID 699169.
  4. Gas on the L2: bridge from Chiado on the EEZ-X Testnet dashboard.
  5. In Remix, Settings → EEZ, add L2 · https://eez.dev/composer/l2 · 699169. Remix's built-in entry still has an older chain ID.
WHAT YOU'LL LEARN
  • 01 · A PROXY IS YOUR CONTRACT ON L2.Create Proxy deploys a stand-in for your L1 address at a predictable CREATE2 address.
  • 02 · CALL IT LIKE A LOCAL CONTRACT.The proxy's fallback hands your call to the L2 manager as a cross-chain call.
  • 03 · IT LANDS ON L1.EEZ runs the call through your L2 account's proxy, and Storage changes on L1.

Verified against eez-core-protocol Git commit 9a1f815 and Remix 2.6.9; interfaces may move.

UP NEXTCross-Chain Flash Loan