How to configure MetaMask for Scroll L2? (ZKP Technology)

Adding Scroll L2 Network to MetaMask

1. Open MetaMask and click the network selector dropdown located at the top of the interface.

2. Select “Add network” or “Custom RPC” depending on your MetaMask version.

3. Enter the Scroll L2 Alpha Testnet RPC URL: https://alpha-rpc.scroll.io/.

4. Set Chain ID to 534353 and confirm it matches Scroll’s official documentation.

5. Input the block explorer URL: https://scrollscan.com/ for seamless transaction verification.

6. Name the network “Scroll Alpha Testnet” and save the configuration.

Connecting Wallet to Scroll Bridge Interface

1. Navigate to https://scroll.io/alpha/bridge using a desktop browser with MetaMask installed.

2. Click “Connect Wallet” and select MetaMask from the available options.

3. Approve the connection request in the MetaMask popup window.

4. Ensure MetaMask is switched to the Scroll Alpha Testnet before initiating any bridge action.

5. Confirm that the wallet address displayed on the bridge page matches your MetaMask account.

6. Observe the green status indicator next to the network name in MetaMask to verify active connection.

Obtaining Goerli ETH for Bridging

1. Switch MetaMask to the Goerli test network via the network selector.

2. Visit https://goerli-faucet.pk910.de/ and connect your wallet.

3. Initiate the PoW mining process by keeping the tab open until sufficient Goerli ETH is credited.

4. Verify receipt by checking the balance in MetaMask under the Goerli network.

5. Confirm transaction history includes at least one successful faucet transaction with non-zero value.

6. Retain at least 0.5 Goerli ETH to cover bridging gas costs and multiple L2 interactions.

Executing Cross-Layer Deposit

1. Return to the Scroll bridge interface while MetaMask remains connected and set to Goerli.

2. Enter the desired ETH amount—minimum recommended is 0.01 ETH.

3. Click “Deposit” and wait for the first MetaMask confirmation prompt for approval.

4. After approval, monitor the progress bar indicating zk-prover queue status.

5. Upon completion, MetaMask will auto-switch to Scroll Alpha Testnet and reflect the deposited balance.

6. Cross-check the updated balance on https://scrollscan.com/address/YOUR_ADDRESS.

Verifying ZK Proof Finality

1. Locate any recent deposit transaction hash on Scrollscan and click into its details.

2. Identify the “ZK Proof Status” field showing either “verified”, “pending”, or “failed”.

3. Confirm presence of a valid proof ID starting with “zkp_” followed by alphanumeric characters.

4. Check timestamp alignment between L1 finalization on Goerli and L2 confirmation on Scroll.

5. Validate inclusion of Merkle root and batch index matching canonical Scroll consensus parameters.

6. Observe that state transition logs match EVM bytecode execution traces without deviation.

Frequently Asked Questions

Q: Can I use the same MetaMask seed phrase for Scroll L2 as I do for Ethereum mainnet?A: Yes. Scroll L2 uses the same cryptographic derivation path as Ethereum, preserving full key compatibility across layers.

Q: Why does Scroll require Goerli ETH instead of direct ETH deposits?A: Scroll Alpha Testnet is anchored to Goerli for security validation; all proofs are submitted and verified against Goerli’s L1 state commitments.

Q: Is the Scroll Alpha Testnet RPC endpoint rate-limited?A: Yes. Public RPC endpoints enforce per-IP request quotas to prevent abuse; developers are advised to run local nodes or use authenticated endpoints for intensive testing.

Q: What happens if my ZK proof fails verification on L1?A: Failed proofs trigger automatic rollback of the corresponding batch; funds remain secured in the bridge contract until re-submission with corrected parameters.