[General] How can i deploy ZKSync on a private testnet?

[SyedMuhamadYasir]

Team or Project

No response

ZK chain

Era

Environment

Testnet

L2 block number

No response

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

I want to deploy ZKSync on top of an already running Ethereum PoS testnet

help and relevant documentation is greatly appreciated!

Repo Link (Optional)

No response

Additional Details

No response

[ly0va]

Hi @SyedMuhamadYasir, you can find all the docs related to setup and launch here in the first chapter or here.

You will need some additional configuration to point your chain to the desired Ethereum testnet as settlement layer, instead of a local reth. The config field to change that is l1.l1_rpc_url in secrets.yaml.

Feel free to unmark this discussion as answered if this does not answer your question.

[SyedMuhamadYasir]

@bxpana thanks alot for explaining this to me, I checked my configs folder and here are the files i see in the folder

as is visible, the wallets.yaml file is not present in the configs folder

however, i was able to find a wallets.yaml file in the following folder,

upon inspection, i see it has some values, exactly as how you show it

my only question, is - can all these entities (deployer, operator, blob_operator, fee_account, governor, token_multiplier_setter ) be the same address and private key?

if not, let me know if i need different ethereum wallets or something else for each of them?

and where can i read more about these in the zksync-era docs? i didn't see proper sections for these entities

[dimazhornyk]

hello! Yes, they all should be different wallets
I'm not sure whether it is documented somewhere, but in short, here is what each of them does:

• deployer is used during the deployment of the chain
• operator sends proveBatches and executeBatches transactions
• blob_operator sends commitBatches transactions
• fee_account receives fees collected from users on L2 (private_key might be omitted)
• governor owns the L1 contracts
• token_multiplier_setter changes the token conversion ratio in the custom-base-token chains

[SyedMuhamadYasir]

hello! Yes, they all should be different wallets I'm not sure whether it is documented somewhere, but in short, here is what each of them does:

• deployer is used during the deployment of the chain
• operator sends proveBatches and executeBatches transactions
• blob_operator sends commitBatches transactions
• fee_account receives fees collected from users on L2 (private_key might be omitted)
• governor owns the L1 contracts
• token_multiplier_setter changes the token conversion ratio in the custom-base-token chains

thank you! I was able to resolve this one

we actually have a MUCH more pressing issue that we need your help with

please inspect this error, i cannot quite make sense of it,

I am stuck here, and will greatly appreciate your help with this!

[dimazhornyk]

It is difficult to give a precise suggestion without full context, but I suspect that your configs are incorrectly initiated, which leads to this issue. Please follow this readme to init the ecosystem, and the chain within the ecosystem - the correct configs will be generated for you in the process.

If there are follow-up questions regarding the logs from screenshot - please create a separate discussion for it

[SyedMuhamadYasir]

It is difficult to give a precise suggestion without full context, but I suspect that your configs are incorrectly initiated, which leads to this issue. Please follow this readme to init the ecosystem, and the chain within the ecosystem - the correct configs will be generated for you in the process.

If there are follow-up questions regarding the logs from screenshot - please create a separate discussion for it

i will take a look at this.

in the meanwhile, a quick and important question - does ZKSync require Cancun on the Layer 1? Our ethereum private testnet does not have the Cancun fork/upgrade

is that going to be a problem?

[dimazhornyk]

It might be a problem, rollup in "Blobs" mode will certainly not work
and there are no guarantees that all L1 contracts will work as expected (or even be deployable)

[SyedMuhamadYasir]

It might be a problem, rollup in "Blobs" mode will certainly not work and there are no guarantees that all L1 contracts will work as expected (or even be deployable)

thank you

and what happens if i am able to upgrade my Layer 1 with the Cancun fork? will zksync work with my Layer 1 then?

[uF4No]

given that ZKsync currently works with Ethereum (Cancun) as L1, yes.