[Deployment] Bootloader-based tx failed

[anxolin]

Team or Project

CoW Protocol

ZK chain

lens

Environment

Mainnet

L2 block number

No response

zkSolc Version

zksync-ethers Version

Minimal Reproducible Code or Repo Link

# Clone project
git clone https://github.com/anxolin/uni-v2-deployments
cd uni-v2-deployments

# build
forge install
forge build

# Set PK for account with some GHO for deploying a new contract
export PRIVATE_KEY=<your-pk>

# Deploy
forge script script/UniswapV2Factory.s.sol:UniswapV2FactoryScript \
  --rpc-url https://rpc.lens.xyz \
  --private-key $PRIVATE_KEY \
  --broadcast 

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

sepolia

Description of What Your Contract Does

This is Uniswap-v2 factory. It creates new pools

Additional Details

The project deploys the Uniswap V2 factory.

It has been deployed and verified in Sepolia:

• https://sepolia.etherscan.io/tx/0xfea70b7447b19b766b76d630a4cdaec3e2be3e46c048072edf98460f983f3a6e

However, when deployed in Lens, I get an error:

• https://explorer.lens.xyz/tx/0x8eea9b0cfbc3f9656548190a84e38719e4a4046990d25159640a4b23348eabbf

I was not able to debug this in Tenderly, nor in foundry:

cast run --debug 0x8eea9b0cfbc3f9656548190a84e38719e4a4046990d25159640a4b23348eabbf --rpc-url https://rpc.lens.xy

The previous command returns:

Executing previous transactions from the block.
The application panicked (crashed).
Message:  Expected create transaction, got Call(0x0000000000000000000000000000000000000000)
Location: crates/evm/evm/src/executors/mod.rs:340

This is a bug. Consider reporting it at https://github.com/matter-labs/foundry-zksync

  ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ BACKTRACE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
                                ⋮ 9 frames hidden ⋮
  10: foundry_evm::executors::Executor::deploy_with_env::h110b1e60003cb6f5
      at <unknown source file>:<unknown line>
  11: cast::cmd::run::RunArgs::run::{{closure}}::h8061beef65e31c7f
      at <unknown source file>:<unknown line>
  12: cast::args::run_command::{{closure}}::hb65ab27cda6c052d
      at <unknown source file>:<unknown line>
  13: tokio::runtime::park::CachedParkThread::block_on::h9cfa93e9c686e329
      at <unknown source file>:<unknown line>
  14: tokio::runtime::context::runtime::enter_runtime::h78a24d1aca995a9e
      at <unknown source file>:<unknown line>
  15: tokio::runtime::runtime::Runtime::block_on::hc12c0bc6d4a35225
      at <unknown source file>:<unknown line>
  16: cast::args::run_command::h7aa114c523b39da8
      at <unknown source file>:<unknown line>
  17: cast::args::run::ha383b010b494ceb6
      at <unknown source file>:<unknown line>
  18: cast::main::h9cd4f72544bca3ff
      at <unknown source file>:<unknown line>
  19: std::sys::backtrace::__rust_begin_short_backtrace::hbea2706721ddca0c
      at <unknown source file>:<unknown line>
  20: std::rt::lang_start::{{closure}}::haa5b66f2e6d01200
      at <unknown source file>:<unknown line>
  21: std::rt::lang_start_internal::hdff9e551ec0db2ea
      at <unknown source file>:<unknown line>
  22: _main<unknown>
      at <unknown source file>:<unknown line>

Run with COLORBT_SHOW_HIDDEN=1 environment variable to disable frame filtering.
Run with RUST_BACKTRACE=full to include source snippets.
[1]    75494 abort      cast run --debug  --rpc-url https://rpc.lens.xyz

[JackHamer09]

Hey, thanks for your report! I'll investigate the issue and get back to you!

[JackHamer09]

@anxolin seems like the deployment issue is related to an outdated foundry-zksync version. Try to update it to version at least v0.0.20. Docs

Also the cast run --debug error is a known issue for EVM contract creation, which is tracked here

[JackHamer09]

Can you share your foundry-zksync version?
I was able to deploy this contract only after updating the foundry. Before that I had exactly same error.

[anxolin]

This is the version I used in my last attempt:

cast Version: 1.0.0-foundry-zksync-v0.0.20
Commit SHA: 2e6c61becda5fc1409cae908c6aa509c5c24e729
Build Timestamp: 2025-06-19T14:22:44.357923000Z (1750342964)
Build Profile: release

However, what I'm after here is of using the compatibility layer. I only used foundry-zksync as an attempt to debug my issue, but what I really need is to deploy using foundry as it is. So the compatibility layer works.
We are aiming to deploy a complex protocol (CoW Protocol) in zksync, so this would help a lot.

Also, how do I debug the issues? For example, in the TX I shared, how can I tell what's the issue there?

[anxolin]

Hello @JackHamer09 could you help me understand this.

• Why compatibility layer is not working out of the box in this case
• How to debug these issues

We are encountering other issues deploying and setting up other contracts, and we struggle to debug those

[bxpana]

@anxolin seeing if I can help out here

1. Did you use the --skip-simulation flag? If not that should help with using Foundry out of the box with the EVM compatibility layer. More details in our docs
2. This one I'll check up on for you.

[Romsters]

Hi @anxolin, unfortunately debugger is not supported yet. You can use anvil-zksync to replay remote transactions and inspect call traces.

[anxolin]

The skip-simulation worked. I will check with anvil-zksync to debug and report back. Thanks!

[bxpana]

That's great to hear! Going to mark as answered for now, but if you run into anything else feel free to open another ticket

[anxolin]

I tried to run the following command, but I got an error:
anvil-zksync replay_tx --fork-url https://rpc.lens.xyz 0x8eea9b0cfbc3f9656548190a84e38719e4a4046990d25159640a4b23348eabbf

Is this expected?

Executing transactions from the block.
⠁ [00:00:00] [------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------] 0/1 tx (0.0s)
thread 'tokio-runtime-worker' panicked at /Users/runner/.cargo/git/checkouts/zksync-era-1391575832f0fa69/992a613/core/lib/multivm/src/versions/vm_latest/types/transaction_data.rs:73:21:
`execute.contract_address` not set for transaction 0x8eea9b0cfbc3f9656548190a84e38719e4a4046990d25159640a4b23348eabbf with EVM emulation disabled
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
Error: [anvil_zksync-node-0] Generic error: Error {
    context: "batch executor panicked",
    source: JoinError::Panic(Id(29), "`execute.contract_address` not set for transaction 0x8eea9b0cfbc3f9656548190a84e38719e4a4046990d25159640a4b23348eabbf with EVM emulation disabled", ...),
}
[anvil_zksync-gen-0] Generic error: [anvil_zksync-node-0] Generic error: Failed to receive a response to the request to seal a block with transactions ["0x8eea…abbf"] because node executor is dropped. \
         Another error was likely propagated from the main execution loop. \
         If this is not the case, please, report this as a bug.
Error: AnvilGeneric(GenericError { message: "[anvil_zksync-node-0] Generic error: Failed to receive a response to the request to seal a block with transactions [\"0x8eea…abbf\"] because node executor is dropped. \\\n         Another error was likely propagated from the main execution loop. \\\n         If this is not the case, please, report this as a bug." })