[ZK Stack] - How to deploy L3 chains? #778
Answered
by
MexicanAce
sachanayush47
asked this question in
ZK Stack
-
Team or ProjectNo response Module Affected
Rust Version1.82.0 Operating System
Issue DescriptionWe were trying to run L3 chain on top of L2 zksync hyperchain under the same ecosystem. L3 chain will have same base token as L2 chain. When we tried to achieve this I got the below error. RPC URL is L2 RPC URL. Base token address is Expected BehaviorL3 chain should get depoyed Current BehaviorFailed to deploy L3 chain Repository Link (if applicable)No response Additional DetailsNo response Prior Research
|
Beta Was this translation helpful? Give feedback.
Answered by
MexicanAce
Nov 19, 2024
Replies: 2 comments 3 replies
-
|
Currently, deploying L3 chains on top of L2 ZKsync hyperchains is not directly supported in the standard documentation or available tutorials. The error you encountered during the deployment process suggests there might be issues with the script or configuration specific to L3 setups, which are not covered in the existing guides. For now, it is only possible to deploy a ZK chain as an L2, but soon it will also work as L3s. This indicates that the functionality for L3 deployment might still be under development or requires specific configurations not yet documented. For further assistance and to discuss this issue in-depth with other developers, I recommend visiting the ZKsync developers discussions on Github. This platform can provide more specialized feedback and updates on the development of L3 capabilities. 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.
0 replies
-
|
Hi @sachanayush47 👋 ! To implement a ZK chain as an "L3", the L2 node would need to have its own Bridgehub deployed to it. This is not something available via the Alternatively, you could run L2s on the Gateway using this CI script (NOTE: This is still a work in progress). However, the Gateway does not allow direct launch of the chain onto the Gateway, nor will it allow chains to settle on Era (only migration to the Gateway will be allowed). |
Beta Was this translation helpful? Give feedback.
3 replies
-
|
Hi @MexicanAce, Thank for your answer. |
Beta Was this translation helpful? Give feedback.
-
|
Apologies for the confusion, but neither approach is via 3rd party providers. We unfortunately don't have guides for either of these approaches, as it's not something we currently support (but more of a hypothetical at the moment). Perhaps it would help if you describe why you are looking to implement an L3 vs an L2? |
Beta Was this translation helpful? Give feedback.
-
|
We have plans for having different side chains with different configuration to target a specific use case. So we interested in having a aggregation layer (L2) and top of that all the side chains exist (L3). and regarding confusion I thought you were referring to https://gateway.fm/ |
Beta Was this translation helpful? Give feedback.
Answer selected by
MexicanAce
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi @sachanayush47 👋 ! To implement a ZK chain as an "L3", the L2 node would need to have its own Bridgehub deployed to it. This is not something available via the
zkstackCLI tool, but if absolutely needed you could attempt to deploy it manually using calldata as L2 will not accept blobs. Be warned that the deploy scripts will not work as the L1/L2 bytecodes differ, so this would be non-trivial.Alternatively, you could run L2s on the Gateway using this CI script (NOTE: This is still a work in progress). However, the Gateway does not allow direct launch of the chain onto the Gateway, nor will it allow chains to settle on Era (only migration to the Gateway will be allowed).