[ZK Stack] - Instructions to Deploy a ZkStack Chain with Custom Token as a Gas token

[brucewhine]

Team or Project

Gotham

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.75.0

Operating System

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

Issue Description

I'm trying to create a custom zk chain, but after creating the ecosystem and trying to initialise the chain, I'm getting the following error.

● Initializing chain xxx
│
■ Failed to create portal config
│
▲ 0: Invalid name: please ensure the contract and method you're calling exist! failed to decode empty bytes. if you're using jsonrpc this is likely due to jsonrpc returning 0x in case contract or method don't exist
│
└ Failed to run command

Followed so far,
For setting up the custom token I've followed this doc: https://code.zksync.io/tutorials/custom-zk-chain/customizing-your-chain.

I've used the governer wallet to deploy the token contract on L1 and used the same address while creating the chain, but when doing
zkstack chain init
getting an insufficient balance error from a different address other than the governor account.

If I send the balance to that account and try again, getting BridgeHubAlreadyRegistered Error

Expected Behavior

Custom token to be Gas token for the Rollup

Current Behavior

Getting error setting up the Custom token

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.

[gleenai[bot]]

It seems like you are encountering multiple issues while setting up a custom zk chain with a custom token as the gas token. Here are some steps and considerations based on the information you've provided:

1. Invalid Name Error: This error typically indicates that the contract or method name provided does not exist or is not correctly deployed. Double-check the contract address and method names in your deployment scripts and ensure they are correctly deployed on L1.

2. Insufficient Balance Error: This error suggests that the address trying to initialize the chain does not have enough balance of the custom token to pay for the gas fees. Ensure that the address you are using to initialize the chain has a sufficient balance of the custom token. You might need to transfer an adequate amount of the custom token to this address.

3. BridgeHubAlreadyRegistered Error: This error occurs if you are trying to register a token or address that has already been registered in the BridgeHub contract. Ensure that the token or address you are trying to register is not already registered. If it is, you may need to use a different address or token, or deregister the existing entry if possible.

For detailed guidance on setting up a custom zk chain with a custom ERC20 token as the gas token, you can refer to the Custom Base Tokens documentation. This guide provides comprehensive steps for deploying an ERC20 token to L1, creating a new chain that uses this ERC20 token, and setting it as the default.

If these steps do not resolve your issues, it may be helpful to revisit the configuration files and deployment scripts to ensure all parameters and addresses are correctly set. Additionally, consider reaching out on the ZKsync developers discussions on Github for more in-depth support.

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.

[bxpana]

Did you make sure to initialize the ecosystem too? https://code.zksync.io/tutorials/custom-zk-chain#deploying-the-ecosystem

I went through the tutorial and was able to get everything running. Had to change a few of the ports but ultimately got 2 chains deployed and one with a custom base token.

[sachanayush47]

To fix BridgeHubAlreadyRegistered error, update the chain ID to something else. For example, if your chain ID is 456, change it to a different value. This error occurred because in your 1st attempt chain has been successfully registered to the Bridge Hub and you cannot register another chain with same ID.