[Dev Tools] Contracts are 4x in size after migrating hardhat project

[rakoia]

Team or Project

No response

ZK chain

abstract

Environment

Testnet

Select the Dev Tool you are using

Hardhat Plugins

Provide the version of the tool (if applicable)

1.6

Provide a brief description of the functionality you're trying to implement and the issue you are running into.

I'm running into an issue when switching over to Zksync where by contracts are all doing about a 4x in size, throwing them all above the limit, even the small contracts. I'm not sure if I have something wrong in my setup or not.

This is my hardhat.config.ts

import { HardhatUserConfig } from "hardhat/config";
import "hardhat-contract-sizer";
import "hardhat-gas-reporter";
import "@matterlabs/hardhat-zksync";
import "@matterlabs/hardhat-zksync-upgradable";

const config: HardhatUserConfig = {
  solidity: {
    version: "0.8.28",
  },
  zksolc: {
    version: "1.5.15",
    settings: {
      optimizer: {
        enabled: true,
        mode: "3",
        fallback_to_optimizing_for_size: true,
      },
      codegen: "evmla",
    },
  },
  contractSizer: {
    runOnCompile: true,
    strict: true,
  },
  gasReporter: {
    enabled: true,
    darkMode: true,
  },
  defaultNetwork: "abstractTestnet",
  networks: {
    abstractTestnet: {
      url: "https://api.testnet.abs.xyz",
      ethNetwork: "sepolia",
      zksync: true,
      chainId: 11124,
    },
    abstractMainnet: {
      url: "https://api.mainnet.abs.xyz",
      ethNetwork: "mainnet",
      zksync: true,
      chainId: 2741,
    },
  },
};

export default config;

And my package.json dependencies

"devDependencies": {
    "@matterlabs/hardhat-zksync": "^1.6.0",
    "@matterlabs/hardhat-zksync-upgradable": "^1.9.0",
    "@nomicfoundation/hardhat-ethers": "^3.0.9",
    "@nomicfoundation/hardhat-ignition": "^0.15.11",
    "@nomicfoundation/hardhat-ignition-ethers": "^0.15.12",
    "@nomicfoundation/hardhat-toolbox": "^5.0.0",
    "@nomicfoundation/hardhat-verify": "^2.0.14",
    "@nomicfoundation/ignition-core": "^0.15.11",
    "@openzeppelin/contracts": "4.8.3",
    "@openzeppelin/upgrades-core": "^1.44.1",
    "ethers": "6",
    "hardhat": "^2.24.3",
    "hardhat-contract-sizer": "^2.10.0",
    "ts-node": "^10.9.2",
    "zksync-ethers": "6"
  },
  "dependencies": {
    "@limitbreak/creator-token-standards": "^5.0.0",
    "@nomicfoundation/hardhat-chai-matchers": "^2.0.9",
    "@nomicfoundation/hardhat-network-helpers": "^1.0.12",
    "@openzeppelin/contracts-upgradeable": "4.8.3",
    "@openzeppelin/hardhat-upgrades": "^3.9.0",
    "@typechain/ethers-v6": "^0.5.1",
    "@typechain/hardhat": "^9.1.0",
    "@types/chai": "^5.2.2",
    "@types/mocha": "^10.0.10",
    "chai": "^5.2.0",
    "dotenv": "^16.5.0",
    "hardhat-gas-reporter": "^2.3.0",
    "solidity-coverage": "^0.8.16",
    "typechain": "^8.3.2"
  }

Repo Link (Optional)

No response

Additional Details

No response

[ly0va]

Hi @rakoia, can you please elaborate what you mean by "throwing them all above the limit"? ZKsync uses a different virtual machine, and a contract's bytecode will be different (and larger) than of the same contract compiled for EVM, but the limit on bytecode size in ZKsync is not the same as in Ethereum.

Feel free to reopen and provide a sample contract you're having issues with so that we can reproduce them, otherwise I'll mark this as answered for now.

[rakoia]

Thanks for the response!

So for example, the basic ERC721 contract, completely default, goes from 3.470kb to 18kb. I cant quite share my other contracts, but here is a before and after of the sizing, but it should be reproducible with the ERC721

[ly0va]

@rakoia Yes I understand the bytecode size changes when compiling for ZKsync, but does it cause any issues? Are you not able to deploy these contracts to a ZKsync network? Otherwise an increased bytecode size is completely normal and expected.

[ly0va]

I'll close this for now, but please reach out if there is an issue with larger bytecode sizes!