Integration of gateway layer into zksync ecosystem fails

[thecodingshrimp]

Team or Project

No response

Module Affected

• System contracts (era-system-contracts)
• Smart contracts (era-contracts)
• zkEVM (era-zk_evm)
• Server (zksync-era)
• Prover (era-boojum)
• Fee withdrawer (era-fee-withdrawer)
• Block Explorer (clock-explorer)
• Portal - Wallet + Bridge (dapp-portal)
• Other (please specify below)

Rust Version

1.84.0

Operating System

• Ubuntu
• MacOS
• Windows
• Other (Please specify below)

Issue Description

When I follow the instructions on your website on how to integrate a gateway into an existing ecosystem, it fails when starting the gateway (4th step): https://docs.zksync.io/zk-stack/running/gateway-settlement-layer.

After the following sequence of commands, the last one fails:

$ zkstack ecosystem create --l1-network localhost --link-to-code path/to/zksync-era --ecosystem-name gateway-test --chain-name testchain --chain-id 271 --wallet-creation localhost --prover-mode gpu --l1-batch-commit-data-generator-mode validium --evm-emulator false --update-submodules false --start-containers true
$ zkstack ecosystem init --dev
$ zkstack server (to start the testchain ledger)
$ zkstack chain create \
    --chain-name gateway \
    --chain-id 506 \
    --prover-mode no-proofs \
    --wallet-creation localhost \
    --l1-batch-commit-data-generator-mode rollup \
    --base-token-address 0x0000000000000000000000000000000000000001 \
    --base-token-price-nominator 1 \
    --base-token-price-denominator 1 \
    --set-as-default false \
    --evm-emulator false \
    --ignore-prerequisites --update-submodules false
$ zkstack chain init \
  --deploy-paymaster \
  --l1-rpc-url=http://localhost:8545 \
  --server-db-url=postgres://postgres:notsecurepassword@localhost:5432 \
  --server-db-name=zksync_server_localhost_gateway \
  --chain gateway --update-submodules false
$ zkstack chain gateway convert-to-gateway --chain gateway --ignore-prerequisites
$ mkdir zklogs
$ zkstack server --ignore-prerequisites --chain gateway &> ./zlogs/gateway.log &

According to the logs, it fails with a transaction to the layer 1:

�[2m2025-07-11T14:26:17.913903Z�[0m �[31mERROR�[0m �[1mEthTxManager::loop_iteration�[0m�[2m:�[0m �[2mzksync_eth_sender::eth_tx_manager�[0m�[2m:�[0m Eth tx failed EthTx { id: 2, nonce: Nonce(4), contract_address: 0x80745456561f8f6837ab04352a91ef884650391c, tx_type: PublishProofOnchain, created_at_timestamp: 1752243976, predicted_gas_cost: Some(800000), chain_id: Some(SLChainId(9)), is_gateway: false }, TransactionReceipt { transaction_hash: 0x2085f60f908136c33059064281c7592afc8f0d6ef4bebc9782399d7100854a14, transaction_index: 0, block_hash: Some(0x88a1cb8b7fbb84b40e53b44f8b0c030bfb3e064f3d8be6aad61dc4c17f391648), block_number: Some(81173), from: 0xaff61e1f5d7a2218a5091e62b3be211838dd29ea, to: Some(0x80745456561f8f6837ab04352a91ef884650391c), cumulative_gas_used: 99524, gas_used: Some(99524), contract_address: None, logs: [], status: Some(0), root: None, logs_bloom: 0x00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000, transaction_type: Some(2), effective_gas_price: Some(1000000004) }, failure reason Some(FailureInfo { revert_code: 3, revert_reason: "", gas_used: Some(99524), gas_limit: 800000 })

You can find all of the logs here:
gateway.log

Expected Behavior

The gateway should be fully integrated into the existing ecosystem after executing all commands on gateway tutorial page

Current Behavior

gateway fails during initial startup. See the logs under issue description.

Repository Link (if applicable)

No response

Additional Details

No response

Prior Research

• Yes, I searched for similar issues and did not find any matching ones.

[sarahschwartz]

@thecodingshrimp Thanks for reporting this! I will take a look and update you soon.

[thecodingshrimp]

@sarahschwartz is there any way I could leverage the documentation below the initial instructions: https://docs.zksync.io/zk-stack/running/gateway-settlement-layer#migrate-existing-zksync-chain-to-gateway-on-testnet-or-mainnet?

Could I potentially have two ecosystem setups and migrate one into the other? That would do the trick as well, right?

[sarahschwartz]

@thecodingshrimp It seems this is a known issue in the CLI, but running the commands I shared earlier from inside a clone of the zksync-era repo should work. Can you confirm the commit of the contracts submodule you have?

[thecodingshrimp]

@sarahschwartz I've tried the latest version of zksync-era @ 048753f31f3ab8f549adafe55cf5fa409921494a and contracts @ 017dc90763fa8d6f380a81482f33746ee5ea57b3 together with your instructions and it didn't work either.
Here is an updated sequence of commands that I do to reach the error:

# executing your commands:
$ foundryup-zksync -C 27360d4c8
$ cd zksync-era
$ git checkout main
$ git pull
$ rm -rf ./contracts
$ git submodule update --init --recursive
$ zkstackup --local
$ zkstack dev clean all
$ cd ..

# preparing ecosystem:
$ zkstack ecosystem create --l1-network localhost --link-to-code path/to/zksync-era --ecosystem-name gateway-test --chain-name testchain --chain-id 271 --wallet-creation localhost --prover-mode gpu --l1-batch-commit-data-generator-mode validium --evm-emulator true --update-submodules false --start-containers true
$ cd gateway_test
$ zkstack ecosystem init --dev
$ zkstack chain create \
    --chain-name gateway \
    --chain-id 506 \
    --prover-mode gpu \
    --wallet-creation localhost \
    --l1-batch-commit-data-generator-mode validium \
    --base-token-address 0x0000000000000000000000000000000000000001 \
    --base-token-price-nominator 1 \
    --base-token-price-denominator 1 \
    --set-as-default false \
    --evm-emulator true \
    --ignore-prerequisites --update-submodules false
$ zkstack chain init \
  --deploy-paymaster \
  --l1-rpc-url=http://localhost:8545 \
  --server-db-url=postgres://postgres:notsecurepassword@localhost:5432 \
  --server-db-name=zksync_server_localhost_gateway \
  --chain gateway --update-submodules false
$ zkstack chain gateway convert-to-gateway --chain gateway --ignore-prerequisites
$ zkstack server --ignore-prerequisites --chain gateway
$ zkstack chain gateway migrate-to-gateway --chain testchain--gateway-chain-name gateway

Did I understand correctly that you created an ecosystem within the zksync-era folder? Would that make a difference?

[mm-zk]

from what I see, you fail on 'PublishProofOnchain' - and you're running with provers enabled (--prover-mode gpu).

Is that expected?

I've just re-run all the steps from https://github.com/matter-labs/zksync-era/blob/main/docs/src/guides/launch.md on 3e360e1c42049f999635f2e509d946c1d0c5f865 (including doing zkstackup --local), and it seems to be working.

I'd suggest making sure that everything works with proving disabled, before you move to enabling proofs.

[antonbaliasnikov]

Hey @thecodingshrimp ,
Please, let us know if it works for you now. Feel free to re-open the thread with the new info if required.