[Deployment] I'm trying to deploy an AA factory, but receivinginsufficient funds for gas + value

[AlbionaHoti]

Environment

Testnet

zkSolc Version

latest

zksync-ethers Version

^6.7.0

Hardhat.config.ts

import { HardhatUserConfig } from "hardhat/config";

import "@matterlabs/hardhat-zksync";

const config: HardhatUserConfig = {
  defaultNetwork: "zkSyncSepoliaTestnet",
  networks: {
    zkSyncSepoliaTestnet: {
      url: "https://sepolia.era.zksync.dev",
      ethNetwork: "sepolia",
      zksync: true,
      verifyURL: "https://explorer.sepolia.era.zksync.dev/contract_verification",
    },
    zkSyncMainnet: {
      url: "https://mainnet.era.zksync.io",
      ethNetwork: "mainnet",
      zksync: true,
      verifyURL: "https://zksync2-mainnet-explorer.zksync.io/contract_verification",
    },
    zkSyncGoerliTestnet: { // deprecated network
      url: "https://testnet.era.zksync.dev",
      ethNetwork: "goerli",
      zksync: true,
      verifyURL: "https://zksync2-testnet-explorer.zksync.dev/contract_verification",
    },
    dockerizedNode: {
      url: "http://localhost:3050",
      ethNetwork: "http://localhost:8545",
      zksync: true,
    },
    inMemoryNode: {
      url: "http://127.0.0.1:8011",
      ethNetwork: "localhost", // in-memory node doesn't support eth node; removing this line will cause an error
      zksync: true,
    },
    hardhat: {
      zksync: true,
    },
  },
  zksolc: {
    version: "latest",
    settings: {
      isSystem: true,
      // find all available options in the official documentation
      // https://era.zksync.io/docs/tools/hardhat/hardhat-zksync-solc.html#configuration
    },
  },
  solidity: {
    version: "0.8.17",
  },
};

export default config;

Deployment Script (WITHOUT PRIVATE KEY)

import { utils, Wallet } from "zksync-ethers";
import { HardhatRuntimeEnvironment } from "hardhat/types";
import { Deployer } from "@matterlabs/hardhat-zksync-deploy";


import dotenv from "dotenv";
dotenv.config();
const WALLET_PRIVATE_KEY = process.env.WALLET_PRIVATE_KEY || "";

export default async function (hre: HardhatRuntimeEnvironment) {
  // Private key of the account used to deploy
  const wallet = new Wallet(WALLET_PRIVATE_KEY);
  const deployer = new Deployer(hre, wallet);
  const factoryArtifact = await deployer.loadArtifact("AAFactory");
  const aaArtifact = await deployer.loadArtifact("HotColdAA");

  // Getting the bytecodeHash of the account
  const bytecodeHash = utils.hashBytecode(aaArtifact.bytecode);

  const factory = await deployer.deploy(factoryArtifact, [bytecodeHash], undefined, [
    // Since the factory requires the code of the multisig to be available,
    // we should pass it here as well.
    aaArtifact.bytecode,
  ]);

  const factoryAddress = await factory.getAddress();

  console.log(`AA factory address: ${factoryAddress}`);
}

Package.json

{
  "name": "zksync-hardhat-template",
  "description": "A template for zkSync smart contracts development with Hardhat",
  "private": true,
  "author": "Matter Labs",
  "license": "MIT",
  "repository": "https://github.com/matter-labs/zksync-hardhat-template.git",
  "scripts": {
    "deploy": "hardhat deploy-zksync --script deploy.ts",
    "interact": "hardhat deploy-zksync --script interact.ts",
    "compile": "hardhat compile",
    "clean": "hardhat clean",
    "test": "hardhat test --network hardhat"
  },
  "devDependencies": {
    "@matterlabs/hardhat-zksync": "^1.0.0",
    "@matterlabs/zksync-contracts": "^0.6.1",
    "@nomiclabs/hardhat-etherscan": "^3.1.7",
    "@openzeppelin/contracts": "4.9.5",
    "@types/chai": "^4.3.4",
    "@types/mocha": "^10.0.1",
    "chai": "^4.3.7",
    "dotenv": "^16.0.3",
    "ethers": "^6.9.2",
    "hardhat": "^2.12.4",
    "mocha": "^10.2.0",
    "ts-node": "^10.9.1",
    "typescript": "^4.9.5",
    "zksync-ethers": "^6.7.0"
  }
}

Contract Code

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

import "@matterlabs/zksync-contracts/l2/system-contracts/Constants.sol";
import "@matterlabs/zksync-contracts/l2/system-contracts/libraries/SystemContractsCaller.sol";

contract AAFactory {
    bytes32 public aaBytecodeHash;

    constructor(bytes32 _aaBytecodeHash) {
        aaBytecodeHash = _aaBytecodeHash;
    }

    function deployAccount(bytes32 salt, address hotWallet, address coldWallet, uint256 maxValue) external returns (address accountAddress) {
        (bool success, bytes memory returnData) = SystemContractsCaller.systemCallWithReturndata(
            uint32(gasleft()),
            address(DEPLOYER_SYSTEM_CONTRACT),
            uint128(0),
            abi.encodeCall(
                DEPLOYER_SYSTEM_CONTRACT.create2Account,
                (salt, aaBytecodeHash, abi.encode(hotWallet, coldWallet, maxValue), IContractDeployer.AccountAbstractionVersion.Version1)
            )
        );
        require(success, "Deployment failed!");

        (accountAddress) = abi.decode(returnData, (address));
    }
}

Does this work on other EVMs? (If yes, please list at least 1 of them)

Didn't test on other EVMs

Description of What Your Contract Does

Deploys an AA Factory.

Repo Link (Optional)

https://github.com/albionahoti/hot-cold-aa/

Additional Details

No response

[gleenai[bot]]

The error message "insufficient funds for gas + value" that you're encountering during the deployment of your AA factory on the zkSync Sepolia Testnet typically indicates that the wallet you are using to deploy the contract does not have enough funds to cover the gas fees required for the transaction.

Here are a few steps you can take to resolve this issue:

1. Check Wallet Balance: Ensure that the wallet you are using for deployment has sufficient funds. You can check the balance by connecting your wallet to a block explorer for the Sepolia Testnet or using a script to query the balance directly.

2. Add Funds to Your Wallet: If your balance is low, you will need to add funds to your wallet. Since you are using the Sepolia Testnet, you can obtain Sepolia ETH from a faucet. Here are a few steps on how to do this:

   • Visit a Sepolia faucet (e.g., https://faucet.sepolia.dev/).
   • Enter your wallet address.
   • Follow the instructions to receive testnet ETH.

3. Adjust Gas Limit and Gas Price: Sometimes, the default gas settings might not be sufficient or optimal for contract deployment. You can adjust these settings in your deployment script. Make sure the gasLimit and gasPrice are set appropriately for the network conditions. You can check the current gas prices on the Sepolia Testnet using a block explorer.

4. Review Deployment Script: Double-check your deployment script for any issues that might cause higher gas consumption. Ensure that the contract code is optimized and that you are not passing unnecessary data in transactions.

5. Network Issues: Occasionally, network issues can cause transactions to fail. Verify that the zkSync Sepolia Testnet is operational and there are no ongoing issues that might affect transactions.

6. Error in Contract Code: Review your smart contract code to ensure there are no errors or inefficiencies that could increase the gas cost unexpectedly. Pay special attention to loops and state changes, which can be costly in terms of gas.

If after taking these steps you still face issues, consider reaching out for support on the zkSync developer forums or community channels where you might get more specific advice related to your contract and deployment environment.

Your feedback helps us serve you better. If this fully addresses your question, please give it a thumbs up. If it doesn't, please give it a thumbs down. This will inform the community and team so we can improve our support.