How to deploy a smart contract on Coinbase's Base network?

Deploying smart contracts on Coinbase's Base network is seamless for Ethereum devs—use Hardhat, fund your wallet with ETH, and leverage EVM compatibility for low-cost, secure deployments.

Jul 23, 2025 at 10:28 am

Understanding the Base Network

Coinbase's Base network is an Ethereum Layer 2 (L2) blockchain built using the OP Stack, offering low-cost and secure transactions while maintaining Ethereum’s security guarantees. Before deploying a smart contract, it’s essential to understand that Base is EVM-compatible, meaning Solidity-based contracts that work on Ethereum will also function on Base. Developers must ensure their tooling supports custom RPC endpoints and that gas fees are paid in ETH—not a native token unique to Base.

Setting Up Your Development Environment

To begin, install Hardhat or Foundry, two widely used Ethereum development frameworks. For this guide, we’ll use Hardhat:

• Run npm init -y in your project directory.
• Install Hardhat: npm install --save-dev hardhat.
• Initialize the project: npx hardhat.
• Choose “Create a JavaScript project” and follow prompts.

• Install additional dependencies: npm install --save-dev @nomicfoundation/hardhat-toolbox.
  

  Ensure your project includes a contracts/ folder and a hardhat.config.js file. This setup prepares you for compiling and deploying contracts specifically to Base.

  Configuring Hardhat for Base Network

  
  Edit your hardhat.config.js to include Base’s network configuration:

  require("@nomicfoundation/hardhat-toolbox");
  /* @type import('hardhat/config').HardhatUserConfig /
  module.exports = {
  solidity: "0.8.20",
  networks: {
  base: {
  url: "https://base-mainnet.gateway.pokt.network/v1/lb/625479831234",
  accounts: [process.env.PRIVATE_KEY], // Store this in .env
  }
  }

• The RPC URL above is a public endpoint. For production, consider using a dedicated provider like Alchemy or Infura with Base support.

• Confirm the Solidity version matches your contract’s pragma statement—mismatched versions cause deployment failures.

  Writing and Compiling Your Smart Contract

  
  Create a simple contract in contracts/MyToken.sol:

  // SPDX-License-Identifier: MIT
  pragma solidity ^0.8.20;

contract MyToken {

string public name = "BaseToken";
mapping(address => uint256) public balances;

function mint(address to, uint256 amount) external {
    balances[to] += amount;
}

}

• Run npx hardhat compile to compile the contract.
• If successful, the artifact will appear in artifacts/.
• Compilation errors often stem from version mismatches or syntax issues—review the output carefully.
• Use npx hardhat clean if you encounter cached compilation issues.

Deploying to Base Mainnet

Create a deployment script in scripts/deploy.js:

async function main() {
  const MyToken = await ethers.getContractFactory("MyToken");
  const myToken = await MyToken.deploy();
  await myToken.waitForDeployment();
  console.log("MyToken deployed to:", await myToken.getAddress());
}
main().catch((error) => {
console.error(error);
process.exitCode = 1;
});
- Fund your wallet with ETH on Base (use the [Base faucet](https://faucet.quicknode.com/base) for testnet).
- Execute: `npx hardhat run scripts/deploy.js --network base`.
- Monitor the transaction on [Base Scan](https://basescan.org/) using the contract address.
- **Ensure your wallet has sufficient ETH to cover gas—Base uses ETH, not a separate token**.

<h3>Verifying the Contract on BaseScan</h3>
After deployment, verify your contract to make source code publicly readable:
- Visit [BaseScan Verify](https://basescan.org/verifyContract).
- Select “Single File” and paste your Solidity code.
- Input the constructor arguments (if any) as ABI-encoded (leave blank if none).
- Provide the contract address and compiler version used (e.g., v0.8.20+commit.1a017a22).
- Click “Verify & Publish”—**verification enhances trust and enables debugging**.

<h3>Frequently Asked Questions</h3>

**Can I use MetaMask to interact with my deployed Base contract?**  
Yes. Add Base as a custom network in MetaMask:
- Network Name: Base Mainnet  
- New RPC URL: `https://base-rpc.publicnode.com`  
- Chain ID: `8453`  
- Currency Symbol: ETH  
- Block Explorer URL: `https://basescan.org`  
Once added, connect MetaMask to your dApp frontend or use it to send transactions directly.

**What if my deployment fails with “insufficient funds”?**  
This means your wallet lacks ETH on Base. Transfer ETH from Ethereum mainnet to your Base address using the [official Base Bridge](https://bridge.base.org/). Confirm the transaction on both chains before retrying deployment.

**How do I deploy to Base Sepolia testnet instead?**  
Update your `hardhat.config.js` with:
baseSepolia: {
 url: "https://base-sepolia.gateway.pokt.network/v1/lb/625479831234",
 accounts: [process.env.PRIVATE_KEY]
}

Then run: npx hardhat run scripts/deploy.js --network baseSepolia. Use the Base Sepolia faucet for test ETH.

Is there a difference between deploying to Base vs. Ethereum mainnet?

The process is nearly identical due to EVM compatibility. Key differences include:

• Lower gas fees on Base.
• Different RPC endpoints and chain IDs.
• BaseScan instead of Etherscan for verification and monitoring.
  
  Ensure your tooling supports Base-specific configurations to avoid errors.