[ZK Stack] - How to initialise an ecosystem with a local Besu network? #826
Replies: 2 comments 4 replies
-
It seems you are encountering an issue with initializing the ZKsync ecosystem using a custom L1 Besu network. The error message indicates a problem with the deployment script Here are a few steps and considerations that might help you resolve this issue:
If you continue to face issues, providing the detailed logs and configurations might help further diagnose the problem. 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. |
Beta Was this translation helpful? Give feedback.
-
Hey @LimonChillo 👋 I do not think anyone has tried to connect to besu before so this is a bit uncharted territory. However, I don't foresee any reason why it should not work but likely some changes may be required when using the cli. Are you able to successfully run the following forge script If so, that is a good initial step. Then we need to confirm that the following additional forge scripts can be successfully run against your besu network. Once we have the contracts fully deployed / admins and permissions set then I think that would confirm our ability to use besu as our L1. |
Beta Was this translation helpful? Give feedback.
-
Team or Project
No response
Module Affected
Rust Version
1.81.0
Operating System
Issue Description
I would like to connect my zkstack (v0.1.0-a10c4baa) ecosystem to a custom L1. I tried to connect to a private Besu network (IBFT, running in docker on my local machine) rather than the packaged reth client.
I have updated the wallet adresses at
/chains/zk_chain_1/configs/wallets.yaml
and/configs/wallets.yaml
to pre-funded rich wallets on the Besu network.After that I started
zkstack ecosystem init
and it failed executingdeploy-scripts/DeployL1.s.sol
. Contracts seem to be deployed successfully though, the console output shows execution up until after theupdateOwners()
task.Did someone encounter something something similar, or can guide me how I may connect the stack to a custom L1 on Besu?
Thanks a lot everyone!
Expected Behavior
Stack should be initiated with a custom L1
Current Behavior
See error output above
Repository Link (if applicable)
No response
Additional Details
No response
Prior Research
Beta Was this translation helpful? Give feedback.
All reactions