Deploying to L2 networks in Blockchain / Solidity - Step-by-Step Execution

Concept Flow - Deploying to L2 networks

Write Smart Contract

↓

Compile Contract

↓

Connect to L2 Network

↓

Deploy Contract

↓

Confirm Deployment

↓

Interact with Contract on L2

This flow shows the steps to deploy a smart contract on a Layer 2 blockchain network, from writing code to interacting after deployment.

Execution Sample

Blockchain / Solidity

const contract = await ethers.getContractFactory("MyContract");
const deployed = await contract.deploy();
await deployed.deployed();
console.log("Deployed to L2 at", deployed.address);

This code deploys a smart contract to an L2 network and logs its address after deployment.

Execution Table

Step	Action	Evaluation	Result
1	Get contract factory	ethers.getContractFactory("MyContract")	Contract factory object ready
2	Deploy contract	contract.deploy()	Transaction sent to L2 network
3	Wait for deployment	deployed.deployed()	Deployment confirmed on L2
4	Log address	console.log(...)	Prints deployed contract address

💡 Deployment confirmed and contract address logged, process complete

Variable Tracker

Variable	Start	After Step 1	After Step 2	After Step 3	Final
contract	undefined	Contract factory object	Contract factory object	Contract factory object	Contract factory object
deployed	undefined	undefined	Deployed contract instance	Deployed contract instance	Deployed contract instance

Key Moments - 2 Insights

Why do we wait for 'deployed.deployed()' before using the contract address?

Waiting for 'deployed.deployed()' ensures the contract is fully deployed on the L2 network before interacting, as shown in execution_table step 3.

What does 'ethers.getContractFactory' do in deployment?

'ethers.getContractFactory' prepares the contract code for deployment, creating a factory object as seen in execution_table step 1.

Visual Quiz - 3 Questions

Look at the execution_table, what is the state of 'contract' after step 2?

A Contract factory object

B Deployed contract instance

C Deployment transaction object

D Undefined

💡 Hint

Check the 'contract' variable in variable_tracker after step 2

At which step does the deployment get confirmed on the L2 network?

A Step 1

B Step 3

C Step 2

D Step 4

💡 Hint

See execution_table step 3 description

If we skip waiting for 'deployed.deployed()', what might happen?

A Contract address will be undefined

B Deployment will fail immediately

C We might interact with a contract not yet deployed

D Nothing changes, safe to skip

💡 Hint

Refer to key_moments about waiting for deployment confirmation

Concept Snapshot

Deploying to L2 networks:
1. Write and compile your smart contract.
2. Connect to the L2 network using a provider.
3. Use contract factory to deploy.
4. Wait for deployment confirmation with deployed.deployed().
5. Interact with the contract using its L2 address.

Full Transcript

Deploying to Layer 2 networks involves writing your smart contract code, compiling it, and then connecting to the Layer 2 blockchain network. Using a contract factory, you deploy the contract by sending a transaction to the network. It is important to wait for the deployment to be confirmed on the network before interacting with the contract. This ensures the contract is fully available and avoids errors. After confirmation, you can use the contract address to call functions or send transactions on the L2 network.