Skip to main content

Deploy Protocols on L2

This guide explains how to deploy and configure the bridge and signal service protocols on L2.

Bridge Configuration​

Prerequisites​

  • L1 Chain ID (3151908)
  • L1_BRIDGE: 0x72bCbB3f339aF622c28a26488Eed9097a2977404
  • L2_SHARED_ADDRESS_MANAGER: 0x7633740000000000000000000000000000000006
  • L2 Prefunded Account
  • L2 RPC URL

Bridge Setup Script​

const { ethers } = require("ethers");

const RPC_URL = $RPC_URL;
const PRIVATE_KEY = $ACCOUNT_PRIVATE_KEY;
const CONTRACT_ADDRESS = $SHARED_ADDRESS_MANAGER;

// Contract ABI (Application Binary Interface)
const contractABI = [
{
    "inputs": [
{ "internalType": "uint64", "name": "_chainId", "type": "uint64" },
{ "internalType": "bytes32", "name": "_name", "type": "bytes32" },
{ "internalType": "address", "name": "_newAddress", "type": "address" }
    ],
    "name": "setAddress",
    "outputs": [],
    "stateMutability": "nonpayable",
    "type": "function"
}
];

async function main() {
const provider = new ethers.providers.JsonRpcProvider(RPC_URL);
const wallet = new ethers.Wallet(PRIVATE_KEY, provider);

const contract = new ethers.Contract(CONTRACT_ADDRESS, contractABI, wallet);

const chainId = $CHAIN_ID;
const name = ethers.utils.formatBytes32String("bridge");
const newAddress = $BRIDGE;

try {
const tx = await contract.setAddress(chainId, name, newAddress);
console.log("Transaction hash:", tx.hash);

const receipt = await tx.wait();
console.log("Transaction confirmed in block:", receipt.blockNumber);
} catch (error) {
console.error("Error calling setAddress:", error);
}
}

main();

Verification Steps​

After deploying both protocols:

  1. Verify Bridge Setup
  • Confirm the bridge address is correctly set
  • Check transaction confirmation on L2
  • Verify the bridge contract is accessible
  1. Verify Signal Service Setup
  • Confirm the signal service address is correctly set
  • Check transaction confirmation on L2
  • Verify the signal service contract is accessible
Environment Variables

Replace all variables (e.g., $RPC_URL, $ACCOUNT_PRIVATE_KEY, $CHAIN_ID, $BRIDGE) with your actual values before running the scripts.

Important Note

Ensure you have sufficient funds in your L2 account before deploying these protocols, as each transaction will require gas fees.

Troubleshooting​

If you encounter issues during deployment:

  1. Check Connectivity
  • Verify L2 RPC endpoint is accessible
  • Ensure network connectivity is stable
  1. Account Issues
  • Confirm account has sufficient funds
  • Verify private key is correct
  • Check account permissions
  1. Contract Interactions
  • Verify contract addresses are correct
  • Check that ABI matches the deployed contracts
  • Ensure gas limits are sufficient