I AM UNABLE TO DEPLOY TO ZKSYNC-SEPOLIA CHAIN USING THE FORGE CREATE COMMAND IN THE FOUNDRY-ZKSYNC DOC[Deployment] <Title>

[EngrPips]

Team or Project

No response

ZK chain

ZKSYNC-SEPOLIA

Environment

Testnet

L2 block number

No response

zkSolc Version

zksolc-1.5.12

zksync-ethers Version

forge Version: 1.0.0-foundry-zksync-v0.0.14

Minimal Reproducible Code or Repo Link

// SPDX-License-Identifier: UNLICENSED
pragma solidity ^0.8.25;

import {ERC20} from "@openzeppelin/contracts/token/ERC20/ERC20.sol";
import {Ownable} from "@openzeppelin/contracts/access/Ownable.sol";

contract PipsToken is ERC20, Ownable {
    constructor() ERC20("PIPST", "PIPS") Ownable(msg.sender) {}

    function mint(address _to, uint256 _amount) external onlyOwner {
        _mint(_to, _amount);
    }
}

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

Ethereum

Description of What Your Contract Does

It is a simple ERC20 contract.

Additional Details

When I run the forge create command provided on both the foundry-zksync book and the zksync docs I run into the error shown below

forge create src/PipsToken.sol:PipsToken  --rpc-url ${ZKSYNC_SEPOLIA_RPC_URL} --account  sepoliaPrivateKey --chain 300 --zksync  --broadcast
[⠃] Using zksolc-1.5.12
[⠊] Compiling (zksync)
No files changed, compilation skipped
Enter keystore password:
Error: server returned an error response: error code -32602: Invalid parameters: transaction could not be decoded: unsupported transaction type

But when I removed the --zksync flag and the --chain flag the contract got deployed successfully, But every docs of zksync suggest adding the --zksync flag and that is really confusing as not adding those flags is what makes it deploy successfully for. So I am confused if the zksync team updated foundry-zksync to run forge create without needing the --zksync flag anymore and forgot to update the docs to reflect this changes or this is some weird stuff happening on my end?

The below is successful deployment when I run without the --zksync flag

forge create src/PipsToken.sol:PipsToken  --rpc-url ${ZKSYNC_SEPOLIA_RPC_URL} --account  sepoliaPrivateKey  --broadcast
[⠊] Compiling...
No files changed, compilation skipped
Enter keystore password:
Deployer: 0x186C2177C01e507596F9a866D3c741c7e1B15001
Deployed to: 0xA0A83a39708E06ABB96bD52ae5426450d7127048
Transaction hash: 0xc598d308bc248cdfd68a2b247a7de85d573af1a994498f7b3346f98370d00952

Looking forward to the team response. thanks for creating this amazing tool.

[JackHamer09]

Try putting --zksync flag before src/PipsToken.sol:PipsToken. For example this works for me: forge create --rpc-url "https://sepolia.era.zksync.dev" --private-key "0x..." --zksync src/PipsToken.sol:PipsToken

Deploying without --zksync flag works because of a very recent upgrade of zksync which added support for evm equivalent bytecode. If you visit Block Explorer page for your contract you will see EVM tag. However, running EVM equivalent bytecode might be more expensive, depending on each specific case.

[EngrPips]

I guess I happened to run into some weird case with Foundry-zksync because now even the command I tried initially which failed is no working fine.

forge create src/PipsToken.sol:PipsToken  --rpc-url ${ZKSYNC_SEPOLIA_RPC_URL} --account  sepoliaPrivateKey --chain 300 --zksync --broadcast
[⠃] Using zksolc-1.5.12
[⠊] Compiling (zksync)
No files changed, compilation skipped
Enter keystore password:
Deployer: 0x186C2177C01e507596F9a866D3c741c7e1B15001
Deployed to: 0xc465a6E775B4Aa0b5Fc281c223Cf6F0A66539B43
Transaction hash: 0xcee88ab69036d5f41e66391f23ac298203c03ed7a1e6e2b730dc1c2935c98cdd

Thanks for the response anyway, I appreciate it.